Move from Odoo to ERPNext, variants and customers included

Why Marta stopped exporting spreadsheets

Meet Marta, who runs a knitwear shop like many we talk to. Her catalogue, sweaters in several sizes and colours, beanies and totes, and her wholesale customers such as Emma Schmidt in Berlin, lived in Odoo.

Her accountant works in ERPNext, so the shop is moving there. The hard part was the data: an export flattens the Merino Crew Sweater into separate rows, splits addresses from customers, and drops the tags her team uses.

This guide follows that move with StoreCopy. Every screenshot is from one real run, from opening the wizard to finding the sweater in ERPNext as an Item template with its Size and Color variants, and Emma with her address and phone.

Sign in at StoreCopy and open the wizard. It starts on Platforms with Select Source Platform.

Under Select Source Platform, click Odoo. The list changes to Select Destination Platform: click ERPNext.

Each side now has its own connect form, Odoo first.

Under Connect Your Odoo Store, type the address you open Odoo at, for example https://mycompany.odoo.com, and click Continue to Odoo.

Odoo shows Connect StoreCopy: which database StoreCopy asks to read and write, and as which user. Click Allow. Odoo creates an API key named StoreCopy migration for your user and sends you back to the wizard with Odoo connected.

TipOdoo → ERPNext also needs the CRM app in Odoo. If it is missing, the wizard says so after connecting: install it under Apps and press Check again.

In ERPNext, open your avatar, My Settings, API Access, and click Generate Keys. Copy the API key and the API secret, which ERPNext shows only once.

Back in the wizard, under Connect Your ERPNext Store, enter the Site URL, API key and API secret, then click Connect ERPNext. Fill in Company only if the site has several companies.

TipGenerate the keys for a user with the Item Manager, Stock Manager, Sales Manager, Sales Master Manager and Accounts User roles, so StoreCopy can create items, customers and orders.

Click Continue, then Estimate Full Migration. StoreCopy counts what your Odoo database holds: collections, customers, products, discounts, quotes, orders and the CRM records.

The table shows each count next to its free quota, and the price of the full migration in the totals row. Nothing is charged at this step.

Click Continue and Start Demo Migration. Up to 20 records of each type are created in ERPNext. Orders wait for the full migration, because an order can only be archived, not deleted.

Each bar fills as its records are created. When Demo Migration completed successfully! appears, open ERPNext and look.

Open Stock, Item: every Odoo product is an Item, with its Odoo SKU as the item code, such as HSR-P10. A product with options is an Item Template with one Variant per combination.

Open a template, here Merino Crew Sweater: Has Variants is on, and the Variants tab lists its Size and Color attributes. Its Odoo tags came over too.

Open Selling, Customer, here Emma Schmidt: under Address & Contact are her Berlin address, phone and email, and the activity shows StoreCopy created them.

TipOpen a few demo items and customers and compare them with Odoo. That is where a migration shows its quality.

Happy with the demo? Click Continue to the Production step. The full migration copies everything else, orders included, and skips what the demo already created.

Want to start over? Go Back to the demo step and click Rollback Demo Migration. StoreCopy deletes only the records the demo created; what was in ERPNext before stays.

What moves from Odoo to ERPNext

Each Odoo record becomes its ERPNext counterpart, linked to the others. Products are created before the orders that sell them, and customers before their addresses and orders.