Implementation · Migration

Migrating from NetSuite to Odoo: what moves and what changes

Subsidiaries, segments, items, saved searches and scripts all have an Odoo counterpart, but few map one to one. Here is the concept map, what data to bring across, what to archive, and how to prove the numbers match at cutover.

By Octagotech Team9 min readUpdated

Key takeaways

  • Work back from your NetSuite renewal date, and cut over at a fiscal period end.
  • Subsidiaries become companies in one database; classes, departments and locations become analytic plans.
  • Move masters, open items, stock on hand and opening balances. Archive the full history outside Odoo.
  • Prove the cutover by reconciling trial balance, AR and AP aging and stock valuation against NetSuite.
  • Re-specify SuiteScript as requirements before anything is rewritten in Python.

Companies rarely leave NetSuite because it stopped working. They leave because the license bill grew with every module and subsidiary, or because every change needs a SuiteScript developer. Either way, the migration has the same shape: translate NetSuite's concepts into Odoo's, move what the business needs to operate, archive the rest, and prove the numbers match at cutover.

The Odoo terms in this guide are Odoo 19's. Odoo 20 shipped in September 2026, and for most new implementations we still start on 19 and move up once 20 matures. We do not quote a standard timeline for a NetSuite migration. Subsidiaries, SuiteScript and integrations set the scope, and only an audit shows how much of each you have.

Why companies move from NetSuite to Odoo

Three reasons come up most. Cost: NetSuite licenses per user and per module, while Odoo's paid plans include every app for one per-user fee. Fit: manufacturers and distributors often find Odoo's MRP, inventory and native eCommerce closer to how they run. Control: Odoo's framework is open, so you choose the hosting and can change partners without changing platforms. NetSuite stays stronger for complex multi-entity consolidation and revenue recognition. Our Odoo vs NetSuite comparison and the Odoo vs SAP vs NetSuite cost comparison weigh both sides.

Time the cutover around renewal and period ends

Two dates set the window. The first is your NetSuite renewal. NetSuite is sold on subscription terms, usually annual, and you should assume access ends when the term does. Find the renewal date and any notice period in your contract, then work backward so that go-live, stabilization and the full history export all land inside the current term with room to spare. If that looks tight, raise an extension or read-only access before renewal talks start.

The second is your fiscal calendar. Odoo's guidance for companies arriving from other accounting software calls the fiscal year-end the easiest point to switch, a tax period end workable, and the middle of a tax period a choice to avoid, because returns then combine data from two systems. The caveat is that a year-end cutover stacks your first weeks on Odoo on top of the year-end close and the audit. If finance cannot carry both, a quarter-end is the next best choice. Avoid peak season, and remember that a mid-year switch splits year-to-date totals, such as vendor payments reported on 1099s in the US, across two systems.

How NetSuite concepts map to Odoo 19

The decisions in this table shape the import templates, the reports and the training.

NetSuiteOdoo 19What to decide
SubsidiariesCompanies in one multi-company databaseWhich subsidiaries trade with each other, and whether inter-company transactions and consolidation cover your eliminations
Chart of accountsChart of accounts from the fiscal localizationRename and recode Odoo's standard accounts where they match; create the rest
Classes, departments and locations as segmentsAnalytic plans holding analytic accountsOne plan per segment, mandatory where NetSuite required it
Items and item typesProducts typed Goods, Service or Combo, with Track Inventory on or offTracking by quantity, lot or serial number; bills of materials for assemblies and kits
Locations and binsWarehouses and internal locations, with Storage Locations enabledWhich locations are physical sites and which are only reporting segments
Customers and vendorsContacts, where one record can be bothDuplicates merged; payment terms and fiscal positions set before import
Saved searches and reportsList, pivot and graph views saved as favorites, accounting reports, spreadsheets linked to Odoo dataWhich searches people still use; rebuild those, drop the rest
Workflows (SuiteFlow)Automation rules and server actionsApprovals and field updates re-created and tested on real records
SuiteScriptCustom Odoo modules in PythonWhat each script does, written as a requirement before any code
Multi-currencyMulti-currency with automatic rates and exchange difference entriesHistorical rates for open foreign-currency invoices

Four rows need more thought. Subsidiaries: in an Odoo multi-company database, products and contacts are shared across companies by default, while quotations, invoices and bills stay with the company that issued them.

Segments: NetSuite lets a transaction line carry a class, a department and a location at once, and Odoo 19 does the same by giving each analytic plan its own column in the analytic distribution. Analytic distribution models prefill the split from the account, partner or product, replacing most of NetSuite's segment defaulting.

Locations: in NetSuite a location both holds stock and acts as a reporting segment. Odoo keeps those apart, so a store may become a warehouse and an analytic account, while a sales region that never held stock becomes only an analytic account.

Valuation: Odoo 19 sets perpetual or periodic valuation and the costing method, Standard Price, FIFO or AVCO, in the Accounting settings, with overrides on product categories. Match them to NetSuite before any product is imported, and agree a replacement with your accountant for any item costed by a method Odoo does not offer.

What data to move, and what to archive

Move what the business needs to operate the morning after cutover, and nothing that exists only to be looked at.

  • Master data. Chart of accounts, analytic accounts, product categories and products, contacts, payment terms, taxes, fiscal positions and bills of materials.
  • Open receivables and payables. Unpaid customer invoices, credit notes, vendor bills and refunds, each carrying only the amount still due.
  • Open orders. Sales and purchase orders not yet fully delivered, received or billed, brought across at their remaining quantities.
  • Stock on hand. Quantities by location, lot and serial number, at costs that tie to NetSuite's inventory valuation.
  • Opening balances. The trial balance at the cutover date, posted as one opening entry.

Full transaction history is the exception. You can import years of NetSuite journals, invoices and orders, but every document type has to be mapped and every imported period reconciled, and after go-live that history is rarely opened. The real argument for importing it is comparatives: finance wants this year against last year inside Odoo. A middle path is to post prior-period totals as summary entries by account and month. It complicates the opening balance, so decide it during mapping.

The rest goes to an archive, and with NetSuite that needs planning, because you cannot count on keeping a subscription system running read-only the way you can one you host yourself. The options are exporting the full history to files or a database you control, keeping the reports auditors ask for (period-end statements, general ledger detail, tax filings), or negotiating read-only access for a defined period. Many companies combine the first two and keep the archive as long as their auditors and tax rules require.

Export the history before the term ends. Schedule the full export well ahead of your renewal date, check it against NetSuite's own reports, and store it somewhere you control.

Getting data out of NetSuite

Saved searches do most of the work: build one per record type, include internal IDs, and export the results to CSV or Excel. Standard reports such as the trial balance and the aged receivables and payables export the same way, and they become your validation figures. For large volumes, developers can pull data through NetSuite's web services instead.

Two habits help. Export IDs, not only names, so each Odoo record can carry its NetSuite ID as an external ID. Odoo's import tool uses it to link invoices to customers and to update records rather than duplicate them when a load is rerun. And freeze the export definitions early, because the same searches run at every rehearsal and again on cutover day.

Audit, Map, Migrate, Validate

We use the same four phases as on every platform move. We have not published a NetSuite case study yet. The closest example of the Validate step is our SF Dyes migration from Odoo 13 to 18, where every historical record was verified against the source database before custom work began.

Audit covers the NetSuite account: subsidiaries, segments, item types, the saved searches people actually use, every workflow, script, SuiteApp and integration, and the quality of the data itself. The output is a written blueprint and a fixed-scope plan, and this is when we can give you dates.

Map turns the concept table into Odoo configuration and import templates in a staging database. Odoo's own guidance is to practice the process in a test database first, and we recommend rehearsing the full load at least twice.

Migrate loads data in dependency order: accounts and currencies, analytic plans, product categories and products, contacts, then the opening entries. Following Odoo's documented method, opening receivables and payables pass through clearing accounts, so the trial balance and the open invoices do not count the same money twice.

Validate proves the result against NetSuite figures taken at the cutover date:

  1. The Odoo trial balance matches NetSuite's, account by account, for every company.
  2. Open invoices minus credit notes equal the receivable balance, and the Aged Receivable report matches NetSuite customer by customer.
  3. Open bills minus refunds equal the payable balance, with the same test on the Aged Payable report.
  4. Quantity times cost across all products equals the inventory account balance, and both match NetSuite's valuation.

These mirror the checks Odoo's documentation sets for opening entries. Then your users run end-to-end scenarios by role, and every discrepancy is closed before sign-off.

Rebuilding SuiteScript and workflows

SuiteScript does not migrate. It is JavaScript written for NetSuite's platform, and none of it runs on Odoo. Porting it line by line into Python carries over workarounds for limits Odoo does not have, and skips the question of whether the logic is still needed.

Instead, each script and SuiteFlow workflow is re-specified in plain language: what triggers it, what it changes, who relies on it. Then it is sorted. Some requirements are covered by standard Odoo. Some become an automation rule that updates a field or creates an activity. The rest become custom Python modules: logic that ran on save moves into the model, scheduled scripts become scheduled actions, and custom endpoints become controllers. How much Odoo customization is too much explains where we draw those lines.

Custom modules run on Odoo.sh or on your own servers, not on Odoo Online, and both options sit under Odoo's Custom plan, which a multi-company database needs anyway.

Integrations that have to be repointed

Every system that talks to NetSuite has to talk to Odoo on cutover day, or be retired: eCommerce storefronts, payment providers, bank feeds, shipping carriers, EDI, third-party logistics, payroll, an outside CRM and BI tools. For each one, record what it moves, in which direction, how often, and who owns it.

Some disappear because Odoo covers the job natively. Some have a ready connector. The rest are rebuilt against Odoo's external API, which is also part of the Custom plan. Build new ones on Odoo 19's JSON-2 API, since the older XML-RPC and JSON-RPC endpoints are scheduled for removal in Odoo 22 (fall 2028), and earlier on Odoo Online, in version 21.1 (winter 2027). Test each at production-like volumes during the rehearsals. Our customization and integration team handles this work.

Parallel run or cold cutover

A parallel run keeps NetSuite live beside Odoo, so transactions are entered twice and compared. It catches errors early, at the cost of double entry and another stretch of NetSuite subscription. A cold cutover makes NetSuite read-only at a set moment and moves everyone at once. It is less work, and depends on the rehearsals above.

For most operations-heavy businesses we recommend a cold cutover after full rehearsals, with the team on hand through hypercare. A parallel run earns its cost when an auditor or regulator expects it, or when you expect issues to surface only in live use. Our post on migrating from a legacy ERP to Odoo goes deeper on that choice, the pre-go-live checklist lists what we confirm first, and our guide to adoption after go-live covers what follows.

Our Odoo upgrade and migration services cover NetSuite migrations end to end, and Odoo implementation covers the configuration around them, at a fixed price agreed before kickoff.

Frequently asked questions

How long does a NetSuite to Odoo migration take?

There is no standard figure. Subsidiaries, SuiteScript, integrations and how much history you bring across set the timeline, so we give dates after the audit, not before.

Can we bring our full NetSuite transaction history into Odoo?

You can, but it is rarely worth it, because every document type has to be mapped and every imported period reconciled. We recommend opening balances plus open items, with the history archived outside Odoo. If finance needs comparatives, prior-period totals can be posted as summary entries by account and month.

Will our SuiteScript customizations carry over to Odoo?

No. SuiteScript is JavaScript written for NetSuite's platform, and none of it runs on Odoo. Each script is re-specified as a requirement, then covered by standard Odoo, set up as an automation rule, or written as a custom Python module hosted on Odoo.sh or your own servers.

Does Odoo handle multiple subsidiaries like NetSuite OneWorld?

Each subsidiary becomes a company in one multi-company database, with inter-company transactions and consolidation through account mapping in Odoo 19. Consolidation is where NetSuite is strongest, so if eliminations are central to your close, test them against your own figures before you commit.

Octagotech Team

Certified Odoo Ready partner · San Francisco, New York, Ahmedabad and Rajkot

Our New York team plans platform migrations, our Ahmedabad engineers build the import scripts and custom modules, and our Rajkot desk supports you after go-live. About Octagotech, Odoo Ready partner.

Plan your move off NetSuite before the renewal date

The first call takes 30 minutes.

Or email sales@octagotech.com