Migrate your Route4Me data

Routes are Route4Me's primary scheduling container. Each Route holds an ordered sequence of Addresses (stops) with time windows, optimization status, and assigned Driver/Member. We export Routes as CSV with customizable columns, preserving the stop order, time windows, and status. Route Map images and route attachment bundles are exported as linked files.

Addresses are the atomic location records within Routes. Each Address carries geocoded coordinates, alias, customer email, phone, order weight, and custom fields. The Address column is mandatory in spreadsheets; Route4Me will suggest geocoded versions for partial entries. We preserve all address fields and their associated custom properties during migration.

Members are Route4Me's internal user accounts. Each Member can be assigned as an Owner on Routes and Drivers. Member records include name, email, role, and team association. We migrate Members 1:1 and map them to corresponding user objects in the destination platform.

Drivers are the operational entities that execute Routes. Each Driver record links to a Member, a Vehicle, and a route schedule. Driver records carry telematics device ID, start/end depot location, and service time per stop. We preserve driver assignments and linked vehicle data across migrations.

Vehicles represent the physical assets assigned to Drivers. Vehicle records include type, capacity, depot, speed profile, and custom attributes. Route4Me supports mixed fleets with vehicle-type constraints applied during optimization. We preserve vehicle profiles and their capacity constraints.

Orders are linked to Addresses and carry custom fields such as order number, weight, payment status, and service type. Custom Order fields are user-defined and vary by account. We migrate Order data but require a pre-migration field-mapping pass to align non-standard custom fields to the destination schema.

The Address Book is Route4Me's master location repository. Entries include alias, full address, geocoded lat/lng, tags, notes, and custom fields. Address Book entries can be imported via CSV spreadsheet or API. We export the full Address Book and map entries to the destination's equivalent contacts or locations object.

Territories define geographic regions for route planning and territory management. They are polygons associated with Members or Teams. Route4Me exports territory boundaries, but representation varies (GeoJSON, polygon format) across tiers. We flag territory boundaries as requiring coordinate-system verification before import.

Avoidance Zones are user-defined polygon regions that the routing engine excludes from route calculations (tolls, restricted areas, low bridges). Zone data is exported as polygon geometry. Migration requires the destination platform to support the same polygon format or coordinate reference system.

Route4Me captures real-time GPS tracking for all active routes. Tracking data includes lat/lng timestamps per Driver, route adherence, and geofence events. We export tracking history as CSV with timestamped coordinate records. Proof-of-delivery photos and signatures are exported as attachment URLs separate from the CSV.

POD records include photo, video, and digital signature captured at stop completion. Route4Me stores POD as attachments linked to Address records. Photos and signatures are exported as URLs pointing to Route4Me's CDN; migration must download and re-host these assets or update URLs to the new storage endpoint.

Notes can be attached to individual Addresses and carry free-text content, captured photos, or audio. Route Notes export as a separate CSV with attachment URLs. We include notes in the migration payload and map them to the destination's equivalent comment or activity object.