Migrate from Odoo Field Service to Nutshell

Odoo FSM version discovery and object inventory

We connect to your Odoo instance via XML-RPC and probe the database schema to determine which Odoo version is running and where FSM task data lives (field.service.task for versions 15–18, planning.slot / project.task for Odoo 19 Planning). We inventory all active Odoo modules, count field.service.task records, res.partner records (technician and customer types), field.service.location records, product.product lines used in FSM, maintenance.equipment records, and any custom fields defined via ir.model.fields. This discovery output drives the migration scope and timeline estimate.

Nutshell schema preparation and owner resolution

Before data moves, we create the Nutshell Custom Fields needed to receive Odoo's FSM-specific data — custom_priority__c, custom_planned_hours__c, custom_total_hours__c, custom_gps_latitude__c, custom_gps_longitude__c, custom_signature__c, custom_equipment_name__c, custom_serial_number__c, custom_parent_location__c, tags__c, custom_original_create_date__c, and custom_last_modified_date__c on Companies and Deals. We also resolve Odoo technician partner IDs to Nutshell users by email match so Deal owners can be assigned correctly. Any technician without a matching Nutshell user is flagged for your team to create the user account before the full run.

Technicians and customers first, tasks second

Nutshell Deals require a valid accountId (Company) and ownerId (user) to be saved. We sequence the migration to resolve these foreign keys first: Odoo technician partners become Nutshell Persons with Role = Technician, Odoo customer partners become Nutshell Companies with their contact Persons, and Odoo locations become Companies (or supplemental address data on existing Companies). Only after all Companies and Persons are committed does the FSM task-to-Deal migration run, ensuring every Deal can link to its customer Company and assigned technician owner without orphan records.

Sample migration with field-level diff

A representative slice of 100–500 records migrates first — spanning technician Persons, customer Companies, location records, FSM Tasks as Deals, and a sample of product line items and timesheet entries. We generate a field-level diff comparing the source Odoo record values against the destination Nutshell record values, so you can verify priority mapping, stage mapping, location address flattening, and owner resolution before the full run commits. You approve the diff before we proceed to the full migration.

Full migration run with delta-pickup window

The full Odoo FSM dataset migrates into Nutshell. A delta-pickup window — typically 24–48 hours — captures any Odoo FSM tasks, technician updates, or location changes made during the cutover while your team continues working in Odoo. FlitStack AI uses scoped read access on Odoo during this window so your team is not locked out. After the delta window closes, we stop writes to Odoo, re-run any changed records into Nutshell, and run a reconciliation count check against the source record totals before declaring the migration complete.

Post-migration validation and manual-rebuild handoff

We run a full reconciliation pass: total Deal count vs. Odoo task count, total Company count vs. Odoo customer partner count, and a field sampling check on custom fields. We deliver an exported CSV of Odoo equipment records, Odoo FSM workflow definitions (for manual rebuild reference), and the Odoo invoice CSV for your finance team. Any unmapped data is documented in a gap report. FlitStack AI's audit log records every operation, and one-click rollback is available if reconciliation fails.