We’re Here to Help!!

Find A Solution, Learn Best Practices & Get Support 24x7

Data Migrator User Guide


What is Data Migrator

Data Migrator takes a subset of the data from your production and migrates the data to your sandbox or any other org. In general, Data Migrator can migrate the data between any two orgs (including developer sandbox, partial or full data sandboxes and the production org).

During data migration, Data Migrator can insert or upsert the records in the target org.


Data Migrator is installed in the source org from which the data is migrated. It is not required to install Data Migrator in the target org. Data Migrator moves the data directly from the source org to the target org (without any intermediary platform or system) thus ensuring that your data is safe and secure.

Why is it needed

When Salesforce creates a sandbox for development, it does not include any of the data from your production org. Without proper application data, it is challenging to build and test applications in the developer sandbox. Data Migrator quickly populates records from the source org to the target org.

Typical Steps

  1. Create a Data Set
  2. Create a Sequence
  3. View Record Count
  4. Migrate-Data (Pushes to target Org and asks for username, password & token of the target Org to complete.)

How to create a data set

Data sets are created on top of custom objects and standard objects. Data sets help to select the records from an object that need to be migrated. In other words, Dataset helps to create a smaller set of data for migration. For example, a data set can select all accounts in the state of New York with assets more than $5B. If a filter is defined on a parent object, the filter will also be enforced on the child objects.

Data Sets also help to select the columns that need to be migrated from the source org to the target org.

Finally, if the Dataset is used for upserts, Data Sets also include the information on the primary key of every object. The records defined in the primary key section help to identify records during upserts in the target org.

To begin setup of Data Migrator, you must create an initial Data Set for the parent object you will be adding in Sequences.

Steps To Create Data Set:

  1. Click the Data Sets tab
  2. Click New (or edit if one exists)
  3. Enter the name of the Data Set
  4. Select the object on which you want to create a data set.
  5. Select the fields that you want to migrate from the "Available Fields" section.
  6. Under the Key Set information, select the primary keys for the object. This information is used during upserts. If you leave the Key Set information blank, the data set can only be used for Inserts, not upserts.
  7. Under Data Set Filter, Select the criteria desired
  8. Click save.

How to create a sequence

A sequence is a particular relationship group of custom objects and standard objects that are connected, within your Salesforce org. A sequence is essentially a template that can be defined once, but can be used over-and-over again to migrate the data between the source org and target org. Setting up a sequence allows you to quickly move over the exact data you need, especially on data you plan to move over regularly.

A sequence specifies the order in which the objects are migrated from the source org to the target org. For example, first the data in Accounts object will be migrated, then Contacts, then Contact Roles, etc.

To create a sequence

  1. Go to the Sequences tab, and hit New. 
  2. Enter a name for your sequence. Data Migrator will now cache the objects and relationship between all the objects so that you can easily define the relationship between the data sets.

  3. Select a DataSet from the drop down, and hit Add. 

  4. This will create a data set line. If the object of that data set has child objects, it will show the button for child objects. If the object of that data set has parent objects, then it will show the button of parent objects.
  5. Click on Child objects or Parent Objects button. Chose the child objects or the parent objects that need to be included.

  6. Depending on the objects added to the sequence, the objects will be inserted at the appropriate place in the sequence. If you would like, you can also change the order of the objects in execution.

  7. Flosum recommends developing your sequence iteratively. It is recommended to test your sequence with no more than 2-3 objects first, and then continuously add objects as you develop your sequence.

  8. Hit save.
  9. Hit Migrate Data

You have created your Sequence and it is ready for migration.

View Record Count

Wait! Before you start your migration, you should know the number of records that will be migrated in each level of the hierarchy. Otherwise, you may run out of storage space during the migration.

  1. To see how many records will be moved click View Record Count on the Execution Sequence Detail page.
  2. On the following page, simply hit create after choosing the sequence you wish to check.
  3. The breakdown will now show how many records will be processed for each object.

Migrate Data

If the number of records pulled at each level meet your requirements, you are ready to migrate the data.

  1. Go back to the Sequence
  2. Click on Migrate Data
  3. Data Migrator will request for credentials of the target org. (sysadmin)
  4. Before the migration starts, Data Migrator will ensure that the all the fields and objects are present in the target organization. After ensuring the objects and fields are present, it will ensure that the user has the ability to insert values in those fields and objects.

 Common Tips:

1. Build the sequence iteratively.

2. Dry run the sequence

3. Migrate the data as a System Administrator. It is recommended that you should be logged as a System administrator in the source org as well as the target org.

4. Create the sequence once, and use it over and over again to save time.

Print Friendly and PDF
Was this article helpful?
0 out of 0 found this helpful


  • Avatar
    Donna Vincent

    Can you use lookup or name (autonumber) fields as part of the key set on dataset?