ERPNext to Odoo migration, step by step

Bring your ERPNext customers, suppliers, products, stock, orders, invoices and ledger into a new Odoo 20 instance. ERPNext is only read, never changed.

Updated . 6 min read

You can move out of ERPNext yourself, from your dashboard, in a few minutes. We create a new Odoo 20 instance for you as a free trial, copy your ERPNext data into it section by section, and then count everything again on both sides and show you the result.

Nothing in ERPNext is changed. We only ever read from it: we list and read your records, and never create, edit or delete anything there. You keep working in ERPNext the whole time, and you decide later whether to go live on Odoo.

Before you start

  • Your ERPNext has to be reachable from the internet, at its own address. We connect to it the way your browser does, over HTTPS unless you type <em>http://</em> yourself - and you should not, because your password travels with the request. An ERPNext that only runs on your laptop or inside your office network cannot be read from here, and the wizard will say so rather than hang.
  • An ERPNext login that can read your data. We sign in with a username and password, exactly as a person would. The simplest choice is an account with the System Manager role; if you would rather not use your own, make a user for the migration and remove it afterwards.
  • An account here. The migrated instance is a free trial, like any new instance, so you do not need to pay anything to try this.
  • Nothing to install, and no export file to prepare. We read ERPNext through its own REST API while the migration runs.

Step 1: Start a new project

In your dashboard, click New Project and choose Migrate from another system.

The Start a new project dialog, with the Migrate from another system card

Step 2: Choose ERPNext

Pick ERPNext as the system you are moving from. The wizard has five steps, and the sidebar keeps track of where you are; you can go back at any point before you start the migration.

Step 1 of the wizard: choosing ERPNext as the system to migrate from

Step 3: Choose what to bring over

There are fourteen kinds of data, and they all start selected. Leave them as they are unless you have a reason not to.

Step 2 of the wizard: the fourteen kinds of ERPNext data, with full history pills

Nine of them are the core of your business, the things the rest of your records refer to:

  • Company & Chart of Accounts
  • Customers & Suppliers
  • Products & Pricing
  • Warehouses & Stock
  • Sales & Purchase Orders
  • Invoices & Payments
  • Journal Entries
  • Users
  • Attachments

The other five are marked full history, which means they also bring your past records rather than only what is needed to start working:

  • CRM
  • Projects & Tasks
  • Employees
  • Bills of Materials
  • Point of Sale

Anything another item depends on is brought over automatically, so you cannot end up with invoices whose customer is missing.

If your ERPNext does not have one of these apps installed - no HR, say, or no manufacturing - clear that section before you continue, rather than leaving it selected with nothing behind it.

Step 4: Connect to ERPNext

Enter your ERPNext address and the login to read it with, then click Test connection. You cannot continue until that test passes, which is deliberate: it is better to find a wrong address or a missing permission here than half way through a migration.

Step 3 of the wizard: the ERPNext address, username and password, with Test connection

The test signs in, then reads one record of each kind you asked for. That means it catches the two things that usually go wrong:

  • A wrong address or an ERPNext we cannot reach. The message names the host so you can check it.
  • A login that cannot read something you selected. The message names the record type, so you know exactly what to give the account read access to, or which section to clear.

Your ERPNext login is kept encrypted, used only to read your data, and erased as soon as the migration finishes. It is never written to a log and never shown again in your dashboard.

Step 5: Name the new instance and start

Give the new instance a name, which becomes its web address, and set the email and password you will sign in to Odoo with. The last step shows a summary; click Start the migration and you can leave the page. Until you click it nothing has been created in Odoo and nothing has been copied out of ERPNext - the connection test read a single record of each kind, and no more.

How long it takes

A few minutes in all. Creating the Odoo instance takes a couple of minutes, and copying a small company's data usually takes less than that again. A larger one takes longer, and the progress page tells you what is happening either way: one line per kind of data, with how many records were created, skipped or failed. You can close the page and come back to it; the migration keeps running.

The finished migration, with every section ticked and its record counts

The verification checks are the part to read

When the data is in, we count it again, on both sides. The verification table compares your old system with the new Odoo: customers and suppliers against partners, items against products, warehouses, what the stock quantities add up to, how many orders, invoices and payments there are, and what the ledger adds up to.

Verification: 29 of 29 checks match, with the comparison table

"Verification · 29/29 checks match" means every one of those comparisons agreed. If a check does not match, it is listed with both numbers, so you can see exactly what differs rather than discovering it in three months. We never post an adjustment to make a total agree.

A few differences are normal and not errors. Odoo gives your invoices its own numbers and keeps the ERPNext name in the document's reference field. ERPNext's accounts are created alongside the ones a new Odoo starts with, so your chart of accounts may be a little longer than it was.

If something goes wrong

A migration that fails can be retried from where it stopped: the sections that already finished are kept, so a retry picks up at the one that failed rather than starting again. It tells you why it failed in plain words. If you would rather start over, Cancel and remove deletes the half-finished instance and everything in it.

In every one of those cases your ERPNext is untouched, because we only ever read from it.

If you are stuck, or a check does not match and you cannot see why, contact us with the name of the instance and we will look at the run with you.

What this does not cover yet

We would rather tell you the limits than have you find them:

  • The migration creates a new Odoo 20 instance. It does not merge your ERPNext data into an Odoo you already use.
  • It copies your records, not your customisations. Custom doctypes, custom fields, scripts, print formats and workflows you built in ERPNext do not come across.
  • Of your ERPNext logins, only enabled staff accounts become Odoo users. ERPNext's own Administrator and Guest do not, and portal logins do not either - those people are already coming over as customers and suppliers, and migrating them twice would give them a second, unconnected account.
  • Passwords never come across, by design: ERPNext's password hashes cannot be read by Odoo, and reusing one password across two systems would be a risk worth avoiding anyway. Each migrated user gets a random password nobody sees, so set each person a new one from Settings > Users after go-live, as you would for a new employee.

Migrating from Sage Accounting works the same way, from the same place in your dashboard - there is a guide for that too.

Rather not run the server yourself?

Get managed Odoo hosting with backups, SSL, monitoring and updates handled for you. Free for 10 days.