Migrating from Winbooks to Odoo in Luxembourg

In short. Leaving Winbooks for Odoo in Luxembourg is not converting one file into another: it is a data migration. Your partners, your chart of accounts, your trial balance, your VAT history and your fixed assets live inside Winbooks in its own logic of the "file" per company; you have to extract them, map them onto Odoo's model and re-anchor them on the PCN 2020, without breaking the audit trail or the ability to produce a FAIA. The real risk is not technical, it is accounting. And the switch is judged at the first closing that follows, not on import day.

Winbooks (now part of the Exact group) is one of the most widespread accounting programs on both sides of the Belgian-Luxembourg border. Many SMEs know it because their accounting firm keeps their books in it; others use it directly for their bookkeeping and invoicing. It is a proven accounting tool. It is not an integrated management tool. When the idea of moving to Odoo comes up, the question is not "is it better?" but "how do I move house without losing my accounts?". This article answers that one, for a Luxembourg setting.

What Winbooks is, and why people leave it

Winbooks is a Belgian accounting and management program built around the notion of the file: one file per company, which is what made it a standard among accounting firms handling dozens of clients. It comes as an installed version (Winbooks Classic) and an online version (Winbooks on Web / Winbooks Connect), with commercial-management and document-handling blocks around the accounting core. On its home turf, keeping the books, it does the job.

The reasons for leaving almost always come through the same doors. Winbooks accounting does not natively talk to the CRM, stock, point of sale or an e-commerce site: whatever happens upstream of the invoice gets re-keyed. A growing company ends up with an accounting program on one side, a sales-tracking spreadsheet on the other, a third tool for quotes, and fragile bridges between the three. Odoo appeals precisely where Winbooks stops: a single base where sales, purchasing, stock and accounting share the same data. If you are still comparing the categories of tools, our analysis Odoo, SAP or Sage: which ERP to choose? sets the frame.

A data migration, not a conversion: the distinction that costs money

There is no "Winbooks to Odoo" button. The two programs do not organise information the same way, and nobody converts one into the other in a single click. What you run is a migration: you extract the data from Winbooks, clean it, line it up against Odoo's model, then import it. It is a specific case of the move to Odoo we describe in general in migrating to Odoo in Luxembourg; here, we zoom in on what is specific to leaving Winbooks. The logic is the same as leaving Sage BOB 50, with its own exports and its own traps.

The "data migration" line is the one most underestimated in a quote. A clean import from well-structured files has nothing to do with a migration that requires de-duplicating partners, re-sorting accounts and rebuilding a history. Have it priced separately, explicitly, rather than buried inside an implementation package.

What comes out of Winbooks, and where it lands in Odoo

Concretely, a Winbooks file holds several blocks of data, rarely all handled the same way. Here is how they transpose.

The target setup itself is the same as for any Luxembourg accounting in Odoo: a chart anchored on the PCN 2020, rates and fiscal positions, regulatory exports. We detail it in setting up Luxembourg accounting in Odoo. A successful migration is that setup applied to data that already exists.

The method, in four steps

Migrating from Winbooks follows an order, and the order matters. You do not rush the import: you prepare the data first.

1. Extract and map. You pull the partners, the chart of accounts, the trial balance, the journals, the open items and, where relevant, the products out of Winbooks. Every source field finds its place in Odoo, or you knowingly decide not to bring it over.
2. Clean. This is the step wrongly skipped. A duplicate partner, an account unused for ten years, an inconsistent label: migrating dirty data means importing the mess into a fresh tool. You clean at the source, not afterwards.
3. Import and check in a sandbox. You load into a test environment, block by block, and reconcile the totals: general balance, customer and supplier receivables and payables, VAT balances. A one-euro gap is chased before the switch, not after.
4. Switch and reconcile. You stop Winbooks at a clean cut-off date, often a period end. You bring the opening balances into Odoo, and you check that the starting balance sheet matches the last statement produced from Winbooks.

One structuring decision comes back every time: bring over the whole history, or only the opening balances and open items? Bringing everything reassures but costs more and imports old debris. Often, restarting from the balances on the switch date, keeping Winbooks read-only for reference, is the best compromise. It is decided file by file.

The Luxembourg angle: PCN 2020, VAT and FAIA

A technically successful migration can be an accounting failure. Three compliance points are at stake with every departure from Winbooks in Luxembourg.

The chart of accounts first. Your accounts must land on the right structure of the PCN 2020, the standard chart of accounts in force since January 2020. A Belgian file kept in Winbooks often starts from a Belgian chart: it is not copied across as-is, it is re-anchored, account by account, on the Luxembourg standardised headings. A bad mapping, and hundreds of entries end up on the wrong accounts, to be re-sorted at closing.

The VAT history next. The Luxembourg rates and, above all, the fiscal positions (intra-EU, reverse charge) must be brought over correctly, otherwise your next eCDF returns come out wrong. You check the migrated VAT balances before validating anything.

The FAIA last. The Registration Duties, Estates and VAT Authority (AED) can request the computerised audit file. It has to return a coherent history, including the period kept under Winbooks. Two routes: either you bring the history into Odoo keeping continuity, or you keep Winbooks read-only for prior years. Either way, you must remain able to produce a clean FAIA on request. We cover this in our guide to setting up Luxembourg accounting in Odoo.

The common case: you are leaving the firm that keeps your books in Winbooks

Many companies do not use Winbooks themselves: it is their accounting firm that keeps the file in it. If you bring your accounting in-house on Odoo, or if you change providers, the migration runs through a sensitive point: getting your data back from the firm. You are entitled to your documents and a statement of your accounts; ask, in writing, for the detailed general balance, the general ledger, the partner list, the fixed-asset schedule and the current year's VAT returns. Those are the statements that feed the migration into Odoo, whatever the source program.

Conversely, if you are yourself an accounting firm using Winbooks as a production tool across a portfolio of files, the reasoning changes. Odoo handles a portfolio well in multi-company mode, one company per file, each anchored on the PCN 2020. But Odoo is a management ERP, not a specialised accounting-production program: it is less equipped than Winbooks on certain review functions and fast batch entry. A firm that migrates therefore has to decide what it really wants from the tool. We develop that trade-off in Odoo for accounting firms in Luxembourg.

Who this migration is not (yet) for

Let us be blunt. If Winbooks covers exactly your need, if you are not after a CRM, e-commerce or integration between your sales and your accounts, and your team knows it inside out, changing tools for the sake of it makes no sense. Odoo earns its place when you want to unify several functions that are scattered today, not when you replace a good accounting program with another at equal scope. And a firm heavily dependent on high-cadence batch entry should check, before deciding, that the input comfort it expects really exists in Odoo. The right time to migrate is when the cost of working around Winbooks outweighs the comfort of staying.

Frequently asked questions

Can Winbooks be converted automatically into Odoo?

No. There is no automatic conversion between the two: they do not organise data the same way. You run a migration, meaning an extraction from Winbooks, a clean-up, a mapping onto Odoo's model, then a controlled import into a test environment before the switch.

Will I lose my accounting history by leaving Winbooks?

Not if the migration is prepared. You decide whether to bring the whole history into Odoo or only the opening balances and open items, keeping Winbooks read-only for prior years. Either way, the aim is to remain able to produce a coherent FAIA.

My Winbooks file is Belgian: how does it move to the Luxembourg chart of accounts?

The chart of accounts is re-anchored on the PCN 2020, the Luxembourg standardised chart. Each Winbooks account is attached to the right standardised heading in Odoo. It is a mapping job to do account by account, which determines how accurate your statements are after the switch.

How do I get my data back if it is my accounting firm that keeps the Winbooks file?

You ask the firm, in writing, for the statements that feed the migration: the detailed general balance, the general ledger, the partner list, the fixed-asset schedule and the current year's VAT returns. Those documents, not the Winbooks file itself, are what rebuild your accounts in Odoo.

How long does a migration from Winbooks take?

From a few days for a clean file brought over on opening balances, to several weeks for a full history migration with clean-up and de-duplication. The timeline depends mostly on the quality and volume of the source data, not on the tool.

Read more

• Migrating to Odoo in Luxembourg: switch tools without losing your accounts
• Migrating from Sage BOB 50 to Odoo in Luxembourg
• Setting up Luxembourg accounting in Odoo: PCN, FAIA and eCDF
• Odoo for accounting firms in Luxembourg: managing client files
• How much does an Odoo implementation cost in Luxembourg?

Why Advena?

• Finance and digital under one roof: the accounting migration (PCN 2020, VAT, FAIA) is handled inside the project, not pushed back onto your accounting firm.
• Compliance tested before the switch: VAT balances, receivables and the FAIA export validated on your real data, not after the fact.
• Clear fixed fees, no hourly billing: the data migration is priced separately, explicitly.
• Direct access to the founders: the partners run your migration, not a junior.

Information current as of 7 September 2026. Winbooks and Exact are trademarks of their respective owners. This article describes a migration method and does not constitute individual accounting or tax advice.