Migrating from Sage BOB 50 to Odoo in Luxembourg

In short. Leaving Sage BOB 50 for Odoo in Luxembourg is not an automatic conversion: it is a data migration project. Your accounting, your partners, your VAT history and your fixed assets live inside BOB 50 in its own logic; they have to be extracted, mapped onto the Odoo model and realigned with the PCN 2020 chart of accounts, without breaking the audit trail or your ability to produce a FAIA. The real risk is not technical, it is accounting. And the switch is judged at the first year-end that follows, not on import day.

Sage BOB 50 (often written "BOB50") runs a large part of the SMEs and accounting firms across Luxembourg and Belgium. It is a solid accounting and business-management package, but many companies eventually find it too tight: installed locally, licensed per seat, walled off from the CRM, stock, point of sale and e-invoicing. When moving to Odoo comes up, the question is no longer "is it better?" but "how do I move house without losing my accounts?". This article answers that one, for a Luxembourg setting.

What BOB 50 is, and why firms leave it

Sage BOB 50 is an accounting and business-management package of Belgian origin, published by Sage, with a strong footprint on both sides of the border. Its "Expert" edition targets accounting firms that run dozens of client files; its management edition serves SMEs that invoice and track their purchases. It is a good accounting tool. It is not an integrated management tool.

The reasons for leaving it come back through the same doors. The software sits on a local workstation or server, with the backup and remote-access constraints that implies. Its accounting does not talk to the CRM, to e-commerce or to a point of sale, which forces re-keying. E-invoicing and the Peppol network, now unavoidable in Luxembourg, call for add-ons. And per-seat licensing gets expensive as the team grows. Odoo appeals precisely where BOB 50 stops: a single base where sales, purchasing, stock and accounting share the same data. If you are still weighing the two categories of tool, our analysis Odoo, SAP or Sage: which ERP to choose? sets the frame.

Data migration, not conversion: the distinction that costs money

There is no "BOB 50 to Odoo" button. The two packages do not organise information the same way, and nobody converts one into the other in a click. What you run is a migration: BOB 50 data is extracted, cleaned, mapped against the Odoo model, then imported. It is a special 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 BOB 50.

The "data migration" line is the one most often 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 history. Have it priced separately, explicitly, rather than buried inside an implementation package.

What comes out of BOB 50, and where it lands in Odoo

In practice, a BOB 50 file holds several blocks of data, and they are rarely all migrated the same way. Here is how they transpose.

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

The method, in four steps

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

1. Extract and map. Export the partners, chart of accounts, trial balance, journals, open items and, where relevant, the products from BOB 50. Each source field finds its place in Odoo, or you knowingly decide not to migrate it.
2. Clean. This is the step wrongly skipped. A duplicated partner, an account unused for ten years, an inconsistent label: migrating dirty data means importing the mess into a new tool. Clean at source, not after.
3. Import and check in a sandbox. 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 hunted down before the switch.
4. Switch over and reconcile. Stop BOB 50 at a clean cut-off date, usually a period end. Carry the opening balances into Odoo, and check that the starting balance sheet matches the last statement produced by BOB 50.

One structural decision comes back every time: migrate the full history, or only the opening balances and open items? Migrating everything is reassuring but costly, and it imports old clutter. Often, starting from the balances at switch date, while keeping BOB 50 read-only for reference, is the best compromise. It is settled 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 every time you leave BOB 50.

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. The BOB 50 chart is not copied across as is: it is realigned, account by account, onto the standardised headings. A bad mapping, and hundreds of entries end up on the wrong accounts, to be re-sorted at year-end.

The VAT history next. The Luxembourg rates, and above all the fiscal positions (intra-EU, reverse charge), have to be migrated correctly, otherwise your next eCDF returns come out wrong. The migrated VAT balances are checked before anything is validated.

The FAIA last. The Registration Duties, Estates and VAT Authority (AED) can request the standard audit file. It must return a coherent history, including the period kept under BOB 50. Two routes: either migrate the history into Odoo while preserving continuity, or keep BOB 50 read-only for the earlier years. Either way, you must remain able to produce a clean FAIA on request.

The special case of the accounting firm

Many BOB 50 users are not SMEs but accounting firms that use it as a production tool across dozens of client files. For them, the reasoning shifts. Odoo handles a portfolio of clients well in multi-company mode, one company per file, each aligned with the PCN 2020 and its own exports. But Odoo is a management ERP, not a specialised accounting-production package: it is less equipped than BOB 50 Expert on certain review or statutory-accounts functions. A firm that migrates therefore has to decide what it really expects 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 plain. If BOB 50 covers exactly your need, you are after neither a CRM, nor e-commerce, nor integration, and your accounting team is perfectly at home in it, changing tools for the sake of it makes no sense. Odoo earns its place when you want to unify several functions that are today scattered, not when you replace one good accounting package with another at equal scope. And a firm heavily dependent on review and statutory-accounts tooling should check, before deciding, that the complementary tool exists. The right time to migrate is when the cost of working around BOB 50 outweighs the comfort of staying on it.

Frequently asked questions

Can BOB 50 be converted to Odoo automatically?

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 BOB 50, a cleaning pass, a mapping onto the Odoo model, then a controlled import into a test environment before the switch.

Will I lose my accounting history when leaving BOB 50?

Not if the migration is prepared. You decide whether to migrate the full history into Odoo or only the opening balances and open items, keeping BOB 50 read-only for the earlier years. Either way, the goal is to stay able to produce a coherent FAIA.

How does my BOB 50 chart of accounts transpose into Odoo?

It is realigned onto the PCN 2020, the Luxembourg standard chart of accounts. Each BOB 50 account is attached to the right standardised heading in Odoo. It is a mapping job to do account by account, and it determines whether your statements are correct after the switch.

What about my Luxembourg VAT after the migration?

You migrate not only the entries but also the rates and fiscal positions (intra-EU, reverse charge), then check the VAT balances before the switch. That check is what guarantees correct eCDF returns from the first period on Odoo.

How long does a migration from BOB 50 take?

From a few days for a clean file migrated on opening balances, to several weeks for a full-history migration with cleaning 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
• Setting up Luxembourg accounting in Odoo: PCN, FAIA and eCDF
• Odoo for accounting firms in Luxembourg: managing client files
• Odoo, SAP or Sage: which ERP for an SME in Luxembourg?
• 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 handed back to your accountant.
• Compliance tested before the switch: VAT balances, open items 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: it is the partners who lead your migration, not a junior.

Information current as of 1 September 2026. Sage BOB 50 is a trademark of Sage. This article describes a migration method and does not constitute individual accounting or tax advice.