Migrate from Service Suite FSM to Odoo CRM

Odoo External API is gated behind the Custom plan — Community and Standard require CSV import

Odoo External API access via XML-RPC or REST is available only on the Custom plan ($37.40/user/month or $37.40/user/month on annual billing). Community edition and Standard plan do not include External API access. If your Odoo instance is running Community or Standard, FlitStack AI cannot execute the migration programmatically and must fall back to CSV import. CSV imports require manual column-header mapping per object, do not support relationship resolution (partner_id lookups must be pre-seeded), and lack transactional rollback. Verify your Odoo plan before scoping begins — plan upgrades add cost and require Odoo partner involvement.

Odoo External API enforces a hard 1 request per second rate limit that cannot be adjusted

Odoo's External API enforces a rate limit of 1 request per second per instance, and Oracle's documentation states this ceiling will neither be raised nor lowered per customer. Service Suite FSM data models with large work order tables (50k+ records) require careful pagination and batching to avoid HTTP 429 responses during the migration run. FlitStack AI paginates FSM bulk exports and uses Odoo's batch-write endpoints (model.create with a list of records) to maximize throughput within the 1 rps ceiling, but migration duration scales with record volume and this constraint cannot be negotiated with Odoo.

FSM work orders have no native equivalent in Odoo CRM — custom fields or a dedicated custom model are required

Odoo CRM's primary objects are crm.lead and res.partner — there is no native work-order or field-service-task object in the base CRM module. FSM work order properties (service type, urgency, skill requirements, actual hours, travel time, billing type) cannot map to standard Odoo CRM fields because none exist. FlitStack AI creates custom fields using Odoo's snake_case convention (x_fsm_service_type, x_fsm_urgency, x_fsm_actual_hours) on crm.lead, or builds a dedicated FSM Work Order custom model if the scope warrants it. The chosen approach is specified in the migration plan before schema creation begins. This is pair-specific: other FSM-to-CRM migrations with simpler data models may not require this bridge.

FSM scheduling rules, dispatch logic, and field-service automations do not migrate to Odoo CRM

Service Suite FSM scheduling rules, dispatch triggers, route-optimization settings, and field-service-specific automations operate on a fundamentally different paradigm from Odoo CRM automation rules and Studio workflows. Odoo automation rules handle CRM triggers (stage changes, field updates, time-based actions on crm.lead) — they do not replicate field-service scheduling, technician dispatch, or GPS routing logic. FlitStack AI does not migrate these. We export FSM automation definitions as a structured reference document so your Odoo admin can rebuild the logic as Odoo automation rules or Studio workflows. If the Odoo Project Management app is installed, FSM tasks can be managed there — but FSM dispatch board logic requires a separate field-service solution.

FSM multi-branch companies map to multiple res.partner records — Odoo has no native multi-location company object

Service Suite FSM allows companies with multiple branch locations, each stored as a separate location record linked to the parent company. Odoo's res.partner model holds a single street, city, state, and country per record — there is no native multi-location company construct. FlitStack AI creates one res.partner per FSM branch location (each with its own address) and links all branches using a custom Char field (x_fsm_company_group) set to the original FSM company name. This allows Odoo reports and queries to group branches while maintaining accurate per-location contact data. The alternative — collapsing all branches into a single res.partner with a single address — loses per-location service history and is not recommended.