Moving from Salesforce Maps

Salesforce retired two separate things on 31 August 2026, and they are often reported as one.

The standalone Maps mobile app is retired

Salesforce's notice states the app is removed from the Apple App Store and Google Play on the retirement date, and that copies already installed on a phone receive no further security updates, bug fixes or support.

Maps Live Tracking Mobile subscriptions have ended

After the subscription end date, in Salesforce's words, reps can no longer generate new geolocation data. Salesforce points customers towards its included Mileage Administration feature, the Check In feature, or a third party.

Salesforce Maps itself has not been retired

Desktop Maps continues. Territory planning, route optimisation and geographic reporting are all still there, and Salesforce's own guidance is to move users to the Maps Mobile tab inside the main Salesforce mobile app.

So if your team is affected, what you have lost is the dedicated field app and live location tracking, not the mapping product.

Export your tracking history first

Salesforce advises exporting any geolocation data held in Maps Live Tracking object records that you want to keep. Those records are not regenerating and they are not part of a standard account export. If that history matters, export it from Salesforce before anything else. Nothing in this guide brings it back later.

Last checked 3 September 2026, against Salesforce retirement notices 005103356 and 005314199.

You are producing one CSV file of places with addresses. That is all the import needs.

Build the report

In Salesforce, create a report on Accounts, or on Leads if your field team works from leads. Include one row for each physical location you want on the map. If you hold sites, branches or assets on a separate object, report on that instead.

Combine the address into one column

This is the step worth doing properly. Salesforce usually exports an address across separate street, city, state or county, postcode and country fields. Add a formula field to the report that joins those into a single full address column, and export that.

It takes a few minutes and it saves a round of corrections later, because a single complete address geocodes far more reliably than fragments spread across five columns.

Choose the other columns

Keep these:

• The account or lead name. This becomes the name of the place.
• Phone and email where they are useful to someone standing outside the building.
• An identifier you can match on. The Salesforce record ID is ideal. Keep it if you ever want to reconcile the two systems.

Add these if you have them:

• Latitude and longitude. If your records are already geocoded in Salesforce, export the coordinates. They are more reliable than re-geocoding an address, particularly for sites that are not at a normal postal address.
• Owner, territory, stage or segment. Any field you organise by is worth bringing, because it can become a tag or sit in the pin description.

Export it

Export the report as a CSV. If the file is large, split it by owner or by region rather than exporting everything at once.

There is no native Salesforce connection, so nothing gets installed in your org. For most admins that is the faster route anyway: no app to add, no security review and no extra permissions to grant. You export a report, you import a file.

Go to Data, choose Import and upload the CSV. Each row becomes a pin.

Every row needs a name and a way to locate it, either a full address or a latitude and longitude pair. You will be asked to confirm how each column should be read, so you can decide which one is the place name, which holds the location and which should be attached as notes or tags. The full detail is in How do I import from a spreadsheet?

There is no strict limit on how many rows you can bring across, though a very large file takes longer to process and occasionally needs a hand from support.

What comes across

• The places themselves, positioned on the map.
• Standard contact details such as phone and email.
• Any column you choose to map, as a tag or in the pin description. Owner, territory and stage all work well this way.

What does not

This is a CSV import rather than a like-for-like migration of Salesforce Maps, so be clear with your team about what is not coming with you.

• Salesforce Maps territories. Territories are drawn on the map here, so they are set up fresh.
• Live location history. Exported separately from Salesforce, as covered above, and it does not import.
• Salesforce record ownership and sharing rules. Access is set up here from scratch.
• Custom fields as structured data. They come across as tags or description text, not as a matching field for field copy of your Salesforce schema.
• Photos, attachments, activity history and opportunities. Anything that belongs to the CRM record rather than the place stays in Salesforce, which is where it should be.

Four things, in this order, before you invite anyone.

Check the geocoding

Spot check twenty pins across different regions rather than assuming the whole file landed correctly. Rural addresses, industrial estates, new build sites and anything without a full postcode are where accuracy slips. If a batch is wrong, fixing the source column and importing again is faster than editing pins one at a time.

Turn your Salesforce fields into tags

The columns you organised by in Salesforce, such as owner, segment, status or account type, are what your team will filter by on the map. Set those up before people start using it, not after.

Draw the territories

These are drawn rather than imported, so do them once, properly, with whoever owns the patch. It is the one part of the move that takes real thought, and it is also the chance to fix the boundaries everyone has been complaining about.

Then invite the team

A half finished map is the fastest way to lose a field team's confidence in a new tool, and you usually only get one go at that.

Common problems

Pins are landing in the wrong place. The address column is incomplete. Check the report formula is joining every part of the address, or export latitude and longitude from Salesforce and import those instead.

Some rows did not import. Those rows are missing a name or a usable location. Filter the source file for blanks in both columns, fix them, and import again.

There are duplicates. Either the file has been imported twice, or you have both an account level and a site level row for the same address. Decide which level is the map, then import again from a clean file.

Everything is in one long list. No tag column was included. Add one to the CSV and import again, or tag in bulk once the pins are in.