Loading

Migrating Salesforce Maps, Territory Planning & Sales Planning Data Across Salesforce Organizations

Julkaisupäivä: May 12, 2026
Kuvaus

You may want to transfer your SPM (Salesforce Performance Management - Maps, Territory Planning and Sales Planning) data from one Salesforce organization to another. We commonly see this with Salesforce organizations that want to transfer Salesforce Maps Marker Layers, Shape Layers, Alignments, Segments and other data from one organization to another. For example, you may want to transfer Salesforce Maps Production data to a Sandbox organization.

Ratkaisu

As a Salesforce Admin, you may be thinking, "I can export SPM records with their associated data. I can import these records with the Data Loader. Therefore I can import them back into Salesforce Maps, Territory & Sales Planning in another Salesforce org."

However, it is recommended that you recreate your SPM data by hand. There are several reasons for this:

  • Salesforce Maps stores data on over 40 custom objects. To import them, you would need to import over 40 custom objects one by one. This would be fairly time-consuming.
  • Attempting to import custom objects may cause issues with your Salesforce org. If the underlying Salesforce records are even slightly different, there may be configuration issues (with custom objects, custom latitude/longitude fields, the Map It button, and so on).
  • There are version issues we cannot know ahead of time. For example, Sandbox organizations may get newer releases of Salesforce Maps than Production organizations. Depending on the features we add, the new object structure may not work with the older version of Salesforce Maps (or vice versa).

You can get guaranteed compatibility by recreating your SPM data. We advise that you avoid trying to export and import custom objects.

Knowledge-artikkelin numero

000381128

 
Ladataan
Salesforce Help | Article