Migrate from Efficy CRM to Odoo CRM

Efficy Company records map directly to Odoo res.partner with partner_type set to 'company' and is_company = True. The Company name becomes partner name; street, city, country, and phone map to their Odoo res.partner equivalents. Efficy custom fields on Company migrate as ir.model.fields on res.partner. We import Companies first because every Contact in Odoo requires a parent_id pointing to a company partner, matching Efficy's requirement to load Companies before Contacts.

Efficy Contact records map to Odoo res.partner with type = 'contact' and is_company = False, linked via parent_id to the company partner. The contact's name, email, phone, function (job title), and website map to their Odoo counterparts. Efficy's multi-address support (address type: billing, shipping) maps to Odoo's address type split across multiple res.partner records with partner_type = 'contact' or 'invoice' linked to the same parent_id. Custom fields on Contact migrate as additional ir.model.fields on res.partner.

Efficy Opportunity records map to Odoo crm.lead. The dealstage maps to stage_id on crm.lead, resolving to a stage within the active crm.stage pipeline. Expected close date maps to date_deadline; deal value maps to planned_revenue; owner assignment maps to user_id. Efficy custom fields on Opportunity migrate as ir.model.fields on crm.lead. Pipeline assignment in Efficy maps to Odoo's crm.team via team_id.

Each Efficy dealstage within a pipeline maps to a crm.stage in Odoo's pipeline. We pre-create the stage records before Opportunity import, preserving the stage sequence order and probability percentage. Stage names are recreated verbatim; stage colors and is_won flags are configured per Odoo's pipeline editor.

Efficy deal pipelines map to Odoo crm.team records. Each crm.team gets a member list populated from Efficy Owner assignments. If Efficy has multiple pipelines with overlapping team members, we create one crm.team per pipeline and assign the relevant stage set to each.

Efficy call activities log to Odoo crm.phone.call if the customer has the VoIP module enabled. The call duration, disposition, and date migrate to duration, state, and call_date respectively. If crm.phone.call is not available in the destination edition, calls migrate as calendar.event with type = 'call' and meeting category set accordingly.

Efficy email engagements map to Odoo mail.message records linked to the parent crm.lead (as model='crm.lead', res_id=<lead_id>) or res.partner (as model='res.partner', res_id=<partner_id>). Email body, subject, and date migrate directly. Attachments on email records migrate as ir.attachment linked to the mail.message.

Efficy meeting activities map to Odoo calendar.event. Start datetime, end datetime, location, and description migrate. Attendee records migrate as calendar.attendee linked to the event, resolving the attendee email to a res.partner or user record. Meeting type metadata from Efficy becomes the calendar.event description or a custom field.

Efficy task activities map to Odoo project.task. If the customer does not have a dedicated project module, tasks migrate to crm.lead as a note or as a calendar.event with task metadata. We resolve the owner assignment from Efficy to the Odoo user_id. Task status (open, closed) maps to stage_id in the destination task project.

Efficy notes (engagement type NOTE) migrate to Odoo mail.message records with message_type = 'comment'. They link to the parent record (crm.lead or res.partner) via model and res_id. Rich text content migrates as HTML body. If Efficy notes contain file attachments, these migrate as ir.attachment linked to the mail.message.

Efficy ticketing module records migrate to Odoo helpdesk.ticket if the Helpdesk app is enabled in the destination. Ticket status maps to stage_id; priority maps to priority; agent assignment maps to user_id. Efficy custom fields on Tickets migrate as ir.model.fields on helpdesk.ticket. Conversation history in Efficy tickets migrates as mail.message thread on the helpdesk.ticket.

Efficy project module records migrate to Odoo project.project with task hierarchy preserved in project.task. Milestones map to project.milestone if available in the destination edition, otherwise as top-level tasks with milestone flags. Resource allocation and time tracking migrate as project.analytic.account entries. The project manager assignment maps to user_id on project.project.

Efficy custom fields on Companies, Contacts, Opportunities, and other objects are extracted during discovery as a full field schema. We pre-create each as ir.model.field in Odoo with the corresponding field_type (char, integer, float, date, selection, many2one, etc.) before any data import. many2one custom fields require a target model to be resolved; we flag these during scoping for explicit mapping decisions.

Documents attached to Companies, Contacts, or Opportunities in Efficy migrate as ir.attachment records linked to the corresponding res.partner, crm.lead, or project.project. We extract the binary or URL and store it in Odoo's filestore. Documents without a download URL go to a reconciliation queue with a written note to the customer for manual retrieval. Large document volumes may require separate filestore provisioning.

Efficy user records (sales reps, admins) map to Odoo res.users by email lookup. Active and inactive status is preserved; inactive Efficy users import as inactive res.users so historical assignments are retained. Role and access group mapping from Efficy's Designer roles maps to Odoo access rights groups or portal configurations if a customer portal is in scope.

Efficy object-level tags migrate as crm.tag records and linked to crm.lead via crm.tag.rel. Tags used for list segmentation (rather than per-record labeling) are flattened to crm.tag membership; the customer decides whether to rebuild segmentation logic in Odoo's Filters or Group By views. Tags that represent customer categories (industry, size tier) may be better implemented as selection fields rather than tags in Odoo.