Migrate from Getfly CRM to Odoo CRM

Getfly Accounts with a single primary contact map to an Odoo Company (res.partner with is_company=True) plus a Contact record (is_company=False) linked via parent_id. Getfly Accounts with multiple linked Contacts generate one Company record and multiple Contact records, each with parent_id pointing to the Company. The Account name becomes the Company name; the primary contact's name, email, and phone populate the Contact record. We flag accounts with no contact records during extraction for admin review before insert.

Getfly's secondary contact fields map to Odoo Contact records with parent_id pointing to the Company res.partner. Email, phone, mobile, and address fields map directly. Role or title fields map to res.partner.function. Any contact-level custom fields migrate to custom res.partner fields created in Odoo Technical Settings before import.

Getfly's configurable pipeline stages map to Odoo CRM Stage records scoped by team_id. Stage order, name, and probability percentage migrate to stage_id.sequence, stage_id.name, and stage_id.onchange_stage_probability. Odoo requires at least one Stage per CRM Team; we create the Stage records before any Opportunity import so the foreign key is satisfied.

Getfly Deals map to Odoo CRM Lead (crm.lead) in opportunity state. Deal name becomes crm.lead.name, deal amount becomes crm.lead.planned_revenue, and dealstage maps to stage_id via the stage name match. Contact_id and company_id (res.partner) are resolved via email and name lookup before the Opportunity insert. Lost or won state migrates as stage_id on the corresponding closed stage.

Getfly Products map to Odoo product.template records. SKU, name, list_price, and standard_price migrate directly. Getfly custom_fields stored as nested objects on Products flatten into custom product.template fields that we create in Odoo Technical Settings before import. Variant management follows Odoo's standard: if Getfly has no variants, we create a single product.template with product_variant_ids containing one product.product.

Getfly Activity records of type Task map to Odoo project.task. Subject, description, date, assigned user, and linked account are preserved. activity_type = task maps to project.task with kanban_state = open. Completed tasks map with kanban_state = done and write_date reflecting the completion timestamp.

Getfly PABX call records map to Odoo project.task records with a note subtype to preserve call direction, duration, and disposition in custom fields. The original Getfly recording URL is downloaded during the extract phase and re-uploaded as an ir.attachment linked to the task. If the destination Odoo instance does not have the VoIP module, call recordings are stored as generic attachments with a naming convention reflecting the call date and duration.

Getfly Activity records of type Meeting map to Odoo calendar.event. Start datetime, end datetime, subject, description, and attendee list (linked contacts) migrate to calendar.event and calendar.attendee records respectively. Meeting location maps to calendar.event.location.

Getfly workflow rules are not exportable via API and do not migrate. We document every active Getfly automation during discovery using a workflow audit questionnaire completed by the customer before migration kickoff. The output is a written inventory with trigger type, conditions, actions, and recommended Odoo base.automation or Studio action equivalent. The customer's Odoo admin or an Odoo partner rebuilds the automations post-migration.

Getfly custom fields vary per customer and are discovered by sampling Account and Product records since Getfly has no schema registry endpoint. We instruct the customer to run a full field audit from Getfly's admin panel before migration kickoff. Each discovered custom field maps to an Odoo custom field (created in Settings > Technical > Fields) with a compatible type (char, text, float, integer, selection, many2one, date) before the data import phase begins.

Getfly Users map to Odoo res.users. We resolve by email match. Any Getfly Owner without a matching Odoo res.users is held in a reconciliation queue; the customer's Odoo admin provisions missing users before the Opportunity and Activity import phases run because OwnerId (user_id) is required on crm.lead and project.task.

Getfly marketing Campaigns (name, start/end dates, linked accounts) map to Odoo CRM Tags applied to the relevant Contact and Opportunity records. Campaign membership is preserved as tag names matching the Getfly campaign. If the customer uses Odoo's full CRM module with Team, each Campaign maps to a CRM Team with its own Stage pipeline.

Attachments associated with Getfly Accounts or Products are referenced by URL in the API. We download each file to local storage during export, preserving the original filename and MIME type, then re-upload to Odoo as ir.attachment records linked to the corresponding res.partner or product.template via res_model and res_id. This prevents broken attachment links post-migration.