Migrate from Salesflare to Odoo CRM

Salesflare Account maps to Odoo res.partner with partner_type = 'company'. Standard fields (name, domain, industry, city, country) migrate directly. The HubSpot-style junction that Salesflare maintains between Account and Contact maps to Odoo's implicit contact-address model where each Contact is a res.partner with parent_id pointing to the Account. We resolve parent_id during migration to replicate the Account-Contact hierarchy. Custom properties on Account become ir.model.fields on res.partner created via Odoo Studio before migration.

Salesflare Contact maps to Odoo res.partner with partner_type = 'contact'. The link to the parent Account is set via parent_id = the migrated Account record ID. Email, phone, title, and social links migrate as standard fields. Enrichment data (LinkedIn URL, company size, revenue) from Salesflare's signature scraping does not have a native Odoo equivalent; we map these to custom Char or Integer fields created in Odoo Studio before migration.

Salesflare's explicit Account-Contact junction with primary/secondary roles maps to Odoo's parent_id field on res.partner. We export the junction as a join table during discovery, then set parent_id = Account ID on each Contact during import. Primary contact designation migrates as a boolean custom field (is_primary_contact__c) since Odoo does not have a native primary-flag on the partner model.

Salesflare Opportunity maps to Odoo crm.lead (type = 'opportunity'). The opportunity value, expected close date, stage name, and probability migrate to Odoo fields. The linked Account maps to partner_id on crm.lead. Closed-Lost and Closed-Won reasons from Salesflare custom properties become Odoo stage customization or tag fields.

Salesflare pipeline definitions (pipeline name, stage labels, stage order) map to Odoo crm.stage records within the default CRM pipeline. Odoo CRM uses a single pipeline model by default. If the customer uses multiple Salesflare pipelines, we map each to a separate stage sequence in Odoo and configure crm.team to segment by pipeline, or we document the gap if true multi-pipeline support is required.

Salesflare activity records (calls, emails, meetings, tasks) map to Odoo mail.message records linked to the target res.partner or crm.lead via model, res_id, and message_type fields. Call disposition and duration become custom fields on mail.message. Meeting details (start datetime, end datetime, location) preserve. The Odoo activity system (crm.activity) is separate and used for planned tasks; historical timeline data uses mail.message for audit continuity.

Salesflare tags (flat labels on Accounts, Contacts, and Opportunities) map to Odoo crm.tag records. Tag associations migrate as a many-to-many join table. No hierarchy or inheritance exists in either platform. Tags on Accounts and Contacts migrate as crm.tag records linked to the migrated res.partner.

Salesflare custom properties on Accounts, Contacts, and Opportunities are exported as a property map during discovery. We create matching Odoo custom fields via Odoo Studio or ir.model.fields XML before migration begins. Field types are mapped: text to Char/Text, number to Integer/Float, date to Date, dropdown to Selection, checkbox to Boolean. Custom field names are preserved as field labels.

Salesflare Users (Owners) map to Odoo res.users by email match. Owner assignments on Opportunities migrate as user_id on crm.lead. Users without a matching Odoo account are held in a reconciliation queue for the customer's admin to provision. Salesflare role and permission sets do not map directly to Odoo access rights groups; we document the mapping for manual configuration post-migration.

Salesflare file attachments (linked to Accounts, Contacts, or Opportunities) migrate as Odoo ir.attachment records with res_model pointing to the target model (res.partner or crm.lead) and res_id pointing to the migrated record ID. We preserve filename, file size, and the download URL if accessible. Large binary files are re-downloaded where the source URL is reachable; otherwise metadata is preserved for manual re-upload.

Salesflare email sequences (Growth tier single flow, Pro/Enterprise multi-step) do not have a direct Odoo equivalent. Odoo does not ship a native sales engagement cadence tool. We deliver a written inventory of every active Salesflare sequence with its steps, delays, conditions, and conditions, plus a recommended Odoo approach (Odoo mass mailing + CRM scheduled actions, or a third-party sales engagement tool). Sequences are not migrated as executable code.

Salesflare lead credits are a metered enrichment quota, not contact records. We export credit balance, monthly allocation, and purchase history as a separate billing CSV. The destination Odoo org has no equivalent credit model. Customers should plan to establish a new enrichment budget in Odoo via a third-party tool (Hunter.io, Apollo.io, or similar) independent of the CRM migration.