Migrate from Route4Me to Microsoft Dynamics 365 Sales

Route4Me address-book entries map directly to Dynamics 365 Sales Account records. Each address becomes an Account with address fields populated from Route4Me's address columns. Geocoordinates from Route4Me require custom lat/lng fields in Dynamics 365. We match Route4Me addresses to existing Accounts by domain or name when duplicates exist.

Route4Me addresses that represent individual contacts (customer name, personal email) map to Dynamics 365 Sales Contact records. The Contact links to its primary Account via the AccountId lookup. Phone, email, and job title transfer as direct field maps when populated in Route4Me.

Route4Me orders map to Dynamics 365 Sales Order records. Each Order links to the Account representing the delivery destination. Order number, total amount, scheduled date, and status all transfer as direct field maps. Route metadata (stop sequence, vehicle ID) becomes custom fields on the Order entity since Dynamics has no native route concept.

Route4Me order-status values (Possession Scan, Sorted, Scheduled, Accepted, Routed, Loaded, Completed, Canceled) map to Dynamics 365 Sales order-state pick-list values using Route4Me's documented status-mapping matrix. In-flight statuses like 'Routed' and 'Loaded' map to Active; Completed maps to invoiced; Canceled maps to Canceled. We validate each mapping against the matrix before migration.

Route4Me custom fields on orders map to custom fields on the Dynamics 365 Sales Order entity. Field type is preserved (text, number, date, pick-list). Dynamics 365 Sales custom fields require creation via solution or Power Apps maker before data loads — we deliver a schema setup plan listing each custom field with its type and target entity.

Route4Me member records representing drivers map to Dynamics 365 Sales SystemUser records. Matching happens by email address when a driver has a user account in the target Dynamics 365 environment. Drivers without Dynamics accounts are flagged for your admin to create users before migration so order ownership resolves correctly.

Route4Me vehicle records have no native equivalent in Dynamics 365 Sales. We create a custom Vehicle table via solution.xml or the Power Apps maker interface. Vehicle fields (license plate, capacity, type) map to custom columns on this table. Order records then link to the Vehicle via a lookup field added during migration setup.

Route4Me route metadata — route name, stop count, total distance, optimization algorithm used — distributes across multiple custom fields on the Order entity in Dynamics 365 Sales. Stop sequence order is preserved as a custom integer field (Stop_Sequence__c). The route's optimization constraints (time windows, vehicle capacity) become custom fields that your team can use for rebuild planning in Power Automate.

Route4Me proof-of-delivery files — signatures, photos, barcode scans — attach to the corresponding Order record in Dynamics 365 Sales as Notes with the filename and file content. Each proof-of-delivery note links to the Order via the ObjectId lookup. We handle the file-size validation; files exceeding Dynamics 365's default 10MB limit are flagged for manual review.

Route4Me GPS tracking data per stop maps to custom lat/lng fields (Last_Known_Location_Lat__c and Last_Known_Location_Lng__c) on the Order record. Route4Me stores per-stop coordinates; we map the final stop's coordinates to the Order for delivery completion reporting. Full location history remains in Route4Me's tracking export for audit purposes.