Tourvia Tourvia
Docs Request trial
News · 6 min read

Salesforce Maps mobile app is retiring. What field teams should do now.

Salesforce announced the retirement of the Salesforce Maps mobile app, effective August 31, 2026. For field sales teams relying on mobile route planning, this means a forced migration. We explain the timeline, what changes, and which alternatives keep your routes inside Salesforce.

Salesforce-native managed package€30/user/month, billed annually30-day trial

What exactly is retiring?

On August 31, 2026, the Salesforce Maps mobile application will reach end-of-life. After that date, the mobile app will no longer receive updates, support, or critical fixes. The desktop Maps components inside Salesforce are not affected in the same way, but the mobile experience — the one field reps use every day to check routes, log visits, and update records on the road — is gone.

Salesforce recommends moving to alternative solutions for mobile route planning and field execution. The window to plan, test, and migrate is short.

Why this matters for field sales teams

Most Salesforce Maps users bought the product for two things: route planning and mobile execution. The mobile app retirement removes the second half of that value. Reps who relied on Maps to plan their day, navigate between accounts, and check in will lose that workflow unless the org migrates to another tool.

The risk is not just technical. A forced migration in September means training, data cleanup, and reconfiguration while reps are trying to hit quota.

What to look for in a replacement

A good replacement should cover four things that Salesforce Maps mobile did:

Salesforce Maps alternatives that still have a mobile app

The main alternatives fall into two groups: Salesforce-native managed packages and external route planning tools.

Native options run inside Salesforce, keep the CRM as the system of record, and require less data synchronization. External tools may have stronger route optimization, but they force reps to switch apps and they create integration overhead.

For teams that need both mobile and Salesforce-native, the short list is small. Tourvia is one of the few options delivered as a Salesforce managed package with its own mobile experience.

How to plan the migration before August 31

A clean migration in six weeks is possible if you keep the scope tight:

  1. Audit your current Maps usage: which users, which objects, which workflows.
  2. Identify the minimum viable route inputs: Accounts, Contacts, Leads, Opportunities, or Campaign Members.
  3. Test one alternative in a sandbox with a pilot group of three to five reps.
  4. Compare the annual cost of each option against your current Salesforce Maps contract.
  5. Roll out in phases: power users first, then the rest of the team.
  6. Train reps on the new mobile app before the old one stops working.

How Tourvia fits the replacement checklist

Tourvia is a Salesforce managed package. It runs inside your org, uses your existing records, and includes a mobile app for field reps. It does not require an external sync. Pricing is published: €30 excluding tax per licensed user per month, billed annually.

If your team is evaluating replacements because of the mobile retirement, Tourvia offers a 30-day trial so you can test the route-to-visit workflow with your own data before making a decision.

Request a 30-day Tourvia trial

Test Tourvia in your Salesforce org for 30 days. Pricing is €30 excluding tax per licensed user per month, billed annually.

Request a 30-day trial See pricing →

Next pages for evaluation