Migrate from Route4Me to Mailchimp

Route4Me address book entries map directly to Mailchimp contacts. Each address record contains a customer name, email, phone, and address fields that correspond to Mailchimp's standard contact fields. Route4Me's alias, customer email, and order-number fields migrate as merge fields. Addresses without an email address cannot become Mailchimp contacts and are flagged for manual email address collection.

Route4Me allows per-address custom fields beyond the standard columns. These map to Mailchimp merge fields on the contact record. Mailchimp enforces a 30-character merge field name limit and only supports text, number, date, phone, address, or URL types — checkbox and dropdown types from Route4Me are converted to text merge fields with the original values preserved as strings.

Route4Me routes group ordered sequences of address stops. Mailchimp has no route object. We preserve route context by creating a tag per route name (e.g., 'Route: Downtown Monday') and applying it to all contacts that were stops on that route. This lets you segment by delivery area or service day in Mailchimp after migration. Route optimization parameters (time windows, priority scores) are not preserved as Mailchimp lacks equivalent fields.

Route4Me stores the junction between an address and a route with metadata: stop sequence number, customer notes, and arrival time. We map the stop sequence number and customer notes to contact-level merge fields (Stop_Sequence__c, Customer_Note__c) and apply the route's tag to the contact. The arrival time is stored as a text merge field since Mailchimp has no native event-timestamp model for contacts.

Route4Me orders are attached to addresses with fields like order ID, status, service type, weight, and scheduled date. Mailchimp has no order object — order data is flattened into merge fields on the contact record (e.g., Last_Order_ID__c, Last_Order_Status__c, Last_Service_Type__c). We preserve the most recent order per contact; full order history is summarized in a text merge field if space allows within Mailchimp's field limits.

Route4Me's user-defined order fields (checkbox, dropdown, text) require Mailchimp merge fields to be created before migration. Each custom field in Route4Me becomes one merge field in Mailchimp. Mailchimp's cap of approximately 40 merge fields per audience may require field consolidation for Route4Me setups that exceed this — the highest-priority fields are migrated first and the rest are documented for manual entry.

Route4Me members (drivers, field agents) have their own records with name, phone, and email. These can be mapped as Mailchimp contacts if the member list represents customers to be marketed to, or as tags applied to customer contacts if members are operational staff. Driver ID, vehicle assignment, and member notes are stored as merge fields. If the member is not a marketing contact, the record is excluded and the association is noted in the migration report.

Route4Me vehicles (with license plate, vehicle type, capacity) have no equivalent in Mailchimp's contact model. We map vehicle type to a text merge field on the member contact record. Vehicle capacity, GPS unit ID, and other operational vehicle attributes are excluded as Mailchimp has no place to store them. The mapping is documented for any future CRM integration that would carry vehicle data.

Route4Me tracks route-level activities (customer calls, emails, visits) with timestamps and notes. Mailchimp has no activity log per contact. We summarize the most recent activity type and timestamp in a text merge field (Last_Activity__c). Full activity history is excluded as Mailchimp's contact model does not support a chronological activity feed.

Route4Me stores file attachments (JPG, PNG, BMP) linked to stops or orders as proof-of-delivery or scanned document records. Mailchimp does not host binary file attachments on contact records. Photos and scanned documents cannot be migrated. URLs to Route4Me-hosted files, if still accessible, can be stored as URL-type merge fields as a reference link. This is disclosed as a data-loss gotcha before migration commits.