Migrate from Fieldy to Odoo CRM

Fieldy customers map to Odoo res.partner records. The 'company' flag in Fieldy determines whether res.partner.is_company is True or False. Company-level fields (industry, employee_count) map to Odoo partner fields; individual contacts link via parent_id to their company partner. and preserve any existing partner tags.

Fieldy customers flagged as field_service type create both a res.partner (the account) and a crm.lead (the field-service opportunity) with type 'opportunity' and a custom field x_fieldy_source_type preserved for reporting continuity. This split ensures that service requests are tracked as leads while maintaining the corporate account hierarchy.

Fieldy site records attached to a customer become Odoo res.partner address records linked via parent_id to the primary customer partner. Latitude/longitude from Fieldy map to Odoo's geo_* fields if the Google Maps integration is active properly on the destination instance.

Each Fieldy job becomes a crm.lead record in Odoo CRM with type 'opportunity'. The Fieldy job name becomes crm.lead.name; job status maps via value_mapping to Odoo crm.stage. Job description and internal notes migrate to crm.lead.description. If the Fieldy job has a primary customer, crm.lead.partner_id is set to the matching res.partner.

Fieldy job line items (service description, quantity, unit price, discount) map to sale.order.line fields. A draft sale.order is created per job in Odoo so the line items are preserved even if the opportunity is not yet converted to a confirmed sale.

Fieldy staff records resolve to Odoo res.users by email match. If a staff member has no Odoo user account, FlitStack creates a res.users with the Fieldy staff email and flags the record for the Odoo admin to assign access rights. Staff certifications and vehicle fields migrate as custom Char or Selection fields on res.users.

Fieldy job-to-staff assignments map to crm.lead.user_id (the Odoo salesman field). If the job is also represented as a project.task in Odoo, the task.user_id is set to the same resolved user. and ensure that assignment history is captured as mail.message records linked to the lead.

Fieldy job notes, call summaries, and status-change entries migrate as Odoo mail.message records attached to the corresponding crm.lead via res_model='crm.lead' and res_id set to the Odoo lead ID. Original timestamps and author names (resolved staff-to-user) are preserved in the message metadata.

Fieldy photos, signed forms, and PDF attachments linked to jobs re-upload to Odoo ir.attachment with res_model='crm.lead' and res_id pointing to the migrated lead. File names, MIME types, and create dates are preserved. Attachment size is validated against Odoo's MAX_ATTACHMENT_SIZE server parameter.

Fieldy custom fields on any object become Odoo ir.model.field definitions created during the schema-setup phase. Fieldy pick-list values are translated to Odoo Selection field options. Char, number, and date custom fields map to corresponding Odoo field types. and preserve any default values set in Fieldy.

Fieldy job routing rules, auto-assignment logic, and status-trigger automations do not have a functional equivalent in Odoo CRM. FlitStack exports all Fieldy rule definitions as a structured JSON document that maps to Odoo Studio actions and server actions for manual rebuild.

Fieldy third-party integrations (payment gateways, GPS platforms, accounting exports) must be reconnected in Odoo. FlitStack documents each active integration's credentials and webhook URL so the Odoo admin can re-establish connections post-migration. and verify that API rate limits and authentication methods are compatible with Odoo's integration framework.