Moving a set of Salesforce records to another org can look like a straightforward export and import. The records already exist, their fields are populated, and their relationships are established. But those records belong to a particular Salesforce org with a specific configuration. The destination may have different fields, different allowed values, and its own version of some of the same records.
A successful migration has to account for those differences. It requires decisions about what each source record should become in the destination, which values should transfer, and how the records should connect after the upload.
Org Loom provides a guided migration flow that takes you through these decisions in the destination org, helping you resolve record matches, field differences, and relationships before uploading.
The destination already has its own data
Consider moving an account, two contacts, and an opportunity into a testing org. The destination already contains the account and one contact. The other contact and the opportunity need to be created.
Importing all four records as new would duplicate information that already exists. Updating everything is not an option either: two records have no destination match. The migration needs a different action for each record.
Finding a match also requires judgment. An account name may return several candidates, and a contact's email address may be missing or shared. A likely match is something to review, not proof that two records represent the same entity.
In Org Loom's migration review, you choose whether to create a new record, update an existing destination record, or exclude it. When updating, Org Loom proposes a match when one is found, but you can also search for a different one. These choices establish which records will be affected by the migration.
A valid source value may not fit the destination
Even after the records are matched, their values may need adjustment. The destination might require a field that was optional in the source, use a different set of picklist values, or store the same information in a differently named custom field.
In the example above, the opportunity's source stage might not be available in the destination. The account might also have a custom field that has no direct equivalent.
Org Loom compares the imported field data with the destination metadata and presents conflicts for review. When reconciliation is needed, you are prompted to supply required values, select applicable record types and picklist values, and map unavailable fields to compatible destination fields.
Relationships need destination records
Moving related records between orgs requires more than copying ID values in lookup fields: the relationships must point to the appropriate records in the destination, which may have different IDs or no ID at all yet.
In our account, contacts, and opportunity example, the destination account could already exist or need to be created. If it already exists, the migrated contacts and opportunity would need to reference that record's ID. If it is created during the migration, they would need its newly assigned ID. Preserving the relationships requires accounting for both possibilities.
Org Loom uses the relationships between canvas records to determine how they should connect in the destination. At upload time, Org Loom dynamically populates lookups to correctly map to new or existing related records. This removes the need to manually locate destination record IDs and substitute them into lookup fields.
Reconcile first, then review the destination canvas
Org Loom allows you to reconcile these decisions before you upload. You prepare a canvas in your source org, export a migration file, and import it into a canvas in the destination org. Org Loom's migration review flow uses that destination org's records, metadata, and your permissions to help resolve migration blockers. The result is a canvas prepared for the destination org, with record matches, field values, and relationships ready for review. This makes migration smoother, with less manual preparation and fewer surprises at upload time.
See the cross-org migration walkthrough for the steps, or get started with Org Loom.