Skip to main content
Gainsight Inc.

Re-run Migrations

Admins have multiple options to run a migration job with the same configurations as an existing migration. This saves time as you do not have to recreate previous configurations. You can complete a re-run migration with or without a changeset file. For more information on the migration process, refer to Cross-Org Migration Overview.

Re-run

Admins can re-run a migration job with a pre-selected configuration (selection of schema, metadata, and assets) to a different org. For example, if you have run a migration job from Org A to Org B, and wish to migrate the same items from Org A to Org C, you can use the re-run feature to do so. You can use this to run multiple migrations from the same source org to different target orgs without having to remember the items moved in the first migration.

Limitations

  1. Only Insert as new records will be considered for a re-run. 

  2. During a re-run, if the migrator identifies a record as auto-mapped in the current source/target org and the record is set to Insert As new in the job, the record will be ignored.

Use the following procedure to re-run a migration job: 

  1. On the migration list page, click the ellipsis menu for a completed migration task.

  2. Click Re-run. This displays the New Migration screen.

  3. Enter a name for the migration task and the token of the org you wish to target, and click Authenticate. This displays the Assets migration section. 

NXT xorg migration rerun migration.gif

  1. Select the required asset, which could not be migrated previously.

  2. Follow the steps mentioned in the Procedure section and complete the migration task. 

Run a migration job using a Changeset file

Changeset files contain information on the schema, metadata, and assets selected during a migration job. Only the records which are inserted as new in the target org will be captured in the changeset file. If you want to perform migration to a different org with the same schema, metadata, and assets, you can directly upload the changeset file and perform the migration. For example, if you have run a migration job from Org A to Org B, and wish to migrate the new records from Org B to Org C, you can use the changeset file and start the migration with Org B as the source org.

Notes:

  • The changeset file can be downloaded after the migration is completed. 

  • The items selected previously in each step will be shown with an orange dot. 

Use Case (click here to expand)

Large enterprises often have different teams perform multiple practice migrations before migrating to the production org. Changeset files contain pre-selected migration configurations that make it easy for these different teams to hand-off deployment from one team to another.

Limitations (click here to expand)

  1. Only successfully migrated items will be added to the changeset file.  

  2. For MDA Schema and Metadata Selection steps only “Insert as new” records are added to the changeset file. 

  3. Item update scenarios are ignored in the changeset file.

Use the following procedure to run a migration job using a changeset file: 

  1. On the migration list page, click the ellipsis menu for a completed migration task.

  2. Click Download Change Set. A file with .mig extension, is downloaded.

NXT xorg migration download change set.gif

  1. Click ADD MIGRATION and select Upload Change Set. This displays the Upload Change Set window.

NXT xorg migration upload change set.gif

  1. Click BROWSE FILES and select the .mig extension file, in the Upload Change Set window.

  2. After successfully processing the migration file, the new migration screen is displayed with the attached changeset file. Snip20190801_12.png

  3. Follow the steps mentioned in the Procedure section and complete the migration task. 

  • Was this article helpful?