Supported Migration Items
Gainsight NXT
This article lists all items supported by the cross-org migration feature. For more information on the migration process, refer to Cross-Org Migration Overview.
Note: Assets and items related to Data Designer are not supported for Cross-Org migration.
Assets
- This is a list of asset items supported for migration (click to expand).
-
- Rules (Custom and Bionic Rules)
- Reports (reports built off of the scorecard fact object are not supported at this time)
-
Success Plans (fields in Plan Info are not supported at this time)
-
Playbooks
-
Surveys
-
Dataspaces
-
Dashboard
-
Email Templates
-
Scorecards
Items supported in MDA Schema step
- This is a list of supported items available for selection on the MDA Schema step (click to expand).
-
-
Both Redshift and Postgres Custom objects (Low and High Volume Objects) can be migrated.
-
Lookup properties are not migrated and lookup fields are ignored.
-
Update keys configured are not migrated.
-
During migration, field display names will not be changed.
-
Icons are not supported for migration.
-
Only Standard and Custom columns are considered for migrations.
-
During the update, Index property is not copied.
-
During update, the primary property cannot be overridden or copied.
-
During update when the target collection has data already, the default value will not be changed.
-
During update when the target collection has data already, if target column has different maxLength property, the column will be ignored from the update.
-
Formula (or calculated) fields will not be updated. It will always be created as a new field.
-
Support Bulk Insert for Schema and Meta.
-
Custom to Standard object migration - custom objects created in a source org can be migrated to a target org (standard object) using the cross-org migration tool.
- To enable this migration, this parameter needs to be set in the source and target org in the tenantMaster > configs property: "MIGRATOR_ALLOW_STANDARD_OBJECT_MIGRATION" : "true"
-
If you have any schema related to the custom object (in source org), be sure to map it in the MDA Schema step to migrate it to the Target org.
-
Items supported in Metadata Step
This is a list of supported items available for selection on the Metadata step, broken up by section.
Picklist
- This is a list of supported items for all Global, Account, and Relationship Level Picklist Configurations (click to expand).
-
-
CTA Status (Alert Status)
-
CTA Priority (Alert Severity)
-
CTA Snooze Reason (Relationship Activity)
-
CTA Reason (Alert Reason)
-
Customer Status
-
Customer Stage
-
Adoption Measure
-
Milestones
-
GSMetaInfo
- This is a list of supported items for all Account & Relationship Level GSMetaInfo Configurations (click to expand).
-
-
Objective Categories
-
Success Plan Types
-
Task Type
-
Scorecard Metric (Sc Metric)
-
Due Date Source Type
-
Due Date Skip Option
-
Success Plan Status
-
CTA Group Category
-
CTA Types - All the Global, Account, and Relationship Type CTA Types gets migrated.
-
Scorecard Metric - Account level scorecard metrics are migrated.
-
Scoring Scheme Definition - Account level scoring scheme definitions are migrated.
-
Application Settings Definition - While migrating Application setting object, the following properties get migrated.
-
Cockpit Related Configuration Parameters
- Cockpit Configuration (JBCXM__CockpitConfig__c)
-
-
GSRelationshipType - Relationship Attributes and Card View Configuration gets migrated. If you select any metadata related to a Relationship Type will also migrate the Relationship Type. For a Rel Type to get migrated you have to select at least one related metadata.
-
Scorecard Configuration
-
What We Migrate
-
Account level scorecards metrics and scorecard scheme definitions are migrated.
-
Scoring Scheme Mapping - Update the configuration related to whether Color/Number/Grading scheme is enabled.
-
-
What We Don’t Migrate
-
Configuration option “Load Snapshot to Engagement every month” will not get updated.
-
-
-
Picklist/Multipicklist under Schema (Both Standard and Custom) data type. For more on dropdown lists, refer to Dropdown List and Multi Select Dropdown List.
-
URL data type
-
Bulk Insert for Schema and Meta. For more information, refer to the Bulk Insert for Schema and Meta section in this article.
-
Items supported in Choose Assets Step
This is a list of supported items available for selection on the Choose Assets step, broken up by section.
Rules
Custom Rules created on Data Spaces are not supported for migration.
- This is a list of rules assets supported for migration (click to expand).
-
-
MDA Rules
-
Load to MDA action is supported.
-
All the objects used must exist in the target org with the same name.
-
All the fields used in the rule must exist in target org with the exact field name and type.
-
Any lookup object or field used in the rule must have the same lookup object and field in target org.
-
Lookup up to three-levels is supported.
-
-
Bionic Rules can be migrated. Load to Feature and Set Score action type is not supported. If a rule contains this action it will not be migrated.
-
Rules having Set Score as an Action Type can now be migrated.
-
Migrate bucket details for Rules which have an S3 dataset. For more information, refer to the Migrate Rules with S3 Dataset section in this article.
-
Reports
- This is a list of report assets supported for migration (click to expand).
-
-
MDA Reports
-
Orgs must have Integration with HAPostgres.
-
MDA object and its fields get validated during migration. Migration happens only if MDA object is successfully validated.
-
Object validation include ObjectName, used Object fields(fieldName), dataType, and joins.
-
Duplicate Reports of the same name will not be migrated (validation from Report API).
-
-
Data Space Reports
-
Reports of type Data Space, which are present in source and Target org can be migrated.
-
You can also migrate dataspace reports from source to target org directly if it is not present in target org.
-
Reports which can include five level join fields created in data space.
-
If report includes a data space, it will also be migrated.
-
-
Picklist and Multi-picklist values are supported.
-
MDA/Data Space report, if a report with the similar name is already present in target org, it cannot be migrated.
-
An update in data space requires an update in the associated reports, otherwise, the migration will fail.
-
WhoID/WhatID and Record data types can be migrated. For more information, refer to the WhoID/WhatID Data Types and RecordID Datatype sections in this article.
-
Dashboard
- This is a list of dashboard assets supported for migration (click to expand).
-
-
The dashboard is supported in migration.
-
All the dependent reports are also fetched and migrated along with dashboard.
-
If MDA report is already present, then it will be Verified in target org.
-
MDA and Dataspace Reports are supported.
-
If any report fails, the associated dashboard migration fails.
-
Data Space
- This is a list of data space assets supported for migration (click to expand).
-
-
All the dependent reports also fetched and migrated along with dashboard.
-
Unique name constraint applied, so duplicate data space (same name) cannot be migrated.
-
Playbooks
- This is a list of playbook assets supported for migration (click to expand).
-
-
All type of playbooks are supported (Company + Relationship)
-
Playbooks get migrated along with the tasks if all the dependencies are met.
-
Playbooks containing Email type tasks can be migrated.
-
Surveys
- This is a list of survey assets supported for migration (click to expand).
-
-
Multilingual Surveys that include static resources (languages) are now migrated when you are migrating a Survey.
-
Surveys in any stage are migrated to the draft stage in the target org
-