Migrate from Route4Me to Salesforce Sales Cloud

Route4Me has no Salesforce equivalent for routes — a Route is an ordered stop sequence with a driver, vehicle, schedule, and execution status. We create a custom Route4Me_Route__c object in Salesforce holding route name, scheduled date, driver lookup, vehicle lookup, total distance, total duration, and route status (Pending / In Progress / Completed). Stop order is preserved via a sequence integer field on the child Stop custom object.

Each stop on a Route4Me route maps to a Route4Me_Stop__c record with a lookup to Route4Me_Route__c. Fields include: address components, sequence number, scheduled arrival window, actual arrival time, stop status, proof-of-delivery photo URLs, signature URL, and linked Order ID. Stop sequence ordering is stored as an integer field so Salesforce reports can re-order stops correctly.

Route4Me's Address Book holds customer locations with alias, address, email, phone, and custom fields. We split this data: address and company details map to Account, and contact details (name, email, phone) map to Contact with AccountId linking to the parent account. Custom Address Book fields migrate as custom fields on Contact and Account with __c suffix.

Route4Me Members store driver identity, email, phone, vehicle assignment, and routing preferences. The member email is used to attempt a match to an existing Salesforce user or contact. Driver-specific routing attributes (preferred vehicle type, routing constraints) migrate to a custom Route4Me_Member__c object linked to the Contact. Route assignments in Route4Me become custom lookup fields on the child Route object.

Route4Me Vehicles hold license plate, capacity, type (van, truck, car), and telematics link. Salesforce's native Asset object is designed for customer-owned equipment — we map Route4Me vehicles to a custom Route4Me_Vehicle__c object to avoid confusion with customer assets, storing capacity, vehicle type, and telematics URL as custom fields.

Route4Me Orders are linked to stops and carry weight, price, payment status, and revenue data tied to actual delivery. We map Order revenue to the Opportunity Amount field and create a custom Route4Me_Order__c object linked to the Stop record for order-level attributes like weight, price, payment status, and customer reference number that don't fit Salesforce's Opportunity model.

Route4Me notes attached to stops migrate as Salesforce Task records linked to the Route4Me_Stop__c custom object, with Subject set to 'Route Note' and Description carrying the original note text. Original timestamps and owning member are preserved on the Task record. This keeps notes queryable in Salesforce reports.

Proof-of-delivery photos and signature images stored as URLs in Route4Me are downloaded and re-uploaded to Salesforce Files. Each file is linked to the Route4Me_Stop__c record via ContentDocumentLink. If Route4Me URLs are temporary, we capture the file content during the migration window before URLs expire.

Route4Me tracking history is a sequence of geolocation events per route. Salesforce has no native geolocation trail object. We store tracking data as a custom Route4Me_Tracking_Event__c object linked to the parent Route record, capturing latitude, longitude, timestamp, speed, and heading per event. High-volume tracking logs may be summarized rather than fully expanded depending on record count.

User account settings, routing preferences, map layers, notification rules, and display configurations in Route4Me are platform-specific with no Salesforce equivalent. These must be manually re-established in Salesforce's Setup menu or documented as a configuration checklist for your admin team, including profile permissions, field-level security, and page layout assignments specific to route-execution workflows.

Route4Me integrations with telematics providers (Verizon Connect, Geotab, Samsara) and GPS devices are stored as external connection IDs. Salesforce has no native telematics integration — these links must be re-established via Salesforce Maps or a third-party telematics connector after migration.