Migrate from SuiteCRM to Odoo CRM

SuiteCRM Accounts map directly to Odoo Partners (res.partner) with is_company=True. The company name, industry, website, and billing address fields migrate as Partner fields. SuiteCRM's shipping address subpanel maps to Partner's contact type records (child Partners with type=delivery) linked to the parent company Partner. Account is imported first in every migration because every Contact, Opportunity, and Case requires a resolved parent Account reference.

SuiteCRM Contacts merge into Odoo Partners with is_company=False. SuiteCRM Lead and Contact records both map to Partner because Odoo does not enforce a separate Lead-to-Contact conversion workflow. We tag each migrated Contact with a SuiteCRM origin tag (contact_lead or contact) to preserve lineage. The Contact's primary Account link maps to Partner.parent_id pointing at the resolved Account Partner record. SuiteCRM's title, phone, email, and address fields map directly to Odoo Partner fields.

SuiteCRM Leads map to Odoo CRM Lead (crm.lead) records in the pipeline kanban. The SuiteCRM lead status (New, Assigned, In Progress, Converted, Dead) maps to Odoo stage_id values that we configure before migration. SuiteCRM lead_source maps to Odoo's source_id (campaign reference). Lead assignment in SuiteCRM (assigned_user_id) maps to Odoo user_id on the Lead. Because Odoo Leads are part of the same crm.lead model as Opportunities, the customer chooses during scoping whether to import historical Leads as Odoo Leads or as archived Opportunities.

SuiteCRM Opportunities map to Odoo crm.lead with type=opportunity. The revenue amount, sales stage, and expected close date migrate to Odoo's planned_revenue, stage_id, and date_deadline. SuiteCRM's Opportunity-Account relationship (linked_id) maps to Odoo's partner_id pointing at the resolved Account Partner. Probability is computed from SuiteCRM's sales stage using a stage-probability map defined during scoping. Closed-Lost and Closed-Won from SuiteCRM map to Odoo's Lost and Won stage states.

Each SuiteCRM pipeline (if multiple exist) maps to an Odoo Sales Team (crm.team) with its own stage pipeline. SuiteCRM pipeline stages become Odoo crm.stage records ordered by sequence. Stage probability percentages migrate to stage_minimum_rate and stage_maximum_rate fields on each Odoo stage. The customer approves the stage mapping matrix before migration begins.

SuiteCRM Products map to Odoo product.product records. Product name, SKU (product_code), description, and list price migrate. Products must be imported before Quotes so that Quote line items can reference product IDs during import. We export the SuiteCRM Products catalogue in a first-pass before any Quote migration begins.

SuiteCRM Quotes map to Odoo Sale Orders. Quote headers (related Opportunity, Account, date, expiry) migrate to sale.order fields; line items reference the product.product IDs resolved from the Product import. Quote tax and discount fields map to Odoo order line taxes and discount fields. If the destination Odoo instance does not include the Sale module, Quotes migrate as crm.lead custom fields and the customer enables Sale separately.

SuiteCRM Invoices map to Odoo Account moves with type=out_invoice. Invoice amount, status (Paid/Unpaid), date, and related Account migrate. Note that SuiteCRM Invoices have no connection to an accounts-receivable ledger — Odoo Accounting is required for full AR/AP functionality. If the destination Odoo instance does not include the Accounting app, Invoice records migrate as PDF-linked records on the Partner and we flag the accounting reconciliation layer as out-of-scope for the CRM migration.

SuiteCRM Contracts (start date, end date, renewal status) map to Odoo Project if the customer uses Odoo Project, or to a custom contract model in Odoo Studio if Project is not enabled. Contract renewal date migrates as a date field on the Project task or the Studio contract record. The mapping strategy is confirmed during scoping based on the customer's intended Odoo app stack.

SuiteCRM Cases (Bugs module) map to Odoo Helpdesk Ticket (helpdesk.ticket). Case priority, status, and description migrate to ticket priority, stage_id, and description. The related Contact or Account maps to ticket.partner_id and ticket.partner_id reference. If the destination Odoo instance does not include the Helpdesk app, Cases migrate as Project Tasks linked to the parent Account Partner for visibility.

SuiteCRM Campaigns map to Odoo UTM Campaign (utm.campaign) for marketing attribution tracking. Campaign name, status, start date, and budget migrate. Target lists from SuiteCRM (Contacts and Leads targeted by the campaign) migrate as Odoo Contact Tags (res.partner.category) applied to the relevant Partner records. Campaign response data (opens, clicks tracked in SuiteCRM) migrates as Note records attached to the Campaign for historical reference.

SuiteCRM Documents store files on the server filesystem with database metadata (filename, revision, template flag). We extract the file blobs from the upload directory in parallel with database export, preserve file permissions and checksums, and import them into Odoo's filestore as ir.attachment records linked to the parent Partner, Lead, or Opportunity. Document metadata (revision number, template flag) migrates as fields on the ir.attachment record. This is the highest-risk step for data loss and requires a checksum validation pass post-extraction.

SuiteCRM Studio custom fields store extended column names (suffix _c appended to module table) in the database. We scan SuiteCRM's metadata tables to enumerate all Studio fields, their data types, and their containing module. Each custom field is re-created in Odoo using Odoo Studio with the closest matching field type (Char, Integer, Float, Selection, Many2One, etc.). Many2One fields require the referenced module to be imported first. Custom fields on SuiteCRM modules without an Odoo equivalent (e.g., SuiteCRM-specific modules) are discussed during scoping for custom Odoo model creation.

SuiteCRM Users referenced in assigned_user_id on any record map to Odoo res.users by email match. SuiteCRM users must be provisioned in Odoo before any record migration begins because OwnerId (user_id) is required on Leads and Opportunities. Users without a matching Odoo account enter a reconciliation queue and the customer provisions them manually before the next migration phase starts.

SuiteCRM activity records (calls, emails, meetings, tasks) tied to Contacts, Leads, or Opportunities migrate to Odoo's mail.message records on the related Lead or Opportunity. Call activities migrate to crm.phone.call if the Odoo CRM module includes the telephony feature; otherwise they migrate as Note records. Meeting activities migrate with date, duration, and location preserved. Email history migrates as mail.message records with the original email body preserved. Each activity is linked to the resolved Odoo Partner or crm.lead record via the Odoo mail.thread model.