It is time to switch when the same problems keep coming back after you have raised them in writing: missed deadlines, slow or no replies, undocumented custom code, and every fix billed as new work. Give your partner one dated recovery plan first. If they miss it, secure your database, hosting and code access, then move.
What are the warning signs that your partner is the problem?
Every project has bad weeks. A pattern is different. Look for these:
- Silence. Tickets and emails go days without a reply, or only get answered when you escalate.
- Repeat bugs. The same issue is “fixed” more than once and comes back.
- No documentation. Nobody can explain what the custom modules do, and only one developer understands them.
- Everything is a change request. Defects in work you already paid for are billed as new scope.
- Locked access. The partner controls your hosting, code repository or admin login and is slow to share it.
- No plan for upgrades. You are on an old Odoo version and nobody has told you what it will take to move.
Should you fix the relationship or switch?
| Situation | Try to fix first | Time to switch |
|---|---|---|
| Missed deadlines | One-off, with a clear reason | Repeated, with no new plan |
| Communication | Slow but honest | Silent or defensive |
| Code quality | Bugs get fixed and stay fixed | Same bugs return; no documentation |
| Billing | Scope disputes discussed openly | Every defect billed as new work |
| Access | Shared on request | Refused or delayed |
Before deciding, send your partner one written recovery plan: the open issues, the dates you need them fixed by and who is responsible. If they meet it, you may not need to switch. If they miss it, you have your answer and a clear record.
What access do you need before you tell them you are leaving?
Secure these first. Losing access mid-handover is the biggest risk in a switch.
- Database administrator login for your Odoo database, under an email your company controls.
- Hosting access. On Odoo Online, ownership of the database can be transferred through a support ticket. On Odoo.sh, make sure your company has an Admin role on the project. On your own server, get root access, the Odoo master password and database credentials.
- Source code of every custom module, ideally in a repository owned by your company.
- Recent backups you have downloaded and checked yourself.
- Documentation: what was customised, why, and any integrations with other systems.
How does the switch work in practice?
- Audit. The new partner reviews your configuration, custom modules, data quality and open issues.
- Prioritise. Decide what to keep, what to fix and what to retire. Not every custom module is worth carrying forward.
- Agree the subscription side. Speak to your Odoo account manager about moving the account to your new partner, and check the notice terms in your current agreement.
- Stabilise first. Fix the issues blocking daily operations before starting new features or an upgrade.
- Hand over in writing. Close the old contract with a list of what was delivered and confirmation of who owns the code.
Get your operations back on track
Tenxora takes over Odoo projects that have stalled: we audit what your previous partner left, secure your access and code, and get your teams working reliably again before anything new is built. If your current project keeps slipping, a short call will tell you whether to fix it or move.
FAQ
Will switching partners mean starting my Odoo project again?
Usually not. A new partner should audit what exists, keep the configuration and modules that work, and fix or replace the rest. A full restart is only needed when the setup is so broken or undocumented that repairing it costs more than rebuilding.
Can I move my Odoo Enterprise subscription to a new partner?
The subscription is normally between your company and Odoo, even when a partner sold it, so you can usually work with a different partner. How existing users and renewals are handled is agreed with Odoo, so involve your Odoo account manager and check the notice terms in your current agreement.
Do I own the custom modules my old partner built?
It depends on your contract and the module licence. Some partners assign the code to you, others keep the rights and license it. Read the contract, ask for the full source code, and get a written IP assignment if the contract is silent.
Related service: Odoo Consulting
Sources: Odoo documentation: Odoo Online database management, Odoo forum: taking over an existing customer as a partner, iVentureTeam: Changing Odoo partners mid-project
