Migrate from Route4Me to HubSpot

Route4Me address book entries map directly to HubSpot Contacts. Address components (street, city, state, ZIP, country) map to HubSpot's standard address properties. Custom data columns attached to the address (alias, customer email, order reference) migrate as HubSpot custom contact properties.

Route4Me Orders become HubSpot Deals. The order number and name map to Deal name. Order total or delivery fee maps to Deal amount. Custom order fields (weight, delivery window, priority flag) translate to HubSpot custom properties on the Deal object.

Each Route4Me Order Custom Field requires a corresponding HubSpot custom property on the Deal object. We create these custom properties before import using HubSpot's Properties API, matching the field type (string, number, date, picklist) from Route4Me's v5.0 custom field definitions. Picklist values are translated one-to-one to maintain consistency across the migration.

Route4Me Routes have no direct HubSpot CRM equivalent. Route metadata including route name, date, and assigned driver migrates as a HubSpot Note attached to the related Contact or Deal record. Individual stop completions surface as engagement timestamps on the Contact record for historical reference.

Route4Me stop-level notes including proof of delivery comments and customer instructions map to HubSpot engagement notes. Original timestamps and the stop address are preserved in the note body or stored as custom properties on the engagement record for complete traceability.

Route4Me Members and Drivers are team resources, not CRM contacts. If your team needs to track driver performance against deliveries, we create a Contact record with a custom 'Driver_Role__c' property set to 'Field Driver'. Vehicle assignments remain in a separate Custom Object.

HubSpot has no native vehicle object. We create a Route4Me_Vehicle__c Custom Object with fields for vehicle name, capacity, and assigned driver. The custom object is associated to Contact records for the driver and to Deal records for deliveries using the association API.

Route4Me Address Groups organize addresses into named lists for dispatch purposes. HubSpot Lists serve a different purpose focused on marketing segmentation rather than route dispatch grouping. We map address group membership as a custom contact property ('Route4Me_Group__c') rather than attempting to recreate the original grouping logic.

Route4Me order statuses (Pending, In Transit, Completed, Cancelled) map to HubSpot Deal stages. We create a Deal pipeline with stages matching your Route4Me status values so deal history reflects the delivery lifecycle. Stage transition timestamps are preserved as HubSpot Deal activity.

Route4Me's real-time GPS tracking and route analytics are telematics data with no HubSpot equivalent. We export stop completion times and actual arrival timestamps as custom datetime properties on the related Deal, preserving operational evidence without migrating the live tracking feed.

Route4Me spreadsheet imports support custom columns beyond the standard address fields. Any custom column you used to attach order references, customer notes, or delivery instructions becomes a HubSpot custom contact property. We map these column-by-column before the import run to ensure all custom data transfers correctly.