This article describes the process of migrating Surveys 2.0 using Gainsight's X-Org Migration tool.
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 article.
You can migrate Survey 2.0 and its corresponding Layout from a source org to a target org.
Auto Migration of Dependencies
This section describes the Survey 2.0 dependencies which are auto migrated during a migration process.
- Entity level dependencies will be migrated to destination org. Language Level dependencies
- Dependent objects for transactional surveys.
- Title, Languages, and Logo.
- Thank you message: custom messages, custom pages for Thank you messages, and redirection URL.
- Header and Footer messages.
- All questions including pages, section and all DISPLAY and SKIP logic rules.
- If any logic rules contain custom field attributes based on the company, company person, and relationship person objects; and those fields are not available in the destination org, then the rules will not be migrated.
- To migrate a Relationship Type Survey, you must first migrate the corresponding Relationship Type or create a new Relationship Type with the same name in the target org. If corresponding Relationship Type is not present in target org, the migration job fails.
- Associated Objects are not auto migrated. However, if the corresponding associated object already exists in the target org, it is auto mapped (both SFDC and MDA objects). If the corresponding object does not exist, associated object field of the Survey is set to null, in the target org.
- Logic rule conditions configured to lookup Company or User object are not auto-migrated. An entry for this will be documented in the migration logs.
- Logic rules with matching picklists (based on name) are auto-mapped. However, if a picklist with same name and category is not found in the target org, the picklist is removed from the rule. An entry for this will be documented in the migration logs.
- The Survey questions which are linked to a Library in the source org, will not retain the link after migration.
Migrate Surveys 2.0
To Migrate Surveys 2.0:
- Navigate to Administration > Operations > Migration.
- Select New Migration from the ADD MIGRATION menu.
- Enter a name for the Migration.
- Enter the credentials of the target org.
- Click AUTHENTICATE.
- The Run Delta Process window is displayed. Click RUN, to run the delta process or click CANCEL, to continue with the migration process. The Delta Process will compare your source org (Sandbox) to your target org (Production) and show you the differences and what needs to be migrated.
To learn more about the Delta process, refer to the Run delta process section of the Cross-Org migration article.
- The Assets window is displayed.
- Scroll down and click Survey 2.0. The list of Surveys is displayed.
- Select the check box for the Surveys to be migrated. (here three surveys are selected for migration)
- Click CONTINUE. The Configurations window is displayed.
- (Optional) Select the configurations to be migrated.
- Click CONTINUE. The Objects window is displayed.
- (Optional) Select the objects to be migrated.
- Click CONTINUE.
- Ensure that all the Surveys selected for migration (in the Assets page) are listed (The three surveys selected in Step 9 are displayed here).
- Click MIGRATE. The Migrate window is displayed.
- (Optional) Select the Test Run check box to perform a test migration.
- (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.
- Click MIGRATE. The migration process starts.
The logged in user and the recipients mentioned in Step 18 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 surveys which migrated and which failed to migrate and also the failure reason.