You are here:
Plan Your Salesforce Maps Deployment
Confirm that you have a supported edition, the required licenses, and complete address data before you install Salesforce Maps.
Required Editions
| Available in: Lightning Experience and Salesforce Classic |
| Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions with the Salesforce Maps or Salesforce Maps Advanced license |
Before You Install Salesforce Maps
Prepare your environment and gather this information before you install Salesforce Maps.
- Create a sandbox if you don't already have one, and install Salesforce Maps in a full copy sandbox before you move it to production. Partial copy and Developer sandboxes can have limitations. See the Salesforce Maps sandbox considerations.
- Get the installation URL from your Salesforce Maps order-form email.
- Identify which stock keeping units (SKUs) you purchased.
- Confirm that Salesforce supports your edition and that your org has API access if you need it.
- Check whether your org enforces Proof Key for Code Exchange (PKCE). Create a connected app exception for Maps with your security team before you install. Otherwise, Maps OAuth fails during setup.
- Confirm that address and coordinate data is complete and consistent for the objects you plot. Include street, city, state or province, postal code, and country. Confirm that existing latitude and longitude values are accurate, not 0,0 or placeholder values.
- Identify an implementation owner, a pilot user group, and success criteria.
Environments and Sandboxes
Install and configure Salesforce Maps independently in each org.
- Don't migrate data or configuration between Salesforce Maps environments, for example from sandbox to production. See Salesforce Maps environment migration limitations.
- Match production licenses after a sandbox refresh, or refresh the sandbox before testing. A sandbox refresh doesn't carry over Maps licenses from production.
- Don't push Salesforce Maps data between orgs by using Data Loader or similar tools. Maps stores data across various custom objects. Importing causes configuration and version-compatibility problems. Recreate the Salesforce Maps configuration manually in each environment.
Did this article solve your issue?
Let us know so we can improve!
