Skip to content
Get a quote

Odoo Enterprise to Odoo ERP migration

We migrate Contacts, Companies, Products, Orders, Invoices, and Projects from Odoo Enterprise into Odoo ERP with Enterprise-only module references stripped, Chart of Accounts and fiscal positions mapped for country localization, and every res.partner and product.product record reconciled against the destination schema before cutover.

Short answer

FlitStack AI migrates res.partners, product.template + product.products, sale.orders, purchase.orders and account.moves from Odoo Enterprise to Odoo ERP, 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.

By

Source Odoo Enterprise
DestinationOdoo ERP
res.partnerproduct.template + product.productsale.orderpurchase.orderaccount.move
Mapped field by field · sample run · one-click rollback

What moves from Odoo Enterprise to Odoo ERP?

Moving from Odoo Enterprise to Odoo ERP is typically a version upgrade, a self-hosted transition, or a downgrade from the paid Enterprise tier to the open-source Community edition or a self-managed Odoo instance.

Read the full summary

Odoo Enterprise stores data in the same PostgreSQL-backed res.partner and product.product models as Community, but carries Enterprise-only modules (CRM Enterprise, POS Enterprise, Documents, Social) whose table references become orphaned when the database is restored on a non-Enterprise instance. We handle this by extracting only the subset of modules with Community equivalents, preserving the full Chart of Accounts with country-matched fiscal localization, and flagging every Enterprise-specific model that will be lost in a downgrade so the customer's admin can decide whether to include it in a scrubbed migration. We do not migrate custom Python modules or third-party Odoo Apps as code; we deliver a written inventory of these for the customer's developers to port. Workflows, Automations, and Odoo Studio configurations are excluded from migration scope.

1:1

res.partner (Contacts / Companies) → res.partner

Odoo uses res.partner for both individuals and organizations across all modules.

How it maps

We extract all partner records via xmlrpc or PostgreSQL direct-read, preserving address fields, category tags, bank accounts, and custom fields defined via Odoo Studio or ir.model.fields. The destination res.partner schema is matched field-for-field; no transformation is required beyond type-mapping of any custom field data types. Parent-company relationships (commercial partner linkage) are preserved via the commercial_partner_id and parent_id fields, and partner_id references on every related document (sale orders, invoices, purchase orders) are resolved at migration time.

1:1

product.template + product.product (Products) → product.template + product.product

Product templates and their variants migrate as a bundle.

How it maps

We preserve product.category hierarchy, vendor pricelist entries (product.supplierinfo), product routes (make-to-order, dropship via stock.location.route), and product.attribute.value combinations. Bills of Materials and work order routing data (mrp.bom, mrp.routing) are covered in the Manufacturing object. Any Enterprise-only fields (e.g., pos_categ_id from POS Enterprise) are flagged and excluded from Community-compatible imports.

1:1

sale.order (Sales Orders) → sale.order

Sale orders are migrated with their order lines (sale.order.line) and linked delivery orders (stock.picking) and invoices (account.move).

How it maps

We preserve the picking state (assigned, done, cancelled) and invoice state (draft, posted, paid) from the source so the destination picks up the order in its current status rather than resetting to draft. The sale_journal_id is remapped to the destination's chart of accounts journal. If the source uses Enterprise-specific sale type workflows, those stages are stripped and mapped to the standard sale order states available in Community.

1:1

purchase.order (Purchase Orders) → purchase.order

Purchase orders migrate with their order lines, linked receipts (stock.picking), and vendor bills (account.move).

How it maps

We preserve receipt-to-bill matching which is critical for accounts payable accuracy; the destination account.move record carries the same reconcile linkage to the original purchase order. Picking state and invoice state are preserved. Any Enterprise-specific purchase approval workflows are excluded from migration scope.

mapping

account.move (Invoices and Bills) → account.move

Odoo Accounting stores posted invoices, vendor bills, and journal entries in account.move.

How it maps

We handle posted vs. draft records differently: posted invoices migrate with full line-item and tax mapping; draft invoices migrate for completion in the destination. Tax grid mappings and reconciliation records are preserved via account.full.reconcile and account.partial.reconcile where the destination schema supports them. We validate that the destination's tax codes can accept the source tax rates before committing the invoice batch.

mapping

account.account (Chart of Accounts) → account.account

Chart of Accounts entries are country-specific via fiscal localization modules.

How it maps

Account codes, types (receivable, payable, expense, revenue), and tax receipt tags must be mapped to the destination's country-matched localization. We use the country localization module of the destination instance to validate that each source account maps to a valid destination account code before importing. Cross-country localization migration is not attempted without explicit remapping of every affected account and tax code.

What moves13 objects
Odoo EnterpriseOdoo ERP
  • res.partnerres.partner1:1
  • product.templateproduct.template1:1
  • sale.ordersale.order1:1
  • purchase.orderpurchase.order1:1
  • account.moveaccount.movetransformed
  • account.accountaccount.accounttransformed

+ 7 more in the mapping below

How Odoo Enterprise and Odoo ERP 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.

DimensionOdoo EnterpriseOdoo ERP
License modelPaid per-user, per-month subscription on Standard ($19.90-$31.10/user/mo) or Custom ($44.80-$46.80/user/mo)Free open-source Community Edition or self-hosted Odoo with no per-user licensing fee
SupportOfficial support and version upgrades included in subscriptionCommunity support via forums; no guaranteed SLA or escalation path
Studio and advanced appsOdoo Studio, advanced accounting, and AI features included on Custom planStudio requires paid Enterprise; Community has no built-in app builder
HostingOdoo Online (SaaS) or Odoo.sh managed cloud includedSelf-hosted on any infrastructure; Community edition runs on-premises or on any cloud provider
Enterprise-only modulesCRM Enterprise, POS Enterprise, Documents, Social, and AI features availableNo equivalents; Enterprise-only modules cannot be installed or used in Community or self-hosted instances
Odoo.sh infrastructureGit-based CI/CD pipeline, managed PostgreSQL, staging environments on Odoo.shNo Odoo.sh; customer manages their own PostgreSQL, backups, and deployment pipeline
Per-user pricing at scaleLinear cost growth: 50 users on Standard runs roughly $1,500/month before implementation costsNo per-user fee; infrastructure cost is fixed regardless of user count

What to watch for in a Odoo Enterprise to Odoo ERP migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Enterprise-only module references break on Community

Odoo Enterprise stores data for modules that have no Community equivalent: CRM Enterprise, POS Enterprise, Documents, Social, and AI features.

How we handle it

When a PostgreSQL database dump from Enterprise is restored on a Community instance, the Community database cannot install these modules, leaving orphaned table references and view types that cause UI crashes on any page that queries the missing models. We avoid this by extracting only the subset of modules with Community equivalents, stripping ir_module_module entries for Enterprise-only modules from the database dump, and migrating data only from tables that have valid Community counterparts. We deliver a written inventory of every Enterprise-specific model that will be lost in the migration so the customer's admin can decide whether to scrub it from scope.

high

Legacy surcharge stacks onto support costs on older versions

As of April 2026, Odoo applies a 25% surcharge on support and upgrade fees for customers running Odoo versions more than two releases behind the current version.

How we handle it

This surcharge compounds annually, making version upgrades increasingly expensive the longer they are deferred. We flag the source Odoo version during scoping, calculate the effective annual cost difference between staying on the legacy version versus migrating to a newer Odoo ERP version, and factor this into the migration ROI analysis. For companies already paying the legacy surcharge, the migration cost is frequently offset within the first year of eliminated surcharge payments.

medium

XML-RPC API has no documented rate limit causing timeouts on large datasets

The Odoo External API uses XML-RPC over HTTP with no publicly documented rate limit per organization.

How we handle it

In practice, large batch operations (10,000+ records) encounter server-side timeouts or 503 errors on shared Odoo.sh infrastructure. We mitigate this by implementing exponential backoff with jitter between batches of 500 records, monitoring for HTTP 503 responses, and extracting data directly from PostgreSQL for read-heavy migrations where the API bottleneck is too constraining. For self-hosted Odoo Enterprise with direct PostgreSQL access, we use database direct-read as the primary extraction path to bypass API overhead entirely.

medium

Custom modules and third-party apps are excluded from official upgrade service

The Odoo Upgrade Service (upgrade.odoo.com) handles only core module data migration.

How we handle it

Any custom modules or third-party Apps from the Odoo Store are explicitly excluded from the upgrade scripts. OpenUpgrade, the community alternative, covers some third-party modules but Odoo v19 scripts were still in early pull requests as of 2024. We scope custom module count and complexity during the discovery call, port custom module Python code to the target version API where feasible, and document any custom modules that require developer-level intervention. Third-party app data migrates only if the app has Community-compatible database tables.

medium

Fiscal localization binds accounting data to country

Odoo's accounting module ships with country-specific fiscal localization modules that embed tax rates, Chart of Accounts templates, and reporting requirements (e.g., FEC for France, SII for Spain, VAT MOSS for EU).

How we handle it

Migrating accounting data between Odoo instances in different countries requires swapping the localization module, which restructures the entire accounting configuration. We treat fiscal positions, tax codes, and chart of accounts entries as domain-specific objects requiring a country-matched migration path. We do not attempt cross-country accounting localization migration without explicitly remapping every affected account, tax code, and fiscal position to the destination's country localization.

How the migration runs

  1. Discovery and version audit

    We audit the source Odoo Enterprise instance across Odoo version, installed modules, custom models (ir.model), third-party Apps, and Enterprise-only module usage.

    What this step covers

    We extract the module list via xmlrpc or PostgreSQL ir_module_module query, identify every module that has no Community equivalent, and flag these as data-loss candidates in the written scope document. We also assess data quality by sampling partner records, product counts, open order volumes, attachment file sizes, and historical journal entry age. The discovery output is a written migration scope, a data loss inventory for Enterprise-only modules, and a destination Odoo version and hosting recommendation.

  2. Destination schema design and localization check

    We design the destination schema by matching the source's chart of accounts, fiscal positions, and tax codes to the destination's country-matched localization module.

    What this step covers

    We pre-create any custom models and custom fields in the destination Odoo instance before data import begins. If the destination is in a different country than the source, we flag all fiscal position and tax mappings for admin-level remapping rather than attempting automatic migration. For self-hosted destinations, we verify that the destination PostgreSQL instance has adequate storage and network access for the migration workload.

  3. Sandbox migration and reconciliation

    We run a full migration into a staging or sandbox destination Odoo instance using production-equivalent data volume.

    What this step covers

    The customer's Odoo administrator reconciles record counts (partners in, products in, orders in, invoices in, project records in), spot-checks 25-50 records against the source for field-level accuracy, and validates fiscal position and tax code mappings. Any mapping corrections, custom field additions, or Enterprise-only table exclusions are resolved in this phase. Sandbox sign-off from the customer's admin is required before production migration begins.

  4. Migration script development with chunking and backoff

    We build ETL scripts that extract from the source Odoo Enterprise instance via xmlrpc (for Odoo Online or Odoo.sh) or PostgreSQL direct-read (for self-hosted), transform records to match the destination schema, and load via xmlrpc into the destination.

    What this step covers

    Scripts implement batch chunking at 500 records per batch, exponential backoff with jitter on HTTP 503 responses, and parent-record lookup resolution so that foreign key references (account_id on invoice lines, product_id on order lines, partner_id on projects) are satisfied at the moment of insert rather than via post-import reconciliation. Custom model records are migrated last after all standard object dependencies are resolved.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Chart of Accounts and Fiscal Positions (account.account, account.fiscal.position, account.tax), Partners (res.partner), Products (product.template, product.product, product.category), Inventory (stock.warehouse, stock.location), Sales Orders (sale.order with picking and invoice links), Purchase Orders (purchase.order with receipt and vendor bill links), Invoices (account.move), Projects and Tasks (project.project, project.task), Employees (hr.employee with contracts and attendance), Custom Models (x_custom_model), Attachments (ir_attachment with filestore reconstruction).

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. We freeze source writes during cutover and run a final delta migration of any records modified during the window.

  6. Cutover, validation, and workflow rebuild handoff

    We validate the destination against control totals from the source: partner count, product count, open order balance, posted invoice total, and inventory quant values as of cutover date.

    What this step covers

    We deliver the written inventory of Enterprise-only modules and custom modules that were excluded from migration scope, along with a rebuild recommendation document for the customer's developers. We do not rebuild custom Python modules, automations, or Odoo Studio configurations; these require the customer's developers to port. We support a one-week hypercare window where we resolve any data reconciliation issues raised by the customer's team after go-live.

Odoo Enterprise Odoo ERP
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Odoo ERPRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

4-8 weeksTypical, smaller accounts
10-16 weeksLarge or heavily customised accounts

Pricing reflects migration complexity, data volume, and custom module scope rather than Odoo licensing costs. Odoo Community Edition itself carries no license cost; infrastructure hosting (self-managed VM, AWS, Azure) sits outside the migration fee and remains the customer's fixed operational cost. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Odoo Enterprise to Odoo ERP →

Why teams move from Odoo Enterprise to Odoo ERP

  • Odoo Enterprise pricing compounds at scale and the 25% legacy surcharge introduced in April 2026 stacks onto support fees for customers on Odoo versions more than two releases behind current. A 50-user team on Standard pays roughly $1,500/month in Enterprise licensing alone before implementation or partner costs. Switching to Odoo Community eliminates the per-user fee entirely, converting a recurring licensing cost into a fixed infrastructure cost that scales with servers rather than headcount.
  • Odoo releases a new major version annually with measurable performance improvements. Reviewers and Odoo partners consistently cite speed gains (Odoo 14 front-end reported as 3.5x faster than v13, v13 back-end 5x faster than v12) and new module integrations as the primary driver for version upgrades. Companies on Odoo 15 or earlier also lose official support, making version upgrades a security and continuity requirement.
  • Enterprise-only modules like CRM Enterprise, POS Enterprise, Documents, and Social create data locked inside the Enterprise edition. Companies that want full ownership of their data model, deployment infrastructure, and upgrade cadence move to self-hosted Odoo ERP to eliminate the vendor lock-in that comes with Odoo Online and Odoo.sh hosting.
  • Custom module development on Odoo Enterprise requires Python and Odoo ORM expertise, and each annual version upgrade demands custom code porting. Odoo partners and migration consultants cite this as the most common hidden cost driver, with OpenUpgrade (the community migration tool) covering only some third-party modules as of 2024. Companies moving to Odoo ERP with a cleaner codebase reduce long-term maintenance burden.
  • Implementation and support responsiveness from Odoo and its official partners is inconsistent for Enterprise customers. Reviewers and forum participants cite delayed escalation on business-critical issues and opaque pricing on partner-delivered implementations as ongoing pain points that drive companies toward the self-managed Community model where they control their own support relationships.

Questions, answered

Odoo Enterprise to Odoo ERP migration questions

How long does an Odoo Enterprise to Odoo ERP migration take?

Most migrations land between four and eight weeks for Odoo instances with fewer than 50,000 partner records, 10,000 products, and straightforward accounting localization (single country, no cross-border tax complexity). Migrations with heavy custom module development, large historical invoice archives (over 100,000 posted journal entries), multi-company structures, or cross-country accounting localization move to ten to sixteen weeks because of PostgreSQL direct-read overhead, fiscal position remapping, and custom module porting. The source Odoo version also matters: v16 and earlier migrations require more compatibility checking against Community than v17-v18 migrations.

What Odoo Enterprise data does not migrate to Odoo ERP?

We do not migrate custom Python modules as code. Any module written for Odoo Enterprise must be reviewed by the customer's developers to port to the target Odoo version's ORM API. We do not migrate Odoo Studio configurations (views, action rules, automated actions) or Enterprise-specific modules including CRM Enterprise, POS Enterprise, Documents, Social, and AI features, as no Community equivalents exist for these tables. We deliver a written inventory of every excluded module, its associated database tables, and the number of records affected so the customer's admin can assess business impact.

Can we migrate from Odoo Enterprise Online to a self-hosted Odoo ERP instance?

Yes. We support migrations from Odoo Online (SaaS), Odoo.sh, and self-hosted Enterprise instances. For Odoo Online and Odoo.sh, we extract via the xmlrpc External API. For self-hosted instances with PostgreSQL direct access, we use direct database read as the primary extraction path, which bypasses xmlrpc rate limit constraints entirely. The destination can be Community Edition on any infrastructure the customer manages, including a new Odoo.sh instance, AWS EC2, Azure VM, or an on-premises server. The migration path does not depend on hosting model.

Do Odoo Workflows, Automations, and Studio configurations migrate?

No. Odoo Workflows, Server Actions, Automated Actions, and Odoo Studio view configurations are stored as XML metadata in ir.actions, ir.rule, and ir.ui.view tables. These do not migrate because they reference Enterprise-specific view types, field definitions, and action types that do not exist in Community. We deliver a written inventory of every active Workflow, Automated Action, and Studio configuration with its trigger, conditions, and actions so the customer's Odoo administrator or developer can rebuild them in the destination. Custom ir.cron scheduled actions also require manual rebuild.

How does FlitStack AI handle attachment migration including the filestore?

Odoo stores attachments in two locations: the PostgreSQL ir_attachment table (with db_datas for small files) and the filestore directory. We extract both sources during migration. For Odoo Online and Odoo.sh, the filestore is accessed via the webdav interface or direct storage bucket read. For self-hosted, the filestore path is read from the Odoo configuration file. We reconstruct the filestore tree on the destination, base64-encode binary attachments for xmlrpc transmission where necessary, and relink ir_attachment records to the reconstructed filestore paths. Large filestore volumes (over 50 GB) require direct storage transfer rather than API-based migration.

How does the 25% legacy surcharge affect the migration decision?

As of April 2026, Odoo applies a 25% surcharge on support and upgrade fees for customers running Odoo versions more than two releases behind the current version. This surcharge compounds annually and applies to the per-user Enterprise subscription cost, making the effective annual cost of staying on a legacy version significantly higher than the sticker price suggests. We factor the legacy surcharge into the migration ROI analysis by calculating the customer's current annual cost (including surcharge), the annual Odoo ERP infrastructure cost after migration, and the payback period for the migration investment. For customers already on Odoo 15 or earlier, the surcharge frequently tips the economics in favor of migration within 12-18 months.

Get a quote

Moving from Odoo Enterprise to Odoo ERP?

Tell us roughly how many records and objects you have. We scope the mapping and the Odoo ERP setup with you, then send a quote.

Get a quote