WordPress to Odoo migration, a case study.

Roughly every six months, a business owner writes to us for the same reason: “my WordPress site can't cope any more, I want to switch”. It keeps getting slower, plugins clash with each other, maintenance bills creep up, and the team no longer dares to change anything for fear of breaking it all. This article tells the story of one of those projects, with the real figures before and after the migration to Odoo. No marketing spin: these are measurements from the field.

Why our clients migrate.

When a business owner decides to leave WordPress for Odoo, it's almost never for a technical reason. It's about mental load. WordPress becomes that thing you no longer dare to touch, that you pay for without understanding why, and that crashes on a Tuesday morning just before an important meeting. At some point, that invisible cost outweighs the initial convenience.

Odoo usually enters the picture because the business already uses it for accounting, sales or CRM. And it realises that its website could simply live in the same environment, without that constant friction between back office and front office. That promise is what wins us most of our redesign projects.

Before: a five-year-old WordPress site.

The project in question: a Belgian food SME with an online shop of 80 products, multilingual FR/NL, around 3,500 unique visitors a month. The site had been built in 2020 on WordPress with a theme bought on ThemeForest, WooCommerce for the shop, WPML for languages, Yoast SEO for meta data and Elementor for editorial pages. A classic setup, with little heavy customisation at the start.

Five years later, this is how things really stood:

The main pain point wasn't the slowness itself (the client had got used to it), but the unpredictability. Every plugin update could break a page. Every new product had to be entered twice (in the Odoo back office and in WordPress). Stock reports fell out of sync every fortnight on average.

The technical pivot.

Our approach to a WordPress to Odoo migration rests on three simple principles. We apply them to every migration project, regardless of the size of the original site.

• We don't carry over the existing design. We use the opportunity to rebuild the front end completely, by hand, in the Odoo website module. Porting a WordPress theme to Odoo makes no sense: it's not the same technology. Rebuilding it properly costs the same as adapting it.
• We keep the product database. We export the products, categories, images and reviews from WooCommerce and import them into Odoo. No manual re-entry. URLs are redirected with 301s to preserve SEO.
• We migrate in parallel and switch over in one night. The WordPress site keeps running throughout the 6 to 10 weeks of the project. At switchover, we change the DNS on a Saturday evening. On Monday morning, the client wakes up to the new site. No visible downtime.

After, 18 months later.

Here are the figures I can share, measured 18 months after the new site went live and compared with the same period on WordPress.

The gain in organic traffic comes from a combination of factors: Core Web Vitals turning green (Google takes them into account), clean semantic HTML, JSON-LD schemas tailored to each page type, and native multilingual support without broken hreflang. Over 18 months, these effects add up to far more than one-off optimisations on the WordPress site would have delivered.

Official benchmark: Google considers a page good with an LCP under 2.5 seconds, an INP under 200 milliseconds and a CLS under 0.1, measured at the 75^th percentile of page loads. Source: Google, Core Web Vitals, accessed in August 2026.

The conversion gain is more subtle. No A/B test isolated the exact cause, but mobile speed (LCP dropping from 3.8s to 1.3s) probably plays the main role. When a product page loads in under 2 seconds, visitors stay. When it takes 5 seconds, they leave.

We paid for a redesign once. We've been recouping it every month since, without even noticing.

WebNest client · food e-commerce project

What surprises clients.

Three things come up almost every time in the feedback, and prospects don't anticipate them before switching:

• The end of the mental noise. No more plugin update emails. No more security notifications. No more Sunday evening panics. It's a comfort you only appreciate once you have it.
• A single back office. Stock, invoices, customers, website, newsletter: everything is in Odoo. A new colleague needs just one training session. There's one logic to learn and one screen to check in the morning.
• Adding a language becomes easy. Odoo's native multilingual support is a game changer. Activating a language takes 10 minutes, compared with 3 days of WPML configuration. For Belgian SMEs working across FR/NL/EN, it makes a world of difference.

Who it's not for.

Let's be realistic. Migrating from WordPress to Odoo doesn't make sense for everyone. If you're in one of these situations, stay on WordPress: it will be cheaper.

• A pure blog with no ERP. If your site is purely editorial, with no product management or online sales, WordPress remains excellent.
• A tight redesign budget. If the scope you have in mind is very limited, the return on investment from Odoo is less obvious than a simple update of your existing WordPress site.
• You're not an Odoo customer and don't intend to become one. Adopting Odoo just for the website is overkill. The value comes when you already use the ERP suite.

If you tick at least two of the following boxes (you sell online, you manage stock, you work in several languages, your WordPress maintenance has become a cost that weighs on you every month, you use Odoo in your back office or plan to), then a migration is probably the right move.