
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
This article explains the availability of metadata migration between organizations and environments using Data 360 Data Kits (Standard / DevOps), as well as the limitations of each migration method, including Package Manager, Change Sets, and Salesforce CLI. Supported tools and key considerations vary depending on the combination of Production and Sandbox environments.
When migrating metadata across environments using Data 360 Data Kits, the available migration methods and availability vary depending on the combination of the source and target environments, as well as the type of Data Kit (Standard / DevOps).
The compatibility and considerations for each migration method (Package, Change Set, Salesforce CLI) for each environment combination are as follows. The same conditions apply to both directions for "Production ⇔ Sandbox" migrations.
|
Environment Combination |
Data Kit Type |
Use of Package |
Use of Change Sets |
Use of Salesforce CLI |
Remarks |
|---|---|---|---|---|---|
|
Production ⇔ Production |
Standard |
Available |
Not Available |
Not Available |
Migration is supported only from the default data space using Package Manager. |
|
Production ⇔ Production |
DevOps |
Not Available |
Not Available |
Available |
Change Sets cannot be used due to connection restrictions between organizations, but migration via direct metadata deployment is possible using Salesforce CLI. |
|
Production ⇔ Sandbox |
Standard |
Available |
Not Available |
Not Available |
Deployment is also possible to Sandboxes with different source organizations. Migration is supported only from the default data space using Package Manager. |
|
Production ⇔ Sandbox |
DevOps |
Not Available |
Available |
Available |
Change Sets can only migrate between Sandboxes created from the same Production environment. |
|
Sandbox ⇔ Sandbox |
Standard |
Available |
Not Available |
Not Available |
Migration is supported only from the default data space using Package Manager. |
|
Sandbox ⇔ Sandbox |
DevOps |
Not Available |
Available |
Available |
Change Sets can only migrate between Sandboxes created from the same Production environment. |
Depending on the components included in the data kit or the type of data being migrated, certain patterns may not migrate correctly. Please also review Data 360: Data Kit Considerations & Common Issues for detailed considerations and common issues.
If any unresolved issues occur, such as a deployment failure in a specific part during the migration process, please contact the Support Center.
005385637