Skip to Content

Case File #02: Vendor Lock-In in Odoo, or ERP Stockholm Syndrome

Two locks. Zero easy exits. One uncomfortable diagnosis.

That Reddit thread got heated fast. I said the biggest Odoo trap was vendor lock-in. The automatic response came quick:


"Odoo is Open Source. You own your data. You can leave anytime."

Technically true. But in the operating room, things look different. There are two real locks. And neither one is psychological.


Lock #1: Odoo S.A. (The Company)


Open source doesn't save you here.


  • Per-user licensing: Once you have 50, 100, or 300 employees using Odoo Enterprise, the annual cost becomes a massive fixed expense. Want to negotiate? Good luck. Odoo sets the price. You pay or you leave.
  • Odoo.sh (Hosting): Migrating a database from Odoo.sh to your own server or another provider is a technical nightmare. Not impossible, but it requires a team that knows what they're doing. Most mid-sized companies don't have one.
  • Forced upgrades: Odoo releases a new version every year. Old versions lose support. You are forced to upgrade. Each upgrade costs money, time, and patches for broken customizations.


Bottom line: You came in because it was affordable. Now you're tied to the ecosystem. Switching ERPs costs more than paying that annual license forever.


Lock #2: The Partner and Captive Localization


This one is quieter and more dangerous.


It happens in regions where Odoo has no official, complete localization (read: Latin America, certain fiscal aspects in Spain, and a long etcetera).


Each partner builds their own fiscal/accounting localization.


  • Electronic invoicing.
  • Tax books.
  • Local withholdings.
  • Specific government reports.


What the partner installed for you is not standard Odoo. It's the partner's proprietary code.


What happens when you want to switch partners?


  1. The outgoing partner forces you to uninstall their modules (they're within their rights if the contract doesn't say otherwise).
  2. The incoming partner installs their own.
  3. Result: Total reconfiguration. Manual historical data migration. Risk of losing already-issued electronic invoices. Weeks of extra work. An unexpected invoice.


And if the contract with the first partner didn't clearly state that the localization modules would remain your property (or at least have a perpetual usage license), you are trapped.


That's hard lock-in. Not a lack of leadership. A poorly read contract and real technical dependency.


The Unmistakable Sign You're Locked In


"To switch partners, we'd have to redo all the accounting from January."
"Odoo just raised license prices by 20% and we can't do a thing about it."


If you've said or heard something like that, the diagnosis is clear.


The lock exists. It's not an internet myth.


How to Break It (Or At Least Know What You're Getting Into)


Not all hope is lost, but it requires preventive "surgery":


  • Localization audit (It applies to each and every custom module): Before signing, ask: Are these fiscal modules standard Odoo or your own development? What happens if we end the relationship? 
  • Escape clause in the contract: Demand that modules critical for fiscal operation come with a perpetual usage license for your company, even if you switch partners.
  • Evaluate On-Premise: If volume justifies it, run from Odoo.sh and host on your own servers with a trusted internal or external technical team.


You can't eliminate lock-in completely. But you can reduce it to a manageable level.


A Final Note on the "Syndrome"


They say Stockholm Syndrome is when the hostage starts defending the captor.


In the ERP world, it sounds a little different:


"Honestly, it's not that bad. The annual increase was only 15% this time."
"Sure, we can't leave without breaking everything, but the partner really understands our business now."


If that sounds familiar, the diagnosis is confirmed. Treatment is available. The first step is admitting the lock exists.


Has your company felt the pull of the double lock yet? Or are you already sending holiday cards to your captor?


Note: To Natalia Duque, my first successful treatment for Vendor Lock-In :)


Case File #01: The Parallel Excel Syndrome
Why your ERP implementation is technically "perfect" but practically invisible.