Migrate from FieldFX to Odoo CRM

FieldFX Account records map to Odoo res.partner with company_type set to 'company'. The account name becomes partner name, website maps to website field, industry maps via Odoo's industry_id selection list, and parent-child company hierarchies map to Odoo's parent_id field on res.partner.

FieldFX Contact records map to Odoo res.partner with company_type set to 'person'. Each contact is a separate partner record linked to its primary Account via the parent_id field. Multi-email addresses in FieldFX (email and secondary email fields) collapse to Odoo's single email field; additional emails are stored in a custom field.

FieldFX Ticket is the core work-order object with status, priority, and service-type fields. It maps to Odoo crm.opportunity (crm_lead model) — ticket name becomes opportunity name, ticket status maps to Odoo stage_id via value mapping, priority maps to a custom priority field, and the ticket's linked account and contact become Odoo's partner_id and contact_id. Ticket description and long-text fields map to Odoo's description field.

FieldFX Job records represent the work-order header in FX E-Ticketing and FX Schedule & Dispatch. They map to Odoo project.project as the project record, with individual Job Tasks mapping to project.task records linked to that project. Job status, estimated duration, and crew assignments become project.task fields and Odoo custom fields on the task model. If Odoo Project is not installed, Job maps to crm.opportunity with a project_id custom field for reference.

FieldFX Ticket Item records (line items on a ticket) map to Odoo sale.order.line. Each Ticket Item's product, quantity, and pricing map to Odoo's product_id, product_uom_qty, and price_unit. Ticket Items linked to a Ticket that becomes an Opportunity can derive a sale.order from the opportunity using Odoo's quotation-from-opportunity flow, with lines linked back to the opportunity.

FieldFX Asset records track equipment under service contracts. They map to Odoo's stock.lot (serial-number tracked inventory) or maintenance.equipment depending on whether the team uses Odoo's Maintenance app. A custom equipment_id field on the opportunity or task preserves the FieldFX asset link. If neither Odoo app is active, assets migrate as a custom res.partner field.

FieldFX E-Ticketing module records (electronic ticket headers) are not a native Odoo object. The ticket number, service address, customer signature capture status, and e-ticket status fields migrate as custom fields on the crm.opportunity record. Signature image binary data (if stored in Salesforce) exports to Odoo as an attachment on the opportunity.

FieldFX DataGuide form responses capture structured inspection, safety, and compliance data per ticket. Each form-response field becomes a custom field on the Odoo record the form was attached to (opportunity or task). Form metadata (form version, submission timestamp) is preserved as custom datetime and text fields. Odoo has no native DataGuide equivalent — custom field creation is required.

FieldFX owner IDs (Salesforce User records) are matched to Odoo res.users by email address. The owner's name, role, and active status map to Odoo's name, groups, and active fields. Unmatched owners are flagged before migration — either the Odoo user is created first or records are assigned to a fallback admin user.

FieldFX task and activity records (logged calls, emails, meetings with timestamps and owners) map to Odoo mail.activity records. Activity type, subject, date, and body text map to Odoo's activity_type_id, summary, date_deadline, and note fields. Attachments on activities link to the corresponding Odoo attachment record.

FieldFX file attachments (Salesforce Files / ContentDocument) are downloaded and re-uploaded to Odoo's ir.attachment table linked to the target record (opportunity, partner, or task). Files stored in FieldFX Back Office's document management are extracted via Salesforce API and re-hosted in Odoo's filestore. File size limits on the Odoo instance apply.

FieldFX timecard records (hours logged per technician per ticket) map to Odoo account.analytic.line if the Timesheets app is active. Each timecard line becomes an analytic line linked to the project/task derived from the parent Job. Hours, date, and technician assignment map to unit_amount, date, and user_id. If Odoo Timesheets is not active, timecards are stored as custom fields on the opportunity.