Migrating Relational Datasets with Snapshot

Snapshot is a powerful tool for migrating metadata and data between organizations. This technical documentation outlines the steps to efficiently transfer relational datasets between organizations using Snapshot.

Step 1: Connect to Snapshots

Connect two organizations through Snapshot by creating a deployment arrow. This connection enables the transfer of data and metadata between the source and destination organizations.

Step 2: Build a Dataset

Right-click on the deployment arrow and select the option to build a dataset from the source organization.

2.1 Select Objects

You can select custom or regular objects for migration. Selection can be done by object names, through filters, or by selecting all records.

2.2 Select Child Objects

Select child objects that are connected to the parent object. For example, if you are transferring account data, you can also choose to transfer connected contacts and opportunities.

2.3 Select Fields

Choose the fields within the objects that you want to include in the dataset. By default, all fields will be selected.

2.4 Build Dataset

Click the “Build Dataset” button. Snapshot will use the Bulk Data API to gather the selected objects and their related child objects and fields. Once complete, Snapshot will display the total number of records gathered in the dataset (e.g. 4,000 accounts, 300 contacts, and 1,200 opportunities).

Step 3: Migrate the Dataset

Right-click on the deployment arrow and choose “Migrate Data Sets” to begin the transfer process to the destination organization.

3.1 Review Fields

Review the fields in the dataset by either field name or object name.

3.2 Select Matching Fields

Choose fields that will be used to match records between the source and destination. For example, for accounts, you might match by name and postal code to ensure that records with duplicate names but different locations are matched correctly.

3.3 Data Scrambling (Optional)

For privacy reasons, especially when moving data into a developer or testing environment, you can choose to scramble certain fields, such as amounts in opportunities.

3.4 Deactivate Rules and Triggers (Optional)

To prevent interference from triggers, validation rules, workflows, and flows during complex deployments, you may opt to temporarily deactivate them for the objects being migrated.

3.5 Migrate Dataset

In the last tab, choose how the data should be migrated:

• Error Handling: Choose to stop after an error or continue.
• Field Truncation: Choose to allow or disallow field truncation if the fields are smaller in the destination.
• Logging: Log errors only or both errors and successes.
• Data Transfer Mode: Choose between parallel or serial data transfer.

Click to start the migration. Snapshot will first migrate the parent object (e.g. accounts) followed by the child objects (e.g. contacts, opportunities).

Step 4: Review Migration Results

Once the migration is complete, Snapshot will display the results. If there are any records that could not be migrated due to errors, this information will be available in the migration errors log. The tool ensures that relationships between objects are maintained and properly reconnected in the destination organization. Snapshot not only helps in migrating data but also in preserving the relationships among the data objects, making it an invaluable tool for efficient and secure data migration across different organizations.