Quickly move metadata and configuration data from your current Salesforce org to a
target org in a single orchestration. This type of direct deployment from DX Inspector is ideal
for moving small, specific changes without using a full DevOps pipeline.
Required Editions
Available in: Lightning Experience
Available in: Professional, Enterprise, Performance,
Unlimited, and Developer Editions
This feature deploys metadata first and then the related data. It retrieves selected records
from the source org and migrates them to the target org. To maintain data integrity, it
migrates records based on their relationships. For example, the feature migrates parent
records first to capture their new record IDs, and then it migrates and maps child records to
the correct parent records by using these IDs. If external IDs are present, they’re used to
upsert records, preventing duplicates and ensuring existing records in the target org are
updated with the latest changes.
Use Cases
Move configuration data, such as objects containing product catalogs and business rules,
between environments.
Deploy a new feature from a development sandbox to your production org after development
and testing are complete.
Develop and test changes in a scratch org, and then move them to a sandbox for further
integration. Seed the sandbox with specific data for validation.
Move metadata and data between developer sandboxes to integrate changes from different
team members. This action is useful for moving a combined feature set to a shared sandbox
for User Acceptance Testing (UAT).
Deploy the final set of customizations to a staging or preproduction environment and
populate it with realistic data that mirrors production for final testing.
Set up new environments, refresh sandboxes with production data, or move configuration
records.
Plan and Prepare for Deployment A successful deployment starts with a solid plan. To avoid conflicts or missing dependent metadata and configuration data during deployments, review these prerequisites, best practices, and limitations.
Working with Metadata and Data Dependencies Identify, map, and visualize the relationships between metadata components and data records in your org. You can view dependencies early to select all required metadata and data before deployment, which prevents deployment failures.
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
Always Active
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
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
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.