Migrate from OptimoRoute to Freshsales

OptimoRoute orders reference a customer by name, email, phone, and address. We extract this into a Freshsales Contact record (with email as unique key) and an Account record if the customer has a company name. Address fields map to Freshsales Contact address fields; phone maps to Contact phone.

When OptimoRoute stores a standalone delivery location without a named customer contact, we create a Freshsales Account record with the location address, lat/long preserved in custom fields, and location name as the Account Name.

OptimoRoute drivers are matched to Freshsales users by email. Drivers without email addresses or unmatched emails become Contacts with a custom 'Driver_Origin__c' field set to OptimoRoute and their driver ID stored for reference. Driver skills, shift schedules, and vehicle assignments map to custom fields.

OptimoRoute vehicles (with type, capacity, features, and cost settings) have no native Freshsales equivalent. We create a custom module 'Fleet_Vehicle' with custom fields for vehicle_type, load_capacity, refrigeration_flag, and assigned_driver linking to the Driver/User record.

OptimoRoute routes are optimized execution sequences with driver assignments and stop ordering. Freshsales has no native route concept. We export the route definition as a JSON file and attach it to the relevant Driver/User record as a reference document — the route sequence itself must be rebuilt using Freshsales workflows or a scheduling integration.

OptimoRoute custom order fields (text, number, single-select) map to Freshsales custom fields on the target object. Single-select fields require value-by-value mapping if the pick-list options differ between platforms. Text and number fields map directly by type.

OptimoRoute POD captures signature, photo, and notes at delivery completion. Freshsales has no native POD object. POD data (signature image URL, delivery timestamp, recipient name) is stored as a custom field on the Contact record and original photos are uploaded as attachments.

OptimoRoute orders include delivery/service time windows (start time, end time). Freshsales has no native appointment window field. We preserve these as custom datetime fields (Time_Window_Start__c, Time_Window_End__c) on the Contact record for reference or integration use.

OptimoRoute tracks actual GPS path taken vs. planned route (breadcrumb feature). This execution tracking data has no Freshsales equivalent. We export the breadcrumb data as a CSV attachment on the Driver/User record — analytics on route adherence must be handled outside Freshsales.

OptimoRoute order priority levels (e.g., high, normal, low) map to a Freshsales custom pick-list field (Delivery_Priority__c) with the same values. If OptimoRoute uses numeric priority (1–10), we map to a Freshsales custom number field.

OptimoRoute order statuses (pending, in-progress, completed, failed) reflect delivery state. Freshsales Contact lifecycle stages (New, Active, On Hold) serve as the closest CRM analogue. We map order status to a custom field (Delivery_Status__c) on the Contact record.

OptimoRoute order notes (dispatcher comments, customer instructions) map to Freshsales Contact Notes. Long-form comments with timestamps become Freshsales Tasks or Notes with the original timestamp preserved as a custom datetime field.