Migrate from Field Nexus to Odoo CRM

Field Nexus customers map directly to Odoo res.partner records. Customer name maps to name, email to email, phone to phone, and address fields to street, city, state, and country on the partner address sub-record. Multiple contacts per customer in Field Nexus each become separate res.partner records linked to the same parent partner.

When Field Nexus stores an organisation-level account, it maps to a res.partner record with the company flag set to True. Individual contact persons at that organisation map as separate res.partner records with type set to contact and a parent_id link back to the company partner.

Field Nexus work orders have no native equivalent in Odoo CRM. FlitStack maps work orders to crm.lead records using the opportunity model, with custom fields added on the Odoo side to store work_order_id, work_order_status, service_type, scheduled_date, technician_id, and service_address. The crm.lead name field holds the work order title, and stage maps from Field Nexus status values to Odoo stage names.

For teams using Odoo Project alongside CRM, work orders can alternatively map to project.task. This requires the Project app to be installed in Odoo. The task gets the same custom fields for work order metadata, and a project is pre-created to contain all migrated tasks. The approach choice is confirmed during the sample migration phase before full migration runs.

Field Nexus estimates map to Odoo sale.order records. Estimate number maps to name, customer to partner_id, line items to order_lines (product_id, product_uom_qty, price_unit, discount), and status maps to sale.order state: draft to Quotation, submitted to Sent, accepted to Sale Order. Tax handling requires Odoo tax configuration review since Field Nexus tax rules may differ.

Field Nexus invoices map to Odoo account.move records with move_type set to out_invoice. Invoice number maps to ref, invoice date to invoice_date, due date to invoice_date_due, and line items to invoice_line_ids. The partner_id, amount_untaxed, amount_tax, and amount_total map directly. Payment status (paid, unpaid, partial) maps via the reconcile field on related account.move.line records.

Field Nexus team members and technicians map to Odoo res.users records. Name maps to name, email to login (used as the username), and phone maps to phone on the related res.partner record created automatically for each user. Active status maps directly. Odoo user permissions and groups are not migrated and must be configured post-migration.

Field Nexus file attachments on work orders, customers, or invoices are downloaded and re-uploaded to Odoo ir.attachment records linked to the corresponding res.partner, crm.lead, or account.move. The original filename, file content, and create date are preserved. Odoo's attachment size limits apply — files exceeding 25MB require chunking or external storage configuration.

Field Nexus work order notes and activity history map to Odoo mail.message records attached to the parent crm.lead or res.partner. Original timestamps and the author name (resolved via email match to a res.users record) are preserved. Notes with internal flag set in Field Nexus map to Odoo's internal note visibility.

Every custom field defined in Field Nexus requires a corresponding custom field to be pre-created in Odoo before migration runs. FlitStack delivers a custom field creation plan specifying the field name, type (char, date, datetime, selection, float, integer), and target model (res.partner, crm.lead, sale.order, account.move, res.users). This plan is reviewed during the pre-migration schema setup step.

Field Nexus scheduling windows and dispatch assignments have no native Odoo equivalent. FlitStack stores scheduled_date, scheduled_time_window, assigned_technician, and dispatch_status as custom fields on the migrated crm.lead or project.task. For teams needing a full scheduling board, a separate project with task dependencies can be configured post-migration.

Field Nexus automations including scheduling rules, dispatch triggers, status-change notifications, and approval workflows cannot be exported or migrated. They must be rebuilt manually in Odoo using automation rules (available in CRM and Project apps) or external tools. FlitStack exports a structured document listing each active automation with its trigger conditions and actions as a rebuild reference.