Migrate from OptimoRoute to Salesforce Sales Cloud

OptimoRoute stores customer name, email, phone, and address on an order. We split this: company/organization name maps to Account.Name; primary contact name splits to Contact.FirstName + Contact.LastName; email maps to Contact.Email; phone to Contact.Phone. For sole proprietors where no separate company exists, Account.Name uses the contact name as a fallback.

OptimoRoute orders are the core entity. We map them to a custom Route_Order__c object in Salesforce. Standard fields: Order_Name__c (from OptimoRoute order title or address), Status__c (from order status), Priority__c (from order priority), Scheduled_Date__c, Delivery_Window_Start__c, Delivery_Window_End__c. All custom order fields (text, number, single-select) map to corresponding Route_Order__c custom fields with __c suffix.

OptimoRoute orders carry a delivery address (street, city, state, postal code, country). We store these as individual text fields on Route_Order__c: Delivery_Street__c, Delivery_City__c, Delivery_State__c, Delivery_Postal_Code__c, Delivery_Country__c. For geocoding use cases, the latitude/longitude pair from OptimoRoute maps to Delivery_Latitude__c and Delivery_Longitude__c.

OptimoRoute Routes group orders into a planned route assigned to a driver on a given date. We map Route to a custom Route__c object with fields: Route_Name__c, Route_Date__c, Status__c (planned/active/completed), Driver__c (lookup to Driver__c), Total_Stops__c (count), Total_Distance__c, Estimated_Duration__c. Route__c links to Route_Order__c via Route__c on the order.

OptimoRoute Drivers have profiles with name, phone, email, skills, work-hour rules, and vehicle assignments. Salesforce Users are license-bound CRM users, so field drivers map to a custom Driver__c object: Name, Email__c, Phone__c, Skills__c (multi-select text), Work_Hours_Rule__c, Assigned_Vehicle__c. Driver__c is a standalone custom object with no standard Salesforce user license cost.

OptimoRoute records stop-level completion: actual arrival time, completion time, status (completed/skipped/failed), and proof-of-delivery (signature, photo, notes). These map to Delivery_Stop__c linked to Route_Order__c via a lookup: Actual_Arrival__c, Actual_Completion__c, Stop_Status__c, Signature_URL__c, Photo_URL__c, POD_Notes__c. Photos and signatures are re-hosted in Salesforce Files and linked.

OptimoRoute links Order → Route → Driver as a three-level hierarchy. In Salesforce we replicate this with lookup relationships: Route_Order__c has a Route__c lookup, and Route__c has a Driver__c lookup. We resolve the chain during migration by matching Route names and driver emails, then backfill the foreign keys in order.

OptimoRoute supports text (single/multi-line), number (with decimal precision), and single-select custom fields per order. Each custom field requires a corresponding Salesforce custom field on Route_Order__c. Single-select fields need value-by-value pick-list mapping if the source values differ from Salesforce pick-list entries. We auto-create the Salesforce fields from the OptimoRoute field metadata before migration.

OptimoRoute vehicles hold attributes such as name, type, capacity (weight or volume), and features like refrigeration, liftgate, or temperature zones. We map these to a custom Vehicle__c object with fields Name, Vehicle_Type__c, Max_Capacity__c, and Features__c (multi-select text). Vehicle__c links to Driver__c via a lookup and can also be referenced from Route__c, letting dispatchers assign the right vehicle to a route based on load requirements or special equipment needs.

OptimoRoute orders include delivery time windows that specify the earliest and latest acceptable times for a stop. We map these to Delivery_Window_Start__c and Delivery_Window_End__c datetime fields on Route_Order__c, preserving the original timestamps. These fields are informational in Salesforce; the platform does not enforce them. Teams can reference them in reports, build Flow alerts for late arrivals, or feed data into third‑party scheduling tools that respect the constraints.

OptimoRoute orders carry a priority level (e.g., high, normal, low). We map these to a Priority__c pick-list field on Route_Order__c using value-by-value mapping. If OptimoRoute uses custom priority labels, we match them to the closest Salesforce pick-list value or create a custom Priority__c field with the source values.

OptimoRoute enforces routing constraints: orders requiring specific driver skills or vehicle features are matched during route planning. We preserve these as text fields on Driver__c (Skills__c) and Vehicle__c (Features__c). Salesforce does not enforce skill-based routing natively — this data serves as reference for rebuilding routing rules in a third-party dispatch tool.