Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Enable Dev Hub Features in Your Org
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Development
Develop Against Any Org
Assign a Permission Set
Ways to Add Data to Your Org
Example: Export and Import Data Between Orgs
Create Lightning Apps and Aura Components
Create Lightning Web Components
Create an Apex Class
Create an Apex Trigger
Run Apex Tests
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Example: Export and Import Data Between Orgs

Let’s say you’ve created the perfect set of data to test your application, and it currently resides in a scratch org. You finished coding a new feature in a second scratch org, pushed your source code, and assigned the needed permission sets. Now you want to populate the scratch org with your perfect set of data from the other org. How? Read on!
This use case refers to the Broker and Properties custom objects of the Salesforce DreamHouse LWC application example on GitHub. Let’s say that the scratch org from which you want to export data has the alias org-with-data. Similarly, the scratch org into which you want to import data has the alias org-needs-data. For the org-with-data scratch org, it’s assumed that you’ve already:
  • Created the Broker and Properties custom objects by pushing the DreamHouse source.
  • Assigned the permission set.
  • Populated the objects with the data.
For the org-needs-data scratch org, however, it’s assumed that you’ve created the Broker and Properties objects and assigned the permission set but not yet populated the objects with data.

See the README in the dreamhouse-lwc GitHub repo for instructions on these prerequisite tasks.

  1. Export the data from the org-with-data scratch org.
    Use the force:data:soql:query command to fine-tune the SELECT query so that it returns the exact set of data you want to export. This command outputs the results to your terminal or command window, but it doesn’t generate any files.

    Because the SOQL query is long, the sample command is broken up with backslashes for easier reading. You can still copy and paste the command into your terminal window and run it.

    Note

    1sfdx force:data:soql:query -u org-with-data --query \
2      "SELECT Id, Name, Title__c, Phone__c, Mobile_Phone__c, \
3              Email__c, Picture__c, \
4       (SELECT Name, Address__c, City__c, State__c, Zip__c, \
5               Price__c, Beds__c, Baths__c, Picture__c,  \
6               Thumbnail__c, Description__c \
7        FROM Properties__r) \
8       FROM Broker__c"
  2. When you’re satisfied with the SELECT statement, use it to export the data into a set of JSON files. 
    1sfdx force:data:tree:export -u org-with-data --query \
2      "SELECT Id, Name, Title__c, Phone__c, Mobile_Phone__c, \
3              Email__c, Picture__c, \
4       (SELECT Name, Address__c, City__c, State__c, Zip__c, \
5               Price__c, Beds__c, Baths__c, Picture__c,  \
6               Thumbnail__c, Description__c \
7        FROM Properties__r) \
8       FROM Broker__c" \
9     --prefix export-demo --outputdir sfdx-out --plan

    The export command writes the JSON files to the sfdx-out directory and prefixes each file name with the string export-demo. The files include a plan definition file, which refers to the other files that contain the data, one for each exported object (Broker and Properties).

  3. Import the data into the org-needs-data scratch org by specifying the plan definition file. 
    1sfdx force:data:tree:import -u org-needs-data \
2    --plan sfdx-out/export-demo-Broker__c-Property__c-plan.json

    Use the --plan parameter to specify the full path name of the plan execution file generated by the force:data:tree:export command. Plan execution file names always end in -plan.json.

Example

Looking for a more complicated example? The easy-spaces-lwc sample app has a data plan showing how to import Accounts, related Contacts, and a 3-level deep custom object chain.