Migration Tool — Upgrade from Jet Analytics 20.10 to Jet Analytics Data Integration

Note: Download and install the latest version of Jet Analytics 20.10 (minimum version 20.10.45) before running the Migration Tool. The Migration Tool is not available in older releases and must be enabled by Jet Analytics — contact support if it does not appear in the Tools menu after upgrading.

The Jet Analytics Migration Tool assists in upgrading existing Jet Analytics 20.10 projects to Jet Analytics Data Integration. This article explains how to use the tool.

Benefits

Jet Analytics Data Integration is cloud-enabled for significantly improved scalability and usability. Features available in Jet Analytics Data Integration include:

• No need to host project repositories — fully managed cloud instances.
• No licence keys — sign-in and granular user permission management replace client secrets and licence keys.
• Simplified multiple-environment management and promotion in the Portal, including Ingest instances.
• Cloud-based data source connection management — admins can create and share access to data sources without distributing passwords.
• PowerShell scripts in Execution Packages — unlocks automation capabilities within Azure.
• Snowflake support as Prepare instance storage.

See the Welcome to Jet Analytics Data Integration release notes for the full list of changes.

Please read first

Jet Analytics Data Integration differs significantly from Jet Analytics 20.10. Some features from the older version are no longer present, including:

• Business Units (these can be converted to Prepare instances using the Migration Tool)
• Multidimensional OLAP Cubes
• Project Variables
• External SQL Connection

Review the release notes and test thoroughly before upgrading to understand the changes and their potential impact on your operations.

Prerequisites

Before running the Migration Tool, create all required destination instances in the Jet Analytics Portal. See Add and Configure Instances for instructions. The tool supports partial migration — for example, migrating one data warehouse or a few semantic models at a time — so it is not strictly necessary to create all target instances before starting.

The instances required are:

• One Deliver instance per semantic model.
• Zero to one Prepare instances for each data warehouse and staging database (Business Unit). Multiple data warehouses and staging databases can be migrated into the same Prepare instance as separate data areas, provided the target Prepare instance has not yet been opened and initialised in Jet Analytics Data Integration.
• One Ingest instance per ODX.

The Migration Tool can automatically migrate many data sources. Some data sources have no direct equivalent in Jet Analytics Data Integration — for these, you must create the data source connections manually in the Jet Analytics Portal and map them in the tool. The tool lists any data sources that cannot be migrated automatically during project validation.

Note: The Jet Analytics portal is managed by the insightsoftware Support team. For assistance or additional information, reach out to Product Support

After creating the instances above, complete the following before running the Migration Tool:

1. Do NOT open or initialise any of the Prepare or Deliver instances in Jet Analytics Data Integration.
2. Do open and initialise the Ingest instance in Jet Analytics Data Integration. This requires running the Jet Analytics Ingest Server Configuration and selecting the newly created Ingest instance, then opening the Ingest instance in Jet Analytics Data Integration.

Open the tool and validate the project

1. OpenJet Analytics 20.10.x and open the project you want to migrate.
2. Under Tools, click Migration Tool.

   

3. On the first page of the wizard, read through the guidelines and click Next.

   

4. The project is validated to check whether it is ready to migrate or whether further action is required. If issues are found, the Project Validation page is displayed.

   

   Two types of issues may appear (see Migration Tool — Project Validation for details on each type):
   • Errors: Issues that must be resolved before migration can proceed — for example, a deprecated feature still in use. These typically require refactoring the project to remove unsupported functionality.
   • Warnings: Less severe issues that do not prevent migration — for example, a feature that has no equivalent in Jet Analytics Data Integration and will be skipped. No further action is required.
5. If the project has errors, click Cancel to close the wizard, fix the issues, and restart the Migration Tool. If validation completes without errors, select the I understand checkbox to accept any remaining warnings, then click Next.

6. Click Log In, enter your credentials, and click Sign In. Verify the account shown is correct (click Log Out if you need to switch accounts), then click Next.

   

7. On the What do you want to migrate? page, click Next to begin migrating data sources and ODX.

Migrate ODX and data sources

1. On the Select Destination page, select the Ingest instance to migrate your data sources to, then click Next. If no instance appears in the list, confirm that you have created an Ingest instance, run the Jet Analytics Ingest Server Configuration for it, and opened it in Jet Analytics Data Integration. Click Refresh and try again.

   

2. On the Connect Current ODXs page, enter the Client Secret and select the ODX Project for each ODX you are migrating, or select I don't want to migrate any ODXs — skip this step if you only want to migrate Business Unit data sources. Click Next.

   

3. On the Select Data Sources to Migrate page, configure how to handle each data source.

   

   • In the Data Source column, data sources from an ODX are prefixed with the ODX name. In the Status column, Already migrated indicates a data source was migrated in a previous run.
   • In the Destination column, select (Create new data source) to automatically create a new data source, or select an existing data source connection created manually in the Portal.
   • If (Create new data source) is not available for a specific data source, the data source cannot be migrated automatically. Manually create the data source connection in the Portal, then click Back to return to step 1, click Refresh, proceed through the steps again, and select the newly created connection in the Destination drop-down.
   Click Next when ready.
4. On the Review page, confirm the selections. ODX data sources are listed in the ODX group; Business Unit data sources appear in the Data sources group. Click Migrate.

   

5. On the Migration in Progress page, monitor the migration as it runs.

   

6. On the Migration Complete page, click Continue Migration to proceed to migrating data warehouses, or click Done to stop for now. It is recommended to open Jet Analytics Data Integration and the Portal to verify that the data sources were migrated correctly before continuing.

   

Migrate data warehouses and staging databases

1. On the What do you want to migrate? page, select Data warehouses and staging databases and click Next.
2. On the Select Destination page, select the target Prepare instance in the Destination list. Under Objects that will be migrated, review the data warehouses and staging databases to be migrated and their destination schema names. To customise a schema name, click Rename Schema and enter a new name. Click Next.

   

3. If not all data sources were migrated before migrating the data warehouse, the Data Source Mapping page is displayed. Map each data source in the Sources column to the corresponding connection in the Destination column. The Status column uses the following values:
   • Precise match: Source and destination were unambiguously mapped by ID.
   • Suggested match: Source and destination were mapped by name.
   • No match: The tool could not map the source automatically.
   • User selected: You have made a manual selection.
4. On the Copy Data Warehouse Data page, select Copy existing data to the Prepare instance if you want to migrate data as well as metadata. This is useful for data warehouses that contain historical data that would be impractical to reload from source. Select Let me select the tables to limit the copy to specific tables, then click Next.

   

   Note:

   To copy data warehouse data, complete the following steps first:

   1. Create Ingest instance storage: right-click the Ingest instance in Jet Analytics Data Integration, select Edit, and click Create Storage. It is not necessary to create the Prepare instance storage — the Migration Tool will create the destination database if it does not exist, using the collation of the majority of the databases being migrated. To use a specific collation, create the database in SQL Server before migrating; the tool will take ownership without changing the collation.
   2. Verify that all migrated data sources are working: execute the import metadata task, synchronise, select tables and fields in Metadata Manager, and run a transfer task.
5. If you chose to copy data and selected specific tables, the Tables Selection page is displayed. Select the tables to copy, then click Next.
6. On the Review page, confirm the selections, then click Migrate.

   

7. On the Migration in Progress page, monitor the migration as it runs.

   

8. On the Migration Complete page, click Continue Migration to proceed to migrating semantic models, or click Done to stop for now.

   

Migrate semantic models

1. On the What do you want to migrate? page, select Semantic models and click Next.
2. On the Select Source of Data page, select the Prepare instance your semantic models should get data from after migration — usually the instance you just migrated your data warehouses to — and click Next.

   

3. On the Map Semantic Models to Deliver Instances page, map each semantic model in the Source column to the corresponding Deliver instance in the Destination column.

   

   Select Copy Tabular Scripts in custom measures to Power BI if you are moving from Tabular to Power BI as part of the migration. This copies the script under Tabular in custom measures to Power BI Premium, avoiding manual copy-pasting.

   

   Click Next when ready.
4. On the Review page, confirm the selections, then click Migrate.

   

5. On the Migration in Progress page, monitor the migration as it runs.

   

6. On the Migration Complete page, click Continue Migration to migrate more, or click Done to finish. Open Jet Analytics Data Integration to verify the results.

   

After migration

1. Once all projects have been migrated, open Jet Analytics Data Integration and open the target Prepare instance. Each migrated project will appear as its own data area within the instance. Click Yes to upgrade the instance if prompted.

   

2. Expand the Tables node — all tables will be marked in red. Right-click and select Deploy and Execute to deploy the tables.

   

3. (Optional) If deployment returns a Table Not Found error, use the Synchronize with Ingest instance feature to remap the tables to the new data source table names. Provided all fields share the same names, this is typically straightforward.

   

4. Right-click the Prepare instance and select Synchronize with Ingest instance.

   

5. Select the appropriate Ingest instance from the list. If multiple projects were migrated into the same Prepare instance, the same Ingest instance may appear more than once — open them one by one to find the one that matches the current data area.

   

6. Click Remap next to any table with a red X in the Status column.

   

7. Use the Select Tables dialog to find and select the correct source table for each remapping.

   

8. Click OK and confirm the status changes to green.

   

9. Complete remapping for all remaining tables as needed, then click OK.

   

10. Attempt to Deploy and Execute the tables in the data area again — the deployment should now complete successfully.