Migrate from FunnelMaker to Odoo CRM

FunnelMaker Contact records map to Odoo res.partner with address-type roles (contact, invoice address, delivery address) preserved via partner_id and address_type fields. All standard fields (name, email, phone, website) map directly. FunnelMaker user-defined contact fields map to Odoo custom fields on res.partner. We set type=contact by default and preserve the FunnelMaker contact owner as a many2one to res.users via the assigned_user_id field.

FunnelMaker Company records map to Odoo res.partner with type=company and child_contact records for individual contacts linked as children. The company name maps to partner.name, industry to industry_id, and domain (website) to website. Custom company-level fields from FunnelMaker migrate to custom fields on the res.partner record.

FunnelMaker Opportunity records map to Odoo CRM Lead. FunnelMaker's pipeline stage maps to Odoo's stage_id with the pipeline mapped to a crm.team record. Expected revenue maps to Odoo planned_revenue; FunnelMaker's deal value maps to Odoo's amount_total if Products are present or stays as planned_revenue if standalone. Owner assignment resolves via email match to res.users.

FunnelMaker's drag-and-drop pipelines map to Odoo crm.team records, each with its own stage sequence. We preserve FunnelMaker stage names, probabilities, and sequence order in Odoo stage records. The FunnelMaker pipeline-to-stage relationship migrates as a many2one on the Lead record. If FunnelMaker had multiple pipelines, each becomes a separate crm.team in Odoo.

FunnelMaker activity records (calls, emails, tasks, notes) map to Odoo mail.message records linked to the parent res.partner or crm.lead via model and res_id fields. Email content migrates as body HTML in mail.message; tasks migrate as mail.activity with activity_type_id resolved to Odoo's standard task types. Activity date and author preserve from FunnelMaker. Call duration and disposition migrate to custom fields on the mail.message record.

FunnelMaker lead scores are calculated using customizable rules. We migrate the numeric score value as a custom Float field (x_lead_score) on res.partner. The scoring rule logic is documented in a written reference sheet so the customer's admin can rebuild the scoring rules using Odoo Automations or a third-party scoring app. Score values themselves migrate without recalculation.

FunnelMaker drip campaigns are email sequences tied to contact segments. We map campaign structure, step timing, and associated contact segments to Odoo Email Campaigns (mailing.mailing) with a written sequence map. Each drip step becomes a separate mailing record within the campaign. The Odoo Automations module (included in CRM) can replicate trigger conditions; we document the equivalent trigger logic for the admin to configure post-migration.

FunnelMaker workflow rules trigger CRM actions based on contact behavior. We document every active workflow during discovery as a written automation map covering trigger condition, filter criteria, time delay, and action type. Odoo's Automations module (CRM included) provides equivalent record-triggered and scheduled actions. We do not migrate workflow logic as code; the admin reviews the map and configures Odoo Automations manually using the documented equivalents.

FunnelMaker Tags and Groups segment contacts into lists. We map tag names to res.partner.category records in Odoo and create tag_ids many2many relations on the res.partner record during migration. Group memberships with hierarchy (FunnelMaker Groups contain sub-Groups) flatten to a flat tag list in Odoo since Odoo does not natively support tag hierarchy.

FunnelMaker unlimited custom objects map to Odoo custom fields on standard models (res.partner, crm.lead) when the custom object is contact-linked, or to a custom ir.model if it has standalone records. We inspect the FunnelMaker custom object schema during discovery, map field types to Odoo field types (char, float, integer, selection, many2one, etc.), and pre-create the Odoo schema before migration. Custom model ir.actions and views require Custom plan or Odoo Studio app.

FunnelMaker document signature requests and stored documents migrate as Odoo ir.attachment records linked to the parent res.partner or crm.lead record via res_model and res_id. Document metadata (filename, create date, create uid) preserve. File content migrates where accessible; binary files requiring FunnelMaker-specific viewer are documented with a reference link for manual retrieval.

FunnelMaker Owners (assigned to contacts, companies, opportunities) map to Odoo res.users by email match. We extract all distinct owner email addresses during scoping and match against the destination Odoo instance's user list. Any Owner without a matching Odoo user is held in a reconciliation queue for the admin to provision before record import. This is a required pre-condition before Opportunities can be imported with owner assignment.