Migrate from Route4Me to Odoo CRM

Route4Me has no native CRM lead object — routes and addresses must be decomposed into crm.lead and res.partner

Route4Me's data model does not contain a CRM lead equivalent; its primary entities are Addresses, Routes, Members, and Orders. When migrating to Odoo CRM, we decompose this into res.partner (for addresses and contacts), crm.lead (for routes as opportunities), and res.users (for members). This decomposition requires decisions about which Route4Me entity maps to which Odoo object — a route is not a 1:1 match for a crm.lead, so we treat the route as the opportunity with route metadata stored in custom fields on the lead. Teams that expect a direct import equivalent to Odoo's CSV import tool will find this decomposition requires pre-migration Odoo configuration that Odoo Studio alone cannot auto-generate. We deliver a decomposition plan before the migration run specifying the exact custom fields and crm.team structure needed.

Odoo CRM requires a Lead-to-Opportunity conversion step that Route4Me routes do not perform

Odoo CRM's standard workflow separates Leads (raw prospects) from Opportunities (qualified deals) with a Convert to Opportunity action that merges the crm.lead with a res.partner record and assigns pipeline stage, probability, and revenue. Route4Me routes arriving as crm.lead records land in Odoo's pipeline kanban view but are not automatically tied to a res.partner unless the address-to-partner mapping explicitly sets partner_id on the lead. We set partner_id during migration so routes land as pre-linked crm.lead records. However, Odoo's Convert to Opportunity wizard may still prompt users to confirm the partner linkage — this is expected behavior and does not indicate a migration error. We document this workflow step in the post-migration runbook so your team knows what to expect when opening the first converted route.

Odoo API rate limits and batch sizing affect export throughput for large Route4Me datasets

Route4Me's API constrains GET requests by query-string length (approximately 40 characters multiplied by the server's maximum GET limit), which means large filter queries with multiple route_ids must be paginated. Odoo's XML-RPC API accepts up to approximately 100 records per batch call before server timeouts occur on standard Community instances. For Route4Me setups with tens of thousands of route records, these two constraints interact — we paginate Route4Me exports across multiple API sessions with offset tracking, batch Odoo's imports into groups of 100, and run delta queries between batches to prevent record drift. FlitStack handles this sequencing automatically, but the total migration time scales with the number of unique API sessions required rather than raw record count alone.

Odoo Community versus Enterprise edition affects which migration tools are available post-migration

Odoo Community edition is free and self-hosted, giving you full database access and no API rate limits, but it does not include Odoo's official migration service, support hours, or the Odoo.sh managed hosting environment. Odoo Enterprise adds the official migration tool, priority support, and automatic version upgrades, but carries a per-user monthly fee. Teams migrating from Route4Me typically self-host on Odoo Community to reduce ongoing costs, which means the Odoo configuration (custom fields, crm.team structure, stage definitions) must be set up manually or by a consultant before data lands. FlitStack delivers the Odoo-side configuration plan as part of the migration package, but Odoo Community users are responsible for implementing the schema plan in their instance.

Route4Me telematics and GPS integrations do not migrate — fleet data lives in the telematics vendor's system

Route4Me connects natively to telematics providers including Verizon Connect, Geotab, Samsara, and Azuga, storing live GPS traces against routes. These telematics integrations are configured in Route4Me and in the respective telematics platform — neither the connection credentials nor the historical GPS traces are stored in Route4Me's exportable API in a format that maps to Odoo CRM. After migration, GPS tracking must be re-established by connecting your telematics platform directly to Odoo via Odoo's IoT module or a third-party connector. Historical route-optimization logs (completed routes, stop sequences, delivery timestamps) migrate as crm.lead records with x_total_distance_km and x_stop_count fields, but the raw GPS trace coordinates require separate export from your telematics vendor.