Migrate your OptimoRoute data

Orders with time windows, priorities, durations, and skills requirements are migrated directly via OptimoRoute's POST /addOrders JSON endpoint. We preserve all standard order fields and validate constraint compatibility with the destination's optimization engine.

OptimoRoute supports three custom field types only: text (single/multi-line), number (configurable decimal places), and single-select (pre-defined option lists). We identify all custom fields in the source, create them in OptimoRoute under Administration before migration, then map values during order import. Multi-select or date custom fields are flagged as unsupported pre-migration.

Drivers with skills, work-hour schedules, break configurations, and cost parameters are migrated via POST /addDriver. Each driver receives a unique activation code for the driver app which we extract and preserve so re-association on the destination account is straightforward.

Driver skills are migrated as string identifiers and must match OptimoRoute's predefined skill taxonomy. Any custom skills defined in the source system that have no OptimoRoute equivalent are flagged during scoping and mapped to the nearest available skill with customer approval.

Vehicle records including load capacity, size categories, and feature flags (refrigeration, loading ramp, etc.) are migrated via POST /addVehicles. We validate feature names against OptimoRoute's feature set and flag mismatches before writing.

Vehicle features like refrigeration, loading ramp, or custom vehicle attributes must align with OptimoRoute's predefined feature list. Non-matching custom features are remapped to the closest available OptimoRoute feature or promoted as a custom vehicle attribute note on the record.

Routes are generated planning artifacts rather than source data. We migrate completed historical route records as read-only records but do not transfer draft or in-progress route plans. Route assignments (driver-to-route mapping) are recreated from the Orders migration using driver identifiers.

OptimoRoute organizes planning by calendar day, not by multi-day plan sequences. We chunk multi-day route plan exports into individual route objects per day, preserving sequence order within each day's route and attaching the correct date to each route on import.

Completed proof of delivery records — digital signatures, photos, notes, and timestamps — are extracted from completed order records and re-attached to their corresponding orders in OptimoRoute as POD evidence. We extract binary assets from the source and upload them via the driver's completed order record.

Order time window constraints (start time, end time, and service duration) are migrated as native OptimoRoute time window fields. We handle timezone normalization to UTC as OptimoRoute uses UTC internally, so all time window values are converted before import.

OptimoRoute does not support user-defined custom object types beyond custom order fields. Any custom entities or related objects in the source system (e.g., inventory items, service contracts) cannot be migrated as standalone objects and must be handled as custom order fields or documented attachments.

File attachments on orders (e.g., delivery instructions PDFs, reference images) are migrated as file assets attached to the corresponding order record. We support common formats (PDF, PNG, JPG) and flag oversized or unsupported file types before migration.