SuiteCRM to Odoo CRM migration
We migrate Accounts, Contacts, Leads, and Opportunities from SuiteCRM into Odoo CRM with the SuiteCRM Lead and Contact models merged into Odoo's pipeline-based model, Documents extracted from the server filesystem alongside database records, and every Studio custom field mapped before cutover.
FlitStack AI migrates partners, leads, opportunities, stages and products from SuiteCRM to Odoo CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-8 weeks.

What moves from SuiteCRM to Odoo CRM?
Moving from SuiteCRM to Odoo CRM is a migration between two open-source platforms with fundamentally different data architectures.
Read the full summary
SuiteCRM keeps Leads and Contacts as separate modules; Odoo CRM uses a single pipeline model where leads enter a kanban view and are tagged and staged without a strict Lead-to-Contact conversion step. We resolve that structural difference at scoping, extracting both SuiteCRM modules and merging them into Odoo's opportunity-based pipeline with tags preserving the original Lead status. SuiteCRM's Documents module stores files on the server filesystem rather than in the database — we include a parallel filesystem extraction step and preserve file-permission metadata during import. AOW Workflow rules (stored as PHP-serialized objects) do not migrate; we deliver a written automation inventory for manual rebuild in Odoo's Automated Actions. Invoices, Cases, Campaigns, Target Lists, and Products/Quotes are fully supported object types that migrate on a dependency-ordered timeline. We use Odoo's XML-RPC API for batch record import with parent-lookup resolution and SuiteCRM's v8 REST or v4.1 SOAP depending on the source version.
Account → Partner
SuiteCRM Accounts map directly to Odoo Partners (res.partner) with is_company=True.
How it maps
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.
Contact → Partner (is_company=False)
SuiteCRM Contacts merge into Odoo Partners with is_company=False.
How it maps
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.
Lead → Lead (crm.lead)
SuiteCRM Leads map to Odoo CRM Lead (crm.lead) records in the pipeline kanban.
How it maps
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.
Opportunity → Opportunity (crm.lead with type=opportunity)
SuiteCRM Opportunities map to Odoo crm.lead with type=opportunity.
How it maps
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.
Lead Status and Stage → Stage (crm.stage)
Each SuiteCRM pipeline (if multiple exist) maps to an Odoo Sales Team (crm.team) with its own stage pipeline.
How it maps
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.
Product → Product (product.product)
SuiteCRM Products map to Odoo product.product records.
How it maps
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.
- AccountPartner1:1
- ContactPartnermerged
- LeadLead1:1
- OpportunityOpportunity1:1
- Lead Status and StageStagetransformed
- ProductProduct1:1
+ 9 more in the mapping below
How SuiteCRM and Odoo CRM differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | SuiteCRM | Odoo CRM |
|---|---|---|
| CRM model | Separate Leads and Contacts as distinct modules with explicit link to Account | Single pipeline model; leads enter kanban pipeline and convert to opportunities without a separate Contact conversion step |
| Lead-Contact split | Two objects; requires manual conversion action to link Lead to Contact and Account | Leads and Contacts are unified; Contacts are created from the Leads pipeline or added directly with tags for classification |
| Architecture scope | Pure CRM; no native accounting, inventory, or HR modules | ERP suite with CRM as one module; accounting, inventory, project, HR, and e-commerce available natively |
| Pricing model | Flat-rate hosted tiers or free Community Edition with self-hosting costs | Community Edition free; per-user pricing on Enterprise ($152/user/mo estimated) locks advanced features behind seat count |
| Document storage | Files stored on server filesystem with database metadata reference | Attachments stored as binary fields in PostgreSQL via Odoo's filestore |
| Automation engine | AOW Workflow module with PHP-serialized rule definitions stored in database | Automated Actions and Studiolow-code workflows with visual builder from the base app |
| Reporting | Built-in Reports module with pivot and graph views | Reporting embedded in each app; cross-app reports require Odoo Studio or custom views |
| Upgrade risk | 7.x to 8.x upgrade documented as breaking CSS, JS, and permissions in community forums | Major version upgrades apply via Odoo.sh or on-premise with migration scripts; generally stable per community feedback |
What to watch for in a SuiteCRM to Odoo CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
SuiteCRM Documents must be extracted from the filesystem separately
SuiteCRM's Documents module stores files on the server filesystem (typically upload/) rather than as database blobs.
How we handle it
The database record contains metadata but not the file itself. During extraction, we must copy the filesystem directory alongside the database export, preserve file ownership and permissions (chmod/chown), and validate checksum integrity before upload to Odoo's filestore. If the source SuiteCRM instance is on a decommissioned server or the upload directory is inaccessible, documents cannot be recovered from the database alone. We flag this risk at discovery and recommend a pre-migration filesystem audit.
SuiteCRM Leads and Contacts both map to Odoo Partners with different treatment
SuiteCRM separates Leads and Contacts into two distinct modules with a manual conversion workflow.
How we handle it
Odoo CRM uses a single pipeline model where Leads enter a kanban view and are tracked through stages without a separate Contact conversion step. We extract both SuiteCRM modules and apply a split rule during transformation: Leads with status Converted map to Odoo Partners (is_company=False) linked to the parent Account; unconverted Leads map to Odoo CRM Leads (crm.lead); existing SuiteCRM Contacts map to Partner records with a contact_lead tag. Skipping this design step produces duplicate Partner records for accounts that had converted Leads.
AOW Workflow rules are PHP-serialized and cannot migrate programmatically
SuiteCRM's Advanced Open Workflow module stores automation rule definitions as complex PHP-serialized objects in the database.
How we handle it
These are not accessible via the REST or SOAP API in a reusable format and cannot be transformed into Odoo's Automated Actions or Studio workflows. We export a human-readable JSON summary of each active AOW rule (module, trigger conditions, actions, delays) for the customer's admin to rebuild manually. Automated Actions in Odoo use a different event model (server actions, cron triggers, UI button triggers) and the rebuild is a configuration task, not a data migration task.
Odoo field types differ from SuiteCRM Studio; custom field mapping requires type translation
SuiteCRM Studio allows administrators to create custom fields with limited type options (Varchar, Int, Float, Decimal, Date, Datetime, Dropdown, Multiselect, Checkbox, Phone, URL, HTML).
How we handle it
Odoo Studio and the ORM expect field types with specific constraints (Char limited to 255 chars, Selection as a static key-value list, Many2One requiring a foreign key to an existing model). We enumerate all SuiteCRM Studio fields during discovery, translate each to the closest matching Odoo field type, and flag any SuiteCRM fields that require a different data model in Odoo (e.g., SuiteCRM multi-select dropdowns that exceed Odoo's selection limit of 50 values). The customer approves the field translation map before migration begins.
SuiteCRM 7.x instances require database extraction; 8.x uses REST API with different field naming
SuiteCRM 7.x does not expose all module data via the v8 REST API (which was introduced with the 8.x rewrite).
How we handle it
7.x instances require direct database extraction or the older v4.1 SOAP API for bulk export. Additionally, SuiteCRM 8.x changed the field naming convention in its API responses, replacing dot-notation custom field names with underscore-suffix notation. We detect the source version during discovery and apply the correct extraction method. If a customer plans to upgrade from 7.x to 8.x before migrating, we recommend completing the migration first on the 7.x instance to avoid a simultaneous upgrade-and-migration risk.
How the migration runs
Discovery and source version audit
We audit the source SuiteCRM instance: version (7.x or 8.x), installed modules, custom fields created in Studio, active AOW Workflow rules, Document upload directory structure, user count, and record volumes per module.
What this step covers
We extract a sample of 50-100 records from each module via the appropriate API (v8 REST for 8.x, v4.1 SOAP or direct database for 7.x) to validate field coverage and identify any non-standard encodings. The discovery output is a written migration scope, a field translation matrix for all Studio custom fields, a Document extraction checklist, and a workflow inventory document for AOW rules.
Odoo environment provisioning and schema design
We provision the target Odoo environment (Odoo.sh staging or customer-hosted) and design the schema.
What this step covers
This includes creating Odoo Users for each SuiteCRM user (matched by email), configuring Sales Teams and pipeline Stages (mapped from SuiteCRM pipelines and lead statuses), enabling required Odoo apps (CRM, Sale, Accounting, Helpdesk, Project as applicable), and re-creating SuiteCRM Studio custom fields as Odoo Studio fields with type-translated counterparts. The Odoo Administrator reviews and approves the schema design before any data is loaded.
Sandbox migration and reconciliation
We run a full migration into the Odoo staging environment using production-equivalent data volumes.
What this step covers
The customer's CRM lead reviews record counts (Partners from Accounts, Partners from Contacts, Leads, Opportunities, Products, Quotes, Cases, Activities), spot-checks 25-50 random records against the SuiteCRM source, and validates that the pipeline stage mapping produces the expected distribution. Any field translation corrections, stage mapping adjustments, or custom field additions happen at this stage and are re-validated before production migration begins.
Document filesystem extraction and integrity validation
We extract the SuiteCRM upload/ directory in parallel with the database export.
What this step covers
We record file paths, checksums (SHA-256), and permissions before copying. Files are zipped and transferred to the migration environment, then uploaded into Odoo's filestore as ir.attachment records linked to the resolved parent Partner or crm.lead. A post-transfer checksum validation pass confirms all files arrived intact. Any missing files or permission errors are reported to the customer for resolution before the production cutover window.
Production migration in dependency order
We run production migration in record-dependency order: Users (manually provisioned and validated), Partners from Accounts (is_company=True), Partners from Contacts (is_company=False with parent_id to Account), Products (for Quote line-item reference), Leads and Opportunities (crm.lead records with type set), Quotes as Sale Orders, Cases as Helpdesk Tickets or Project Tasks, Invoices as Account Moves (if Accounting is enabled), and Documents as ir.attachment.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. AOW Workflow rules are not migrated as code; the written inventory document is delivered alongside the data migration completion report.
Cutover, validation, and handoff
We freeze SuiteCRM writes during cutover, run a final delta migration of any records modified during the migration window, then enable Odoo as the system of record.
What this step covers
We validate that Partner counts match, that Leads and Opportunities are distributed across the correct pipeline stages, that Document attachment counts match, and that User assignments are consistent with the SuiteCRM owner data. We deliver the AOW Workflow inventory document to the customer's admin team with Odoo Automated Actions and Studio equivalents listed per rule. We offer a one-week hypercare window for reconciliation issues; post-migration admin support, workflow rebuild, and Odoo Studio configuration are separate engagements.
SuiteCRM - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, number of custom Studio fields, and SuiteCRM version (7.x requires database extraction vs 8.x REST API). Odoo subscription cost (Community free or Enterprise per-user) and any Odoo.sh hosting fees sit outside the migration fee. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for SuiteCRM to Odoo CRM →Why teams move from SuiteCRM to Odoo CRM
- SuiteCRM's outdated PHP-based UI and maintenance burden drive teams to Odoo. Reviewers on G2, Capterra, and comparison sites cite clunky navigation, slow performance, and the requirement for a technical resource to manage upgrades and customisations as ongoing pain points. Odoo's modern web interface and application stack reduce the sysadmin dependency for teams that want a functional CRM without managing PHP infrastructure.
- Teams wanting CRM plus accounting, inventory, or project management in one platform migrate to Odoo. SuiteCRM is a pure CRM with no native accounting, stock, or HR module, requiring third-party integrations that SuiteCRM community reviewers describe as unreliable. Odoo's integrated ERP ecosystem consolidates those functions under one vendor and one database, eliminating the middleware and sync failures that plague SuiteCRM-and-a-separate-accounting-tool stacks.
- Odoo's ERP integrations are tighter than SuiteCRM's third-party ecosystem. Odoo connects natively to its own Accounting, Inventory, and e-commerce apps with shared data models and API consistency. SuiteCRM community members and comparison bloggers note that Google Calendar sync, third-party accounting plugins, and REST integrations require custom development and break regularly after SuiteCRM upgrades.
- Odoo's open-core model and Odoo.sh cloud hosting remove the infrastructure management burden that SuiteCRM's self-hosted model imposes. Teams leaving SuiteCRM hosted tiers for Odoo gain a managed cloud platform with automatic backups, version management via Odoo.sh, and a App store of tested integrations, replacing the self-hosted server maintenance that SuiteCRM requires even on its paid hosted plans.
- SuiteCRM 7.x extended support ends mid-2027 on the ESR branch, and standard 7.x is already unsupported. Teams running older SuiteCRM instances face a forced choice between an upgrade (which community forums document as high-risk for 7.x-to-8.x migrations) and a platform move. Odoo represents a clean break from the PHP stack and the upgrade risk entirely, which Prospeo and Crozdesk cite as a meaningful factor in migration decisions.
Questions, answered
SuiteCRM to Odoo CRM migration questions
How long does a SuiteCRM to Odoo CRM migration take?
Most migrations land between four and eight weeks for accounts under 15,000 Contacts and 3,000 Opportunities with no custom modules and no Document extraction complexity. Migrations with heavy Studio custom field use, multi-module SuiteCRM instances (Invoices, Cases, Campaigns, Contracts), large Document libraries, or SuiteCRM 7.x version extraction requirements move to ten to twenty weeks because of dependency-ordered staging, filesystem extraction, and Odoo pipeline-model reconciliation.
Do SuiteCRM AOW Workflows and automation rules migrate to Odoo?
No. SuiteCRM's Advanced Open Workflow module stores rule definitions as PHP-serialized objects in the database that are not accessible via the REST or SOAP API in a reusable format. These rules cannot be programmatically transformed into Odoo's Automated Actions or Studio workflows, which use a different event model (server actions, cron triggers, button triggers). We export a human-readable JSON inventory of every active AOW rule with its module, conditions, actions, and delays, and the customer's Odoo admin rebuilds them manually in Odoo Studio. This is a configuration task, not a data migration task, and is scoped separately from the record migration.
Can we migrate SuiteCRM Invoices and accounting data to Odoo?
We migrate SuiteCRM Invoice records to Odoo Account moves (type=out_invoice) if the destination Odoo instance includes the Accounting app. However, SuiteCRM Invoices are standalone records with no connection to a general ledger, accounts-receivable ledger, or payment reconciliation system. Full accounting migration — chart of accounts, journal entries, tax codes, payment reconciliation — is an accounting migration scope that is separate from the CRM migration. We recommend engaging an Odoo Accounting specialist to configure the chart of accounts and fiscal positions before Invoice records are imported so that the Invoice data lands in the correct journal.
How do we handle SuiteCRM Documents and file attachments?
SuiteCRM Documents store files on the server filesystem with database metadata references. We extract the upload/ directory alongside the database export, preserve file paths and permissions, compute checksums, and import files into Odoo's filestore as ir.attachment records linked to the parent Partner or crm.lead record. If the source SuiteCRM server is decommissioned or the filesystem is inaccessible, files cannot be recovered from the database alone. We flag this risk at discovery and recommend a pre-migration filesystem audit and backup as a prerequisite step.
Do we lose historical activity data (calls, emails, meetings, tasks) migrating to Odoo?
We migrate SuiteCRM activity records (calls, emails, meetings, tasks) as Odoo mail.message records linked to the resolved Partner or crm.lead. Call activities migrate as crm.phone.call records if the Odoo CRM instance includes the telephony feature, or as Note records otherwise. Email bodies, meeting dates, locations, and task descriptions are preserved. Activity ordering is maintained by setting the Odoo message date to the original SuiteCRM activity timestamp. However, SuiteCRM activity metadata such as email open/click tracking from the Campaigns module is summarized as Note records rather than native Odoo campaign response tracking, which is a known Odoo limitation.
What happens to SuiteCRM Custom Fields created in Studio?
We enumerate all SuiteCRM Studio custom fields during discovery (name, data type, containing module, relationship type). Each custom field is re-created in Odoo using Odoo Studio with the closest matching field type. Many2One relationships require the referenced module to be imported first; we sequence the import accordingly. Multi-select SuiteCRM fields that exceed Odoo's 50-value selection limit are converted to tags (res.partner.category) applied to the related Partner records. The customer approves the custom field translation map before migration begins, and Odoo Studio configuration is included as part of the schema design step.
Can FlitStack AI migrate SuiteCRM Cases and Campaigns as well as Contacts and Opportunities?
Yes. SuiteCRM Cases (Bugs module) migrate to Odoo Helpdesk Tickets or Project Tasks depending on the customer's intended Odoo app stack. Campaign records migrate to Odoo UTM Campaigns for marketing attribution. Target Lists from SuiteCRM Campaigns migrate as Contact Tags applied to the relevant Partner records. Target List membership (junction table of Contact ID and Target List ID) migrates as Partner tag assignments. The migration scope includes all standard SuiteCRM modules beyond Accounts, Contacts, Leads, and Opportunities, subject to the Odoo apps enabled on the destination instance.
Related migrations
Odoo implementation
Set up Odoo CRM and migrate into it as one engagement.
See the service → Zendesk Sell to Odoo CRMMapping · history · rollbackAct! to Odoo CRMMapping · history · rollbackMyCase to Odoo CRMMapping · history · rollbackMailchimp to Odoo CRMMapping · history · rollbackJonas Enterprise Service & Construction Software to Odoo CRMMapping · history · rollbackHubSpot to Odoo CRMMapping · history · rollback SuiteCRM to SalesforceMapping · history · rollbackSources: official documentation
- Export and import data — Odoo 19.0 documentation
- Import products — Odoo 19.0 documentation
- Odoo Online programmatic throughput limits — Odoo Forum
- Data Cleaning — Odoo 19.0 documentation
- Datetime field reference — Odoo 19.0 documentation
- Upload size limit in Odoo — Odoo Forum (128 MiB cap)
- Fields and widgets — Odoo 19.0 documentation (Studio)
Get a quote
Moving from SuiteCRM to Odoo CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Odoo CRM setup with you, then send a quote.
Get a quote