Migrate from Route4Me to Twenty CRM

Route4Me addresses are location-centric records containing contact details, company affiliations, and geocoordinates. They map to Twenty's People object for individual contact fields (name, email, phone) linked to a Companies record for the address's organization. Geocoordinates, address alias, and last-visited metadata become custom fields on the People record. Addresses without a named contact land as standalone People records with the address data in custom fields.

Route4Me routes are the core optimization entity — they sequence stops, enforce time windows, and carry scheduling metadata. Twenty has no native route entity, so we create a Route__c custom object in Settings → Data Model. Route-level fields (name, date, status, optimization_level, distance, travel_time, stop_count, service_time_per_stop) become custom fields. The original Route4Me route_id is stored as a custom field (Route4Me_ID__c) for traceability.

Route4Me stop sequences define the ordered list of addresses on a route with arrival times and sequence numbers. Since Twenty's custom objects do not support nested sub-objects, the stop sequence is serialized as a custom long-text field (Stop_Sequence_JSON__c) on the Route__c record. Each entry includes the address reference, sequence position, arrival time, and departure time. Downstream reporting uses the serialized JSON.

Route4Me orders represent delivery or service jobs linked to addresses, contacts, and optionally to routes. Twenty has no native order entity, so we create an Order__c custom object. Order fields (order_number, status, amount, cost, customer_reference, promised_time, completed_time, barcode) become custom fields. Line items are stored as a JSON text field (Line_Items_JSON__c) since Twenty lacks a native order-items sub-object. The address contact link resolves to the migrated People record.

Route4Me drivers are personnel records linked to vehicles and routes. They map to Twenty's People object with a custom type field set to 'Driver' for filtering. Driver name, email, and phone map directly to People fields; driver status, assigned vehicle, license_number, and Route4Me driver_id become custom fields. Drivers without associated People contact data create People records using driver name and email where available.

Route4Me vehicles store capacity, dimensions, and routing constraints. They map to Twenty's People object with a custom type field set to 'Vehicle'. Vehicle ID, name, and type map directly; capacity_kg, capacity_volume, license_plate, and Route4Me vehicle_id become custom fields. Vehicle records are unlinked to People records by default unless a driver assignment in Route4Me creates a natural association.

Route4Me addresses optionally link to a named company entity. We extract the company name from the address record and create or match a Companies record in Twenty, then link the People record via the companyId relation. If no company name exists in Route4Me, the People record is created without a company link. Multi-company affiliations in Route4Me collapse to a primary company link with others noted in a custom field.

Route4Me time-window constraints (earliest_arrival, latest_arrival, service_duration) attach to route stops and route headers. These are preserved as custom datetime and number fields on the Route__c record: Time_Window_Start__c, Time_Window_End__c, Service_Duration_Minutes__c. Each stop's time-window values are embedded in the Stop_Sequence_JSON__c field alongside the address reference.

Route4Me stores optimization algorithm parameters per route: route_type (one-way, round-trip, etc.), optimization_level, distance_unit (miles/km), traffic_mode, and algorithm_hints. These become custom pick-list and text fields on Route__c: Route_Type__c, Optimization_Level__c, Distance_Unit__c, Traffic_Mode__c. The values are copied verbatim; the optimization engine itself does not migrate.

Route4Me attachments (images, signatures, PDFs) on orders and stops migrate as Twenty Notes linked to the corresponding Order__c record. POD images and signature URLs are stored as text URLs in a custom field (POD_URL__c) on the Order__c record. Large files are re-hosted in Twenty's file storage and linked. The original attachment timestamp is preserved in the Note's created_at field.

Route4Me supports user-defined custom data columns on addresses and orders via the custom data API. We extract all custom fields per object, create matching custom fields in Twenty's Data Model under the appropriate object (People, Route__c, Order__c), and map values directly. Field type mapping: text → TEXT, number → NUMBER, date → DATETIME, select → SELECT. Unused custom fields are flagged during audit for exclusion.

Route4Me assigns routes and orders to member/owner accounts. We resolve Route4Me owner email against Twenty workspace members invited via Settings → Members. Matched owners link as the record assignee (assignedTo). Unmatched owners are flagged before migration; their records land under a fallback workspace member or in a custom assigned_to_name field for manual reassignment post-migration.