Salesforce Maps mobile app retires on 31 August 2026 (opens in a new tab)
You will learn that the standalone Salesforce Maps app and Maps Live Tracking Mobile are retired on 31 August 2026, where reps should go instead, and what a self-owned field app would involve.
- 31 Aug 2026: Standalone Salesforce Maps app retired
- 31 Aug 2026: Maps Live Tracking Mobile retired
Salesforce retired the standalone Salesforce Maps app for iPhone and Android on 31 August 2026. Reps now use the Maps tab inside the main Salesforce mobile app. On the same day Salesforce retired Maps Live Tracking Mobile, and live tracking did not move into the main app. Salesforce points to Check-In and Mileage Administration in its place, through third-party products named TripLog and Voze. Desktop Salesforce Maps is unchanged.
The article sets out three options for a field sales team. The first is to stay on Salesforce and move reps to the Maps tab in the mobile app, which suits reps who work in Salesforce all day. The second is to move to a dedicated per-user field tool such as Badger Maps, SPOTIO or Map My Customers, which suits teams where route optimisation and live mapping are central. The third is to own a field app, which the author suggests for teams that visit the same customers on a cycle and take orders and collect payments.
The author’s own product, Beatplan, is presented as the third option. It offers daily visit plans, GPS-verified check-ins with photos, order handling through dispatch and payment, cash and cheque collections, customer balances, and a manager dashboard on iPhone, Android and web. The article is explicit that it has no live location tracking, no route optimisation, no CRM deal pipeline and no Salesforce or Zendesk sync, and that dealer orders need a connection while visits, plans and payments work offline. It is sold once for US$2,900, with hosting from about US$25 a month.
The piece is disclosed as written by a person who works on the product and was produced with AI assistance. Its facts were checked against vendor pages in November 2026, and readers are advised to confirm current vendor documentation before acting.
Read the original at dev.to (opens in a new tab)