---
title: "NetSuite to Odoo ERP Migration: Field Mapping & Rollback"
description: "Migrate NetSuite to Odoo ERP with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/erp/netsuite/to/odoo-erp"
---

# NetSuite to Odoo ERP migration

We migrate Accounts, Customers, Vendors, Items, Transactions, and Custom Records from NetSuite into Odoo ERP with the subsidiary-to-company structural map resolved upfront, journal entry carry-forward sequenced as opening balances or historical replay, and every NetSuite custom field registry recreated as Odoo custom fields before cutover.

Short answer

FlitStack AI migrates accounting > chart of accounts, contacts, product template + product variants, sale orders and account moves from NetSuite 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.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/erp/netsuite/to/odoo-erp#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source NetSuite ![](https://flitstack.ai/platforms-trim/netsuite.webp)

Destination Odoo ERP ![](https://flitstack.ai/platforms-trim/odoo-erp.webp)

Accounting > Chart of Accounts Contact Product Template + Product Variants Sale Order Account Move

Mapped field by field · sample run · one-click rollback

## What moves from NetSuite to Odoo ERP?

Moving from NetSuite to Odoo ERP is a structural migration, not a record copy.

Read the full summary

NetSuite's single-database subsidiary model lets one environment represent multiple legal entities with intercompany eliminations; Odoo uses a multi-company architecture where each legal entity is a separate database pod with shared contacts and products. We resolve that mapping during discovery, flagging whether each NetSuite subsidiary maps to a distinct Odoo company or whether consolidation happens at the reporting layer. Historical journal entries require an explicit carry-forward policy: either replay every historical posting date with original exchange rates, or create fresh opening-balance entries and close the historical periods in NetSuite. NetSuite custom fields (custbody\_\*, custrecord\_\*, custentity\_\*) have no public schema catalog; we run a metadata discovery pass against SuiteQL before building the migration map. Workflows, SuiteFlow automations, and SuiteScript customizations do not migrate as code; we deliver a written inventory for the customer's Odoo partner to rebuild as Studio actions or Python modules. Odoo's Community Edition is open-source and free to run; Enterprise runs approximately $24 per user per month with hosting included, making the five-year cost differential versus NetSuite's tiered subscription significant for mid-market buyers.

1:1

### Chart of Accounts (Accounts) → Accounting > Chart of Accounts

NetSuite account type codes (0=Bank, 1=AR, 2=Inventory, 5=Fixed Assets, 10=AP, 21=Income, 23=COGS, 24=Expense) map to Odoo Account types.

How it maps

We preserve acctNumber as the account code, account name as the account label, and NetSuite's isInactive flag as a archived state in Odoo. Eliminations accounts in NetSuite's subsidiary model become Odoo inter-company accounts under multi-company configuration.

1:1

### Customer → Contact (with Customer = True)

NetSuite Customers map to Odoo Contacts with the Customer flag enabled.

How it maps

We preserve address fields (billingAddress, shippingAddress), tax registration fields, credit limit, payment terms, and currency settings. NetSuite's custentity\_\* custom fields on Customer records migrate as Odoo custom fields on res.partner via Studio or Python field definition.

1:1

### Vendor → Contact (with Vendor = True)

NetSuite Vendors map to Odoo Contacts with the Vendor flag enabled, enabling the purchase module to function.

How it maps

We preserve tax ID, bank account details, payment terms, and the vendor-specific address subrecords. Custom fields on Vendor (custentity\_\*) migrate alongside standard fields as Odoo res.partner custom fields.

1:1

### Item (Inventory Assembly, Non-Inventory, Service) → Product Template + Product Variants

NetSuite inventory items, assemblies, non-inventory items, and service items map to Odoo Product Templates.

How it maps

We preserve the item's SKU (stored in itemId or itemNumber), unit of measure, cost, sales price, product type mapping (inventory item = storable product, assembly = consignment or kit depending on Odoo configuration), BOM relationships on assemblies, and landed cost fields. Lot and serial number settings map to Odoo's lot/serial tracking on stock.move.

1:1

### Sales Order → Sale Order

NetSuite Sales Orders map to Odoo Sale Orders.

How it maps

We preserve order date, customer reference (poNumber), line items with quantities and prices, tax amounts, shipping address, incoterms mapping where present, and order status (Pending Fulfillment maps to Sale Order state 'sale', Shipped to 'done'). Open versus closed status is determined by shipping status in NetSuite at the time of extraction.

mapping

### Invoice (AR) → Account Move (Invoice type)

NetSuite AR invoices map to Odoo Account Moves of type 'out\_invoice'.

How it maps

We preserve invoice number, invoice date, due date, line-level amounts with taxes, exchange rates on foreign-currency invoices, and payment terms. NetSuite's custbody\_\* custom fields on transaction headers migrate as Odoo account.move custom fields. Historical paid invoices are migrated as posted moves; open AR invoices are migrated with state='draft' pending payment reconciliation.

******What moves 12 objects

NetSuite Odoo ERP

- Chart of Accounts Accounting > Chart of Accounts 1:1
- Customer Contact 1:1
- Vendor Contact 1:1
- Item Product Template 1:1
- Sales Order Sale Order 1:1
- Invoice Account Move transformed

\+ 6 more in the mapping below

## How NetSuite 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.

| Dimension              | NetSuite                                                                                        | Odoo ERP                                                                                                |
| ---------------------- | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Architecture model     | Single database with subsidiary-level segmentation                                              | Modular apps with separate database per company pod in multi-company setups                             |
| Multi-entity handling  | Subsidiaries within one NetSuite database with intercompany eliminations                        | Separate Odoo company databases linked via multi-company rules, or separate instances                   |
| Custom field registry  | custbody\_\*, custcol\_\*, custentity\_\*, custrecord\_\* with no public schema catalog         | Odoo Studio custom fields discoverable via Settings > Technical; Python fields require developer access |
| Pricing model          | Named-user subscription at $999/month base plus $99-$149/user with tiered transaction-line caps | \~$24/user/month for Enterprise (hosting included) or free Community Edition self-hosted                |
| Customization approach | SuiteBuilder and SuiteFlow for non-developer admins; SuiteScript for custom code                | Odoo Studio for point-and-click; Python modules and XML definitions for developer-level customization   |
| E-invoicing            | Widely described as immature and unreliable by G2 reviewers                                     | Module-dependent; FatturaPA and other localization modules available per-country                        |
| Workflow automation    | SuiteFlow visual builder with triggers, conditions, and actions                                 | Studio automated actions (record rules, server actions) plus Python workflows                           |

## What to watch for in a NetSuite 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

### Subsidiary-to-company map is structural, not cosmetic

NetSuite's subsidiary model lets one database represent multiple legal entities with intercompany eliminations.

How we handle it

Odoo requires each legal entity to be a separate company database pod under multi-company rules, or separate Odoo instances entirely. Each NetSuite subsidiary must map to a distinct Odoo company with its own Chart of Accounts, fiscal year settings, and posting journals. Getting this wrong causes Odoo posting rejections at import time because the company context on an account.move line must reference the correct Odoo company. We build the subsidiary-to-company map during the discovery phase and validate the multi-company configuration in a staging environment before any data lands.

high

### Custom fields and custom records have no public schema

NetSuite attaches custom fields to nearly every standard object using custbody\_\*, custcol\_\*, custentity\_\*, and custitem\_\* prefixes, and Custom Record Types use custrecord\_\* script IDs.

How we handle it

Every NetSuite environment has a unique set of these fields that cannot be discovered via public documentation. We run a metadata discovery pass against the account's SuiteQL endpoint to enumerate all active custom objects and fields before building the migration map. Destination Odoo custom fields and models must be pre-created in Odoo Studio or via Python before data import begins. Custom fields on transaction lines (custcol\_\*) require special handling in SOAP/REST payloads and must map to Odoo account.move.line custom fields.

high

### API concurrency limits gate extraction throughput

NetSuite enforces a maximum number of simultaneous API requests per account: 15 for default tier, up to 55 with SuiteCloud Plus licenses on Tier 5.

How we handle it

We monitor concurrency headers and implement exponential backoff with a queue system. If we exceed concurrency during a large migration, NetSuite queues or rejects requests with 429/403 errors. We scope each migration within the account's tier ceiling and chunk exports into date-bounded batches of up to 1,000 records per request. We also flag when a migration scope will push the account over its monthly transaction-line tier ceiling before committing to a timeline.

medium

### Journal entry carry-forward policy must be decided before data sequencing

NetSuite journal entries include prior-period adjustments, intercompany eliminations, and currency revaluation rows that carry original posting dates and exchange rates.

How we handle it

Some organizations prefer to replay historical journal entries in Odoo with original dates and rates preserved. Others prefer to carry forward open-period balances only as fresh opening-balance entries, closing historical periods in NetSuite before cutover. These are fundamentally different migration paths with different ETL logic. We present both options to the customer's finance team during scoping and capture the chosen policy in the migration contract before sequencing data.

medium

### NetSuite intercompany eliminations cannot be directly migrated

NetSuite's subsidiary model natively generates intercompany elimination entries as part of consolidated reporting.

How we handle it

In Odoo, intercompany transactions require configuration of Odoo's Inter-Company Transactions feature, which creates mirrored documents between companies in a multi-company setup. NetSuite's historical elimination journal entries cannot be replayed in Odoo because Odoo's elimination logic runs prospectively on future transactions, not retroactively on historical data. We flag the elimination gap during scoping and recommend that the customer's finance team handle period closures and elimination adjustments manually or via an Odoo partner's post-migration accounting review.

## How the migration runs

1. ### Discovery and custom field registry enumeration

   We audit the source NetSuite account across service tier (Standard, Premium, Enterprise, Ultimate), subsidiary count and hierarchy, transaction volume by type, custom record type count, custom field registry via SuiteQL, and open AR/AP aging balances.

   What this step covers

   We extract a representative sample of each transaction type to validate field coverage before building the full ETL map. The discovery output is a written migration scope, subsidiary-to-company map, journal carry-forward policy recommendation, and an Odoo edition recommendation (Community free self-hosted vs Enterprise hosted).

2. ### Staging environment setup and custom field schema creation

   We provision a staging Odoo environment matching the production configuration.

   What this step covers

   We create the Chart of Accounts structure, multi-company configuration for each NetSuite subsidiary, and all custom field definitions (via Odoo Studio or Python model definition) matching the discovered NetSuite custom field registry. The Odoo staging environment runs in parallel with the production NetSuite account during UAT so that the customer can validate data accuracy before production cutover.

3. ### Data quality audit and cleansing

   We extract representative samples from NetSuite across each object type and surface data quality issues in writing: duplicate customer and vendor records, inconsistent item pricing, misaligned tax codes, missing required fields on transactions, and any records with invalid foreign currency exchange rates.

   What this step covers

   We do not silently clean data. Every cleansing decision is documented and presented to the customer's admin for approval before ETL scripts are finalized.

4. ### ETL script development and sandbox rehearsal

   We build ETL scripts with automated reconciliation: for each object, we generate control totals (record count, sum of line amounts, sum of balances) and validate them against NetSuite exports before any Odoo import.

   What this step covers

   Scripts handle the subsidiary-to-company mapping, currency exchange rate resolution using NetSuite's exchange rate table, and parent-record lookup resolution (e.g., customer must exist in Odoo before a sale order referencing it is imported). We run a first full rehearsal migration into staging, reconcile all control totals, and fix issues in code before proceeding.

5. ### User acceptance testing in staging

   The customer's finance and operations leads validate migrated records in the staging Odoo environment.

   What this step covers

   They spot-check 25-50 records per object against the NetSuite source, verify that open AR and AP aging matches the source report, confirm that journal carry-forward matches the agreed policy, and sign off the schema and mapping before production migration begins. Any corrections discovered during UAT are made in the ETL scripts and re-reconciled in staging.

6. ### Production migration and cutover

   We freeze NetSuite writes during the cutover window, run a delta migration for any records modified during the migration process, then load into production Odoo in dependency order: Chart of Accounts, Contacts (Customers then Vendors), Products, Open AR/AP aging entries, Sale Orders, Vendor Bills, Journal Entries, then Custom Records last.

   What this step covers

   Each phase emits a row-count reconciliation report. We enable Odoo as the system of record and maintain a four-to-eight-week read-only window on NetSuite in case discrepancies surface during hypercare. We deliver the SuiteFlow and custom SuiteScript inventory document to the customer's Odoo partner for Studio and Python workflow rebuild.

![](https://flitstack.ai/platforms/netsuite.svg) NetSuite ![](https://flitstack.ai/platforms/odoo-erp.svg) Odoo ERP

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Odoo ERP Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**4-8 weeks** Typical, smaller accounts

**10-16 weeks** Large or heavily customised accounts

A quote scales with data volume, custom field complexity, subsidiary count, and whether historical journal entries are replayed or carried forward as opening balances. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for NetSuite to Odoo ERP →](https://flitstack.ai/contact)

## Why teams move from NetSuite to Odoo ERP

- NetSuite renewal uplifts surprise organizations with edition upgrades triggered by user or transaction growth at contract renewal. Odoo Enterprise pricing at roughly $24 per user per month with hosting included presents a fixed, predictable cost structure. A business case analysis by Novobi found a five-year cumulative savings exceeding $490,000 for a 30-user deployment, with break-even between years one and two even after full implementation costs. Reddit threads and O2B Technologies comparisons confirm that organizations facing NetSuite renewal shock actively evaluate Odoo as a cost-stable replacement that avoids tier-based billing surprises.
- NetSuite's HelpDesk module receives 386 mentions on G2 as inadequate for serious customer service operations, with reviewers citing missing features, poor UX, and forced reliance on dedicated ticketing platforms. Odoo's native Helpdesk app provides ticket pipelines, SLA tracking, rating surveys, and knowledge base integration as standard functionality, eliminating the need for a separate third-party ticketing system and its associated integration cost and data siloed from the ERP.
- NetSuite page load times of 30-60 seconds for routine operations frustrate daily users. G2 and Capterra reviews consistently cite slow transaction saves and follow-up action delays as a top pain point for NetSuite environments with large transaction volumes or complex custom record types. Odoo's Python-based architecture with modular apps handles transactional CRUD operations with significantly faster response times in typical deployment configurations, which matters for teams processing high transaction volumes daily.
- NetSuite is a proprietary Oracle SaaS platform with no source code access, requiring all customization through SuiteScript or SuiteFlow at additional licensing cost as tier grows. Odoo's open-source Community Edition provides full source code access, enabling in-house Python developers to extend functionality without Oracle's pricing gate. Versich and Broken Rubik comparisons note that organizations with developer resources prefer Odoo's code ownership model and faster iteration cycle versus NetSuite's developer-constrained SuiteScript environment.
- NetSuite enforces API concurrency ceilings (15 default, up to 55 with SuiteCloud Plus) and monthly transaction-line tier caps (Standard: 200K, Premium: 2M, Enterprise: 10M, Ultimate: 50M) that constrain data extraction and migration throughput. Odoo's XML-RPC and JSON-RPC APIs carry no per-account concurrency ceiling beyond server resource limits, removing the extraction bottleneck that NetSuite environments hit when attempting large-volume exports or migrations.

Questions, answered

## NetSuite to Odoo ERP migration questions

How long does a NetSuite to Odoo ERP migration take?

Typical migrations land between four and eight weeks for accounts with under 50,000 transactions, up to three subsidiaries, and no custom record types. A documented SISU case study showed a 47-user, nine-app migration completed in 42 days with Bista Solutions as the implementation partner. Mid-size migrations with multiple subsidiaries, large transaction histories, or custom record type complexity requiring metadata discovery move to ten to sixteen weeks. The journal carry-forward policy (historical replay vs opening balances) and data cleansing scope are the two biggest timeline drivers.

Do NetSuite SuiteFlow workflows and SuiteScript customizations migrate to Odoo?

No. SuiteFlow and SuiteScript are NetSuite-specific automation and code layers with no direct Odoo equivalent. Odoo handles automation through Studio server actions and automated actions, which are structurally different from SuiteFlow's trigger-condition-action model. We do not migrate workflows or custom scripts as code. We deliver a written inventory of every active SuiteFlow workflow and SuiteScript customization with its trigger, conditions, and actions, plus a recommended Odoo Studio equivalent or Python module approach for the customer's Odoo partner to rebuild. This inventory is delivered before cutover so that rebuilding can proceed in parallel with the data migration.

Can we migrate our historical journal entries with original posting dates and exchange rates?

Yes, if the customer chooses the historical replay option during scoping. We extract NetSuite journal entry lines with original posting dates, account assignments, debit and credit amounts, currency, and exchange rate. We create Odoo account.move records with those original dates and rates preserved. This option requires more ETL development and a longer reconciliation phase because Odoo must permit prior-period postings. Alternatively, the customer can choose the opening-balance option: we extract period-end GL balances from NetSuite as of the cutover date and create fresh Odoo opening-balance entries, carrying forward net balances rather than replaying every historical row. Both options are presented and decided during the discovery phase.

How do we handle multiple NetSuite subsidiaries in Odoo?

NetSuite's subsidiary model allows one database to represent multiple legal entities with intercompany eliminations at the subsidiary level. Odoo handles this differently: each legal entity is a separate company database pod under a multi-company configuration, or a separate Odoo instance. Each NetSuite subsidiary maps to a distinct Odoo company with its own Chart of Accounts, fiscal year, and posting journal. Intercompany transactions in NetSuite become cross-company journal entries in Odoo under the multi-company configuration. We build the subsidiary-to-company map during discovery and validate the multi-company configuration in staging before any data lands.

Do we lose NetSuite custom fields and custom records during migration?

No, but they require pre-work. NetSuite custom fields (custbody\_\*, custcol\_\*, custentity\_\*, custitem\_\*) and Custom Record Types (custrecord\_\*) have no public schema catalog and vary by environment. We run a metadata discovery pass against the NetSuite SuiteQL endpoint before building the migration map to enumerate every active custom field and custom record type. Destination Odoo custom fields and models are then created in Odoo Studio or via Python before data import begins. Custom Records migrate last because they often reference Customers, Vendors, and Items that must exist in Odoo first to satisfy relational integrity.

Can Odoo handle our NetSuite e-invoicing and tax compliance requirements?

Odoo's e-invoicing capability is localization-specific rather than a single global module. Countries supported include Italy (FatturaPA, SDI), Spain (FacturaE), France (Chorus Pro), Brazil (NF-e), Mexico (CFDI), and others through Odoo's community and partner-developed localization modules. NetSuite's e-invoicing is described by G2 reviewers as immature and unreliable with ongoing workarounds. We assess the customer's country-specific e-invoicing requirements during discovery and flag whether Odoo's localization modules cover the compliance needs or whether a separate third-party e-invoicing middleware layer is required post-migration.

What happens to our NetSuite data after migration?

NetSuite remains in a read-only hold state for four to eight weeks after Odoo go-live during the hypercare reconciliation period. The customer's NetSuite account continues running under its existing contract during this window, which protects against rollback risk if Odoo reconciliation surfaces discrepancies. After hypercare closes, the customer can choose to let the NetSuite contract lapse, renew at a reduced scope, or archive the account for compliance purposes. We do not delete or export NetSuite data without explicit written instruction from the customer; data ownership remains with the customer throughout.

## Related migrations

[![](https://flitstack.ai/platforms-trim/odoo-erp.webp) Migrate to **Odoo ERP** Every source we move into Odoo ERP, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/erp/odoo-erp)

### [Odoo implementation](https://flitstack.ai/services/odoo-implementation)

[Set up Odoo ERP and migrate into it as one engagement.](https://flitstack.ai/services/odoo-implementation)

[See the service →](https://flitstack.ai/services/odoo-implementation) [**Atlas ERP to Odoo ERP** Mapping · history · rollback](https://flitstack.ai/migrations/erp/atlas-erp/to/odoo-erp) [**ERPNext to Odoo ERP** Mapping · history · rollback](https://flitstack.ai/migrations/erp/erpnext/to/odoo-erp) [**Sage Intacct to Odoo ERP** Mapping · history · rollback](https://flitstack.ai/migrations/erp/sage-intacct/to/odoo-erp) [**Odoo Enterprise to Odoo ERP** Mapping · history · rollback](https://flitstack.ai/migrations/erp/odoo-enterprise/to/odoo-erp) [**NetSuite to Business Central** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/microsoft-dynamics-365-business-central) [**NetSuite to Acumatica** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/acumatica) [**NetSuite to Epicor Prophet 21** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/epicor-prophet-21)

## Sources: official documentation

1. [Export and import data — Odoo 19.0 documentation](https://www.odoo.com/documentation/19.0/applications/essentials/export_import_data.html)
2. [Export and import data — Odoo 14.0 documentation (Country/Database ID/External ID resolution)](https://www.odoo.com/documentation/14.0/applications/general/export_import_data.html)
3. [Definitive foolproof steps for a successful import — Odoo Forum (Many2many comma-separated)](https://www.odoo.com/forum/help-1/is-there-a-definitive-foolproof-steps-for-a-successful-import-doc-39822)
4. [Upload size limit in Odoo — Odoo Forum (64 MiB Odoo.sh, 128 MiB self-hosted)](https://www.odoo.com/forum/help-1/upload-size-limit-in-odoo-221095)
5. [Fields and widgets — Odoo 19.0 documentation (Studio)](https://www.odoo.com/documentation/19.0/applications/studio/fields.html)
6. [Batch Import — Odoo Forum (Odoo Online throttling)](https://www.odoo.com/forum/help-1/batch-import-262164)
7. [What Does Odoo Migration Really Cost? Transparent Pricing Breakdown — Aspire Softserv](https://dev.to/aspire-softserv/what-does-odoo-migration-really-cost-a-transparent-pricing-breakdown-for-2025-48fj)

Get a quote

## Moving from NetSuite 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](https://flitstack.ai/contact)
