Data Integrator Migration Topics

Other Help Sets

Data Integrator
Galaxy Connectivity
[ALLDOCS:RushAnalytics for KNIME]


Skip to end of metadata
Go to start of metadata

Data Integrator 10 differs from version 9 in several important ways:

  • The new architecture, including all connectivity features, is 100-percent 64-bit. Any v9 connector using 32-bit connectivity will not migrate to v10.
  • Support for hierarchical data, such as XML, HIPAA, and EDI, has been completely redesigned. When migrating maps with these connectors defined in them, expect to modify the map after migration. Typically, you will need to do some manual steps , such as redraw mapping links and add event handlers after migration due to the connectors being redesigned in v10.
  • Undeprecated map events and actions provide the same functionality. However, they have been renamed, reduced in number, and simplified.

For a detailed list of differences between v9 and v10, see Comparing Version 9 with 10.

This help topic addresses the planning, preparation, and in certain cases, manual steps after migration required when using the v10 Migration Assistance Utility to convert v9 artifacts to v10 artifacts.



The v10 Migration Utility is specifically for converting v9 artifacts. If you want to convert artifacts from a release prior to the most current version of v9, you must first perform specific upgrade steps. See Upgrading from Previous Versions.

Migrating v9 artifacts to v10 artifacts using the Migration Assistance Utility involves the following steps:

  1. Discover your options for migrating v9 artifacts and determine your next step. See Step 1: Understand Your Options.
  2. Review important guidelines. See Step 2: Prepare to Migrate
  3. Assess your potential v9 artifacts for migration. See Step 3: Assess Your Artifacts.
  4. Use the Migration Assistance Utility to convert v9 artifacts to v10 artifacts. See Step 4: Run the Migration Assistance Utility.
  5. Review the Migration Assistance Utility log to evaluate the results of the migration. See Step 5: Evaluate the Migration Results.
  6. Use the Packaging Utility to combine your converted v9 artifacts into v10 projects. See Step 6: Run the Packaging Utility.
  7. If necessary, use the Macro Migration Utility to convert v9 macro definition files to the v10 format. See Step 7: Run the Macro Migration Utility,


The following are examples of how to use the Migration Assistance Utility. Note that migrated files are written to the same directory as the original files.

A migration may be set up as follows:

  • The v9 files are located here: C:\test_directory\
  • The Migration Assistance Utility is located here: C:\migration_util\

Use this command to run the migration:

Use this command to migrate files recursively if they exist in subdirectories:

For a more complex example that involves the need for manual changes to convert a v9 artifact, see Example: Migrating a Map with a ChangeSource Action.


  • No labels