Insight v5 Data Migration Requirements and Steps for Existing Insight 4.x Customers – Archer Community

Data Migration Requirements for Existing Insight 4.x Customers

To support the Archer Insight v5.0 upgrade, the Archer Insight 2025.04 package introduces several structural changes that require data migration.

These migration activities can be completed using standard data export and import procedures.

1. Deprecation of Insight Driver Probability and Insight Upstream Risk Probability Applications

The Insight Driver Probability and Insight Upstream Risk Probability applications have been deprecated.

The synchronization process now writes calculated data directly to the Insight Drivers application.

Architectural Changes

Driver Probability Changes

Removal of the Insight Driver Probability application.
Removal of risk probability calculations for drivers.
- Driver rates should represent the likelihood that the driver causes the risk event, rather than the independent likelihood of the driver occurring.
Addition of a direct relationship between Insight Risk Events and Insight Drivers.
Addition of a direct relationship between Insight Control Probability and Insight Drivers.

Upstream Risk Probability Changes

Removal of the Insight Upstream Risk Probability application.

Migration Steps

A. Migration from Driver Probability

Execute a search that:
- Includes the Risk Event Tracking ID.
- Includes a relationship to Driver Probability (without selecting additional fields).
- Includes the Insight Driver Tracking ID.
Use the exported results to perform a data import that creates direct relationships between Risk Events and Drivers using the new reference field.
Review any Driver Probability records with a risk probability value other than 1.0.
- If found, adjust the associated driver rate accordingly.
- This scenario is expected to be uncommon because it would typically occur only if risk events were created outside of the Insight assessment screens.
Review whether any Insight Drivers are linked to multiple Risk Events.
- Under the new architecture, a driver may be associated with only one Risk Event.
- Where reuse exists, create separate Insight Driver records for each Risk Event.
- This situation is also expected to be uncommon.
Execute a second search that:
- Begins with Insight Drivers.
- Includes the Driver Tracking ID.
- Includes a relationship to Insight Driver Probability.
- Includes related Control Probability Tracking IDs.
Use the exported results to perform a data import that links Driver records directly to the existing Control Probability records using the new Driver-to-Control Probability relationship.

B. Migration from Upstream Risk Probability

Note: Upstream Risk Probability records could not be created through the standard assessment screens. As a result, most customers are unlikely to be using this application.

Execute a search that:
- Includes the Risk Event Tracking ID.
- Includes associated Upstream Risk Probability records.
- Includes associated Control Probability records.
Use the exported data to create new Insight Driver records through data import.
- The inherent rate from the upstream Risk Event should become the rate of the new Driver.
- Control Probability records previously linked to Upstream Risk Probability should be reassigned to the newly created Driver records.

2. Utility Scale Application Enhancements

The Utility Scale application now supports a flexible number of impact levels by impact type.

For example:

Environmental impacts may use six impact levels.
Reputational impacts may use six impact levels.
Social impacts may use four impact levels.

The Utility Scale application is now used solely to define impact-level descriptions and ranges for each impact type.

Architectural Changes

Non-Financial Consequences

Removal of the Utility Scale cross-references used by:
- Minimum Impact Level
- Most Likely Impact Level
- Maximum Impact Level
Replacement of these cross-references with:
- Minimum Impact Value
- Most Likely Impact Value
- Maximum Impact Value

Economic Consequences

Removal of the Minimum Impact Field.

Migration Steps

A. Migration of Non-Financial Consequences

Execute a search that:
- Filters only non-financial consequences.
- Includes the record Tracking ID.
- Includes Utility Scale reference fields for Minimum, Most Likely, and Maximum Impact Levels.
Export the results and perform a data import that maps the referenced utility scale values to the new Value List fields.
After validation, remove the legacy reference fields for Minimum, Most Likely, and Maximum Impact Levels.

B. Configure Impact Levels by Type

The new architecture allows different maximum impact levels for different impact types.

Key requirements:

Impact levels must always begin with 1.
Impact levels must be sequential with no gaps.
The maximum value for a Utility Scale record cannot exceed the number of impact levels defined in Corporate Global Variables.

For example:

If Corporate Global Variables specifies 6 impact levels:

Health & Safety may use levels 1–6
Environmental may use levels 1–4
Reputational may use levels 1–3

In this case, the Utility Scale application should contain:

Health & Safety: Levels 1 through 6
Environmental: Levels 1 through 4
Reputational: Levels 1 through 3

The Insight UI will automatically determine the number of available impact levels based on the highest defined non-financial impact level for each impact type.

3. Corporate Heat Map Scale Configuration

The Corporate Global Variables application now includes a new Heat Map Corporate Scale section.

This feature allows organizations to define:

Minimum Economic Impact Value for the X-axis
Maximum Economic Impact Value for the X-axis

To enable this functionality:

Open the Corporate Global Variables record.
Populate the following fields:
- Minimum Economic Impact Value for X-axis
- Maximum Economic Impact Value for X-axis

If either field remains blank, the Use Corporate Scale option will be unavailable on the Risk Quantification Dashboard heat map.

Related to