Who owns your Odoo database?
Not necessarily you. If an implementation partner created your Odoo subscription under their company account rather than yours, they are the account holder — and you are a user of a database somebody else controls. Businesses have discovered this the hard way: paid-up subscriptions where the client was, as far as they knew, the administrator, and where the partner was nonetheless able to delete the database or revoke access without consent.
It takes one question in writing to check, and it's much easier to ask before you sign than after.
What actually happens
Public reviews from late 2025 describe the same pattern more than once. Paraphrasing rather than quoting the individuals:
- A business pays for a full year of Odoo. The subscription is set up by their implementation partner.
- The database is created under the partner's Odoo account, not the client's company ID.
- The relationship breaks down — a dispute, an unpaid invoice, a decision to move on.
- The client loses access, or the database is deleted entirely. In at least one account, a business woke up to a fully paid subscription with its database and point-of-sale gone, with no prior notice.
The recurring detail is that the client believed they were the administrator. Being the admin user of a database is not the same as being the account holder of the subscription, and nothing in the day-to-day interface makes the difference visible.
To be clear about what this is and isn't. This is not most partners, and it usually isn't malice — it's often just how the partner set things up for convenience, with no thought about what happens later. The risk isn't a class of bad actors. It's a structural arrangement that's fine right up until the relationship isn't, at which point you have no leverage at all.
How to check, right now
If you're on Odoo Online or Odoo.sh: log into odoo.com and open your account. Confirm the subscription is under your company's name and that you can see billing details and the database list. If you can't find the subscription — or it isn't in your company's name — it isn't yours.
If you're self-hosted: you're mostly fine on the licensing side, but ask two more questions. Who has root on the server? Whose cloud account is it billed to? A database on a server you can't log into is the same problem in a different place.
Whatever your setup, ask these four in writing:
- Whose Odoo account is my subscription created under?
- Can I download a full database backup right now, without asking permission?
- If we part ways, what happens to the database and how quickly do I get it?
- Whose name is on the server or hosting account?
An honest provider answers all four in a paragraph. Vagueness on any of them is your answer.
Try downloading a backup today
The single best test costs ten minutes: go and take a full backup of your production database now.
Not because you expect a problem. Because attempting it tells you three things at once — whether you have the access, whether the process works, and whether anyone has to approve it. If you can't complete that on your own, you don't control your system, whatever the contract says.
Then check the backup restores. An untested backup is a hope, not a copy.
What good looks like
Reasonable arrangements share four properties:
The subscription is in your company's name. If a partner set it up, it's been transferred to you. If they resist transferring it, ask why, and listen carefully to the answer.
You can export without asking. Full database backup, on demand, no ticket, no notice period, no fee.
The exit is written down. What you get, in what format, how fast. "We'd obviously give you your data" is not a term.
The infrastructure is identifiable. You know which cloud account, which region, who holds credentials.
None of this is exotic. It's the same due diligence you'd apply to any system holding your customer list and your ledger — Odoo just gets skipped because it arrives bundled with an implementation project.
If it's already happened
Not legal advice, and if the data matters get a lawyer quickly — but practically:
- Ask Odoo directly. Odoo SA is the platform operator and may be able to help on ownership disputes, particularly where you can evidence payment.
- Gather evidence now. Invoices, contracts, emails, anything showing you paid and what was agreed.
- Find any backup you already hold. Old exports, accounting extracts, a stale test copy. Anything beats nothing.
- Check what's reconstructible elsewhere. Bank records, email, the e-commerce platform, supplier statements.
- Fix the ownership before rebuilding. Rebuilding into the same arrangement repeats the exposure.
Why this is structural, not accidental
The Odoo market is built around implementation partners, and the partner usually arrives before the system exists. Somebody has to create the subscription, and the fastest path is the partner's own account. It stays that way because there's no forcing moment to change it.
Add per-seat licensing, quote-per-change customisation and custom modules only that partner understands, and the arrangement has a lot of switching cost baked in — most of it unintentional, all of it real. Implementing Odoo without a partner covers which parts of that relationship you actually need, and what an Odoo implementation actually costs covers the money side.
Our answer, since we're a provider too
You should hold us to the same four questions.
The server and the data are yours. Not "we'd give them to you" — yours. Download the database whenever you want, no ticket, no notice, no exit fee. Go and take a backup during the trial; nothing is gated.
We run standard Odoo Community — unmodified, not a fork — so what you download is an ordinary Odoo database that restores anywhere. Modules made with our AI builder are ordinary readable Odoo code, so they come with you and keep working. There is nothing proprietary holding your system hostage.
$150/month for up to 25 people, $450/month unlimited, including backups, security patches, version upgrades and every module we've built.
If you leave, you leave with everything. That's the whole commitment, and it's short because it should be.
FAQ
Can my Odoo partner delete my database?
If the subscription was created under their Odoo account rather than yours, they hold the account and can act on it. There are documented cases of clients losing access to databases they had paid for in full.
How do I check who owns my Odoo subscription?
Log into odoo.com and confirm the subscription appears under your company's name with billing details visible. If you can't find it, or it's in someone else's name, it isn't yours.
Am I the owner if I'm the admin user?
No. Being the administrator of a database is different from being the account holder of the subscription. The interface doesn't distinguish them.
Can I transfer my Odoo subscription from a partner to my own account?
Generally yes — ask your partner to transfer it and contact Odoo if they won't. Reluctance is itself information.
What should I ask before signing with an Odoo partner?
Whose account the subscription will be under, whether you can download a full backup unassisted, what happens to the database if you part ways, and whose name is on the hosting.
Does self-hosting solve this?
Mostly, on the licensing side. But ask who has root on the server and whose cloud account it's billed to — a database on a server you can't reach is the same problem elsewhere.
How do I test whether I really control my system?
Take a full production backup today, without help, and confirm it restores. If you can't, you don't.
The rest of the cluster
Take a backup right now. See if you can.
Then ask your provider the four questions.