Migrate from FIVE CRM to Odoo CRM

FIVE CRM Contacts map directly to Odoo CRM Contacts. The email address is the primary dedupe key during import. We resolve the parent Company reference before Contact import so that the partner_id foreign key is satisfied on insert. FIVE CRM owner assignments map to Odoo User records by email match, with unresolvable owners held in a reconciliation queue for admin provisioning before the contact phase begins.

FIVE CRM Companies map to Odoo Contact records with company_type set to company. The company name becomes the Contact name field, and the domain becomes the website field. Contact is created before any child Contact import so that the parent partner_id lookup resolves at insert time. This ordering is enforced in every phase sequence.

FIVE CRM Leads map to Odoo CRM Lead records. The original FIVE CRM lead_source value migrates as a custom field or tag so that sourcing attribution is preserved. Any FIVE CRM lead_score or telemarketing qualification flags map to custom integer fields on Odoo Lead. Odoo Lead kanban stage names are configured during scoping to match the customer's existing FIVE CRM lead pipeline stage labels.

FIVE CRM pipeline configurations with custom stage names map to Odoo CRM Stage records within a single pipeline. Each FIVE CRM pipeline becomes a Stage sequence; if the customer uses multiple named pipelines in FIVE CRM, we document the mapping and configure separate kanban views in Odoo via custom kanban view XML rather than as separate pipeline objects, since Odoo's native CRM uses a single pipeline per sales team.

FIVE CRM Campaigns map to Odoo Marketing Campaign records with campaign_membership records linking individual Contacts to the campaign. Campaign name, type, and status migrate as Odoo Campaign fields. Individual email event data (opens, clicks, replies) does not migrate via bulk export; we migrate campaign membership (which contacts are in which campaigns and their current status) and flag granular engagement event logs for a separate FIVE CRM export followed by Odoo manual import.

FIVE CRM Tasks map to Odoo CRM Task records or Project Task records depending on whether the customer has the Project app installed. Due date, assignee, priority, and completion status transfer directly. FIVE CRM task types that do not map to Odoo's default task stages are resolved during scoping and consolidated into the nearest Odoo stage.

File attachments associated with Contacts, Companies, or Leads in FIVE CRM migrate as Odoo IrAttachment records linked via the res_model and res_id fields to the parent Contact or Lead record. Attachments over 10MB are flagged for separate file-transfer handling due to API payload limits.

FIVE CRM tags migrate to Odoo CRM tags (stored in the crm.tag model). Multi-select tag fields in FIVE CRM custom properties split into individual tag assignments during migration. We agree on tag normalization rules during scoping to prevent tag proliferation in Odoo.

FIVE CRM Owner records map to Odoo ResUsers by email address. Any Owner without a matching Odoo User is placed in a reconciliation queue. The customer's Odoo admin provisions the missing user before record import resumes, because OwnerId references are required on Contact, Company, and Lead records.

FIVE CRM telemarketing custom fields (lead scoring matrices, dialer session flags, campaign targeting fields, warm-up status fields) require explicit field-level mapping during a pre-migration field mapping session. We enumerate every custom field in use, confirm its data type against the FIVE CRM schema, and agree on a destination Odoo field before any data moves. Odoo custom fields are created via Studio or Python before migration begins. This step is mandatory for every FIVE CRM migration because the platform does not expose a complete schema document via its public API.

FIVE CRM lead scoring values stored in custom numeric fields migrate to Odoo custom integer fields on the Lead model (crm.lead). We preserve the field name as a suffix on the Odoo custom field for admin readability. Score thresholds used for routing in FIVE CRM are documented separately for Odoo automated action rebuild.

FIVE CRM campaign membership (which Contacts are subscribed to which Campaigns, with subscription status flags) maps to Odoo Campaign lines via the mail.mass_mailing.contact model linked to the Odoo Campaign. This preserves segmentation for re-running campaigns in Odoo Marketing after migration.