Migration Record Mapping Tools

The Record Mapping Rule tool is used to create rules telling CopyStorm/Restore how to map between records in the CopyStorm backup to records in the target Salesforce. This is very useful for migration in mapping Salesforce users and a variety of core Salesforce configuration records.

For example:

  • Mapping Salesforce Users by their email address.
  • Map Record Types based on record type (where the names are not the same in CopyStorm and the target Salesforce).

CopyStorm/Restore includes default mapping rules for a few common tables. However, these rules do nothing by default because no specific mappings are supplied.

Additional tables can be added by clicking on the “Add Record Mapping Rule…” button at the bottom of the tool.

To add or modify the mappings for a specific table, click on the “Edit” button next to its name. A dialog will appear showing existing mappings allow them to be edited or removed and allowing additional mappings to be imported from a CSV file.

When the Save Changes button is clicked, CopyStorm/Restore will validate the mapping rules looking for entries that are missing in either the CopyStorm database or in Salesforce. Though missing entries will be silently ignore during the restore process, cleaning them up is almost always the right choice.

Built in Mapping Rules

In addition to mapping rules provided on the Migration Setup tab, CopyStorm/Restore will always map records using a handful of built-in mapping rules. Mappings on the Migration Setup tab will override the default mappings.

Object Mapping Rule
User Field matching on Email
Profile Field matching on Name
UserRole Field matching on Name
Group Field matching on DeveloperName and Type
RecordType Field matching on Name and SObjectType
  • First map the Standard Pricebook in CopyStorm to the Standard Pricebook in Salesforce
  • Then use field matching on Name
Organization If the CopyStorm database contains 1 Organization, map it to the current User’s Organization.

If this does not map, the CopyStorm database contains conflicting information from multiple Salesforce instances.