Cross-org Migration FAQs
IMPORTANT: Based on customer feedback, it is important that you have the right level of support from Gainsight to use this feature effectively. If you are interested in leveraging Cross-Org in your implementation migration, please contact your Gainsight Project Manager or Gainsight CSM for more information.
Which assets can I currently migrate?
With the current release, following assets can be migrated:
- Application Settings & Scorecard Configuration (automatic)
- CTA Types, Reasons, Status, etc.
- Milestones
- Relationship Attributes
- Rules (Custom and Bionic) based on SFDC (Call to Action, Load to Relationships, Load to SFDC, Load to Milestones, Load to Usage, Load to Customers)
- Bionic Rules
- Reports
- Surveys
- Surveys 2.0
- Playbooks
- MDA Schema
- Dataspaces
- Powerlists
- Dashboard
What order should I set up the migrations?
|
Order # |
Source or Target |
Description |
|---|---|---|
|
Prior to Migration |
||
| 1 |
Target |
Validate that Gainsight version matches that of Source org |
|
2 |
Target |
Refresh "GS Relationship", "Customer Info", "Contact" , "Account" and any other customer objects from Source org. ** Note: Field Names in Target org need to match Source org |
|
3 |
Target |
Ensure OAuth User has correct permission sets and access to all assets for migration (Including picklists, etc). |
|
Migration #1 |
||
|
4 |
Source |
Add all relevant Master and Detail MDA tables to the Migration Package |
|
5 |
Source |
Add all relevant CTA configurations to the Migration Package |
|
6 |
Source |
(optional) Migrate all Relationship types in Target Org |
|
7 |
Source |
Execute Migration Package #1 |
|
Migration #1 Validation |
||
|
8 |
Target |
Validate that MDA tables, formulas, CTA configurations and Relationships match source org |
|
9 |
Target |
Manually permission MDA Tables for Rules Engine |
|
10 |
Target |
Manually insert records into MDA tables to ensure data and metadata exist |
|
11 |
Target |
Manually create all fields with a lookup and map all lookups (joins) in target org Data Management |
|
Migration #2 |
||
|
13 |
Source |
Add all relevant Account-level and Relationship-level rules to the Migration Package |
|
14 |
Source |
Migrate all Playbooks |
|
15 |
Source |
Add all relevant Dashboards and Reports to the Migration Package ** Note: Reports within a Dashboard will migrate with the Dashboard |
|
16 |
Source |
Execute Migration Package #2 |
|
Migration #2 Validation |
||
|
17 |
Target |
Validate that Rules and Reports migrated successfully with no broken field mappings |
|
18 |
Target |
Manually configure Scorecards to match Source Org |
|
19 |
Target |
Manually configure C360 / R360 layout to match Source Org |
|
20 |
Target |
Manually build Rule Chains |
What if my organization doesn’t have a security token authentication enabled?
The Security Token is optional for organizations that have this feature disabled.
If I make a change to an asset in the Source org, how will these changes migrate to the Target org?
Rule & Playbook assets will be duplicated in the Target org and you will need to delete the original asset if it is no longer needed.
Which SFDC permissions are required to use the Cross-org Migration tool?
The Gainsight Admin permission set is required to use Cross-org migration tool. For more information on permission sets, see Gainsight and SFDC Permission Sets.
In which scenarios are Custom rules not migrated with the Cross-org Migration tool?
Rules are not migrated when they contain the following action types:
- Actions for Account based rules
- Load to Feature
- Set Score 1.0
- Actions for Relationship-based rules
- Set Score
- Load to Relationship Related Object
- Success Plan
For more information on supported items, see Cross-org Migration.