Migrate from Route4Me to monday CRM

Route4Me address book entries with customer name, email, phone, and address components migrate as monday CRM Contacts. When a Route4Me address entry has no contact email (e.g., a delivery-only location), it lands as an Item on a custom monday CRM Address Board with name, location, and alias columns.

The Route4Me address alias field (e.g., 'Store #42 — Back Entrance') maps directly to the monday CRM Contact Name field or to a custom Alias text column on the Address Board Item, preserving the human-readable label your dispatchers use. The alias also surfaces on the Route Board Item and Subitems, giving drivers an immediate visual cue at each stop.

Route4Me stores latitude and longitude per address. monday CRM's Location column accepts lat/lng pairs and renders them on a map within the board. Both values migrate intact, preserving the geocoded position for route planning reference in monday. The coordinates can be used by map widgets or third-party integrations to compute distances, plan detours, or display stops on a visual route overview.

Route4Me routes have no direct CRM equivalent in monday CRM. We map each route to an Item on a dedicated monday CRM board, with route name, status, planned distance, planned stop count, and driver assignment stored as Columns. The optimization sequence itself requires monday-side rebuild using monday's native ordering.

Route4Me stop sequence and arrival timestamps map to monday CRM Subitems on the Route Board Item, linked to the parent route. Each Subitem stores the address (linked Contact), sequence number, planned arrival time, and status. Actual arrival times are preserved as custom datetime columns.

Route4Me orders map to monday CRM Deals (Pipeline Items) with order name as Deal name, order amount as Deal value, and order status mapped to the monday CRM Pipeline status column. The associated address becomes the linked Contact on the Deal.

Route4Me order custom fields require new monday CRM columns created before migration runs. Order weight maps to a Number column; delivery instructions maps to a Text column; notes map to a long-text Notes column. We generate a column-creation plan per monday CRM board based on the Route4Me custom field inventory.

Route4Me member records (driver name, email, phone) migrate as monday CRM Contacts stored on a separate Drivers Board. Custom columns added for driver phone, license plate, vehicle type, and Route4Me member ID preserve the full driver profile without conflicting with customer Contacts.

Route4Me vehicle records (plate, type, profile ID) migrate as monday CRM Items on a Vehicles Board with custom columns for plate number, vehicle type, and Route4Me vehicle ID. monday CRM has no native vehicle object; the Vehicles Board is a flat-item board with standard monday columns for name, status, and custom vehicle fields.

Route4Me stop-level notes and proof-of-delivery records migrate as monday CRM Notes column text on the Route Subitem. Photo attachments download from Route4Me and re-upload as monday CRM Files linked to the Subitem, preserving POD evidence in the destination. The Notes column also captures driver comments, timestamps, and any inline flags, while the file column retains the original file name and upload date for auditability.

Route4Me generates real-time GPS tracking URLs per route. monday CRM has no native tracking URL field. We preserve the Route4Me tracking URL as a Read-only text column on the Route Board Item so your team can still access live tracking until you rebuild the integration with a monday-compatible GPS connector.