Skip to main content
Gainsight Inc.

Migrate C360/R360 Layouts

Overview

X-Org is Gainsight's migration tool which can be used to migrate data from a source object to a target object. (Source object can be a sandbox org and target object can be a production org). To learn more about the X-Org tool refer the <<Cross-Org Migration>>TBH article.

You can migrate C360 and R360 Layouts from a source org to a target org.

Auto Migration of Dependencies

When a 360 Layout is migrated, all assets dependent on the layout, including any associated reports, are also migrated automatically.

Limitations

If the layouts contain a report you also wish to migrate, the report needs to be migrated to the target org before, or at the same time as, the layout migration. If the report is migrated to the target org after the layout migration, the layout will not contain the report.

Migrate C360/R360 Layouts

To Migrate C360/R360 Layouts, take the following steps:

Setup Migration

  1. Within the target org, navigate to Administration > Operations > Migration.

  2. Click GENERATE TOKEN.

  3. Enter the Tenant Id of the source org.

  4. Click GENERATE TOKEN.

  5. Click the copy icon to copy the token and click CLOSE.

Note: If you have already generated the token for the source org target org, you can use the existing token.

migrate 360 layout generate token.gif

  1. Within the source org, navigate to Administration > Operations > Migration.

  2. Select New Migration from the ADD MIGRATION menu.

  3. Enter a name for the Migration.

  4. Enter the Migration Token.

  5. Click AUTHENTICATE. This will dispaly the Migration Assets window.

authenticate migration.gif

For steps on selecting C360 Layouts for migration, navigate to Select C360 Layouts. For steps on selecting R360 Layouts for migration, navigate to Select R360 Layouts.

Select C360 Layouts

  1. From the Select Entity Type drop-down menu, select Company.

  2. Select C360 from the left column. A list of C360 assets is displayed, including C360 Layouts.

  3. Select the check box for the layouts you wish to migrate.

migrating 360 layout asset selection 2.gif

For steps on selecting R360 Layouts for migration, navigate to Select R360 Layouts. For steps on completing the migration, navigate to Continue Migration.

Select R360 Layouts

  1. From the Select Entity Type drop-down menu, select the Relationship Type associated with the R360 Layouts you wish to migrate.

  2. Select R360 from the left column. A list of R360 assets is displayed, including R360 Layouts.

  3. Select the check box for the layouts you wish to migrate.

migrating R360 assets selection.gif

For steps on selecting C360 Layouts for migration, navigate to Select C360 Layouts. For steps on completing the migration, navigate to Continue Migration.

Continue Migration

  1. (Optional) Select any remaining assets to be migrated.

  2. Click CONTINUE. The Configurations window is displayed.

  3. (Optional) Select the configurations to be migrated.

  1. Click CONTINUE. The Objects window is displayed.

  2. (Optional) Select the objects to be migrated.

  3. Click CONTINUE. The Summary window is displayed.

  4. Review the summary and ensure that all the layouts selected for migration on the Assets page are listed.

  5. Click MIGRATE. The Migrate window is displayed.

  6. (Optional) Select the Test Run check box to perform a test migration.

  7. (Optional) Select the Send Copy of  Migration Status Email check box and provide recipient Email IDs to whom the migration results must be mailed. By default, only the logged in users receive a copy of migration status mail.

  8. Click MIGRATE. The migration process starts.

migrate 360 layouts completing migration.gif

When the migration is complete, the logged in user and recipients whose Email IDs were added to the Send Copy of  Migration Status Email check box, will receive an email which shows the results of the migration task. You can view the Assets tab of this report to check the number of layouts which successfully migrated, as well as the number of layouts which failed to migrate, including their failure reason.

Snip20190715_8.png

  • Was this article helpful?