Odoo rescue, for a project that has stalled or a partner who has gone quiet.
Go-live keeps slipping, tickets go unanswered, or the people who built your system have moved on and nobody can explain it. The first job in a rescue is to make sure you hold your own data, code and access. The second is an honest look at what you have. Everything after that is your decision.
Or call us: +1 515-644-1400, any time. Rescue and rehost price. How to start.
Allodi is run by Mark Kladivo in Des Moines, Iowa; his manufacturing company, Corn Belt Aluminum, is making the same move Allodi sells, to Odoo 19 Community on Hetzner with Backblaze backups. Read the case study.
Signs an Odoo project needs rescuing
None of these means Odoo was the wrong choice. They mean the system has lost its owner, and someone needs to take it back.
The relationship
- Support requests take weeks, or get no answer at all.
- The go-live date has moved more than once, and each new estimate comes with a change order.
- The partner holds the server, the code repository and the passwords, and nobody at your company has an administrator login.
- An upgrade was quoted at close to the price of the original implementation.
The system
- Custom modules nobody on either side can explain.
- Backups that have never been restored, or no backups you can reach.
- Bank statements that fail to import, or receivables that do not match the bank.
- Staff keeping spreadsheets alongside Odoo because they do not trust what it shows.
What we do first
The order matters more than people expect. Nothing here changes your production system.
-
Secure what you own before anything else
A full backup with the filestore, an administrator login, the custom code, and control of your domain and DNS. These are ordinary requests, and you can make them before any conversation about the future. Our partner handover checklist lists everything, in the order to ask.
-
The free scan before you sign
A read-only scan counts your companies, users, modules, Enterprise apps and customizations, and checks your version. It changes nothing. You get a plain-English report and a quote with project fees that are binding for what the scan counts, from the published prices. See a sample report.
-
A copy on a server in your name week 1 to 2 after signing
Your company opens a Hetzner Cloud project and a Backblaze account and gives us access to both. We restore a neutralized copy of your database there, with mail, scheduled actions and payment providers switched off, and confirm every module loads. If we cannot get your database running on the new server, the start milestone is refunded (conditions).
-
A written migration plan within 10 business days of access
An inventory of what is installed and connected, including modules, custom code, integrations and scheduled actions, and the plan for moving it to your server. Anything that needs more than the move, such as a fix, a cleanup or an upgrade, is quoted separately, so you can decide with your own people, and with your current partner if you want to.
-
Cutover and handover cutover two to six weeks from signing
After a parallel run in which your team checks its own work, production moves on an evening you choose. Within 30 days of cutover you receive the handover: the runbook, the integrations sheet, the credentials list, a backup test report and the repository. Managed Odoo keeps it running from cutover if you want it.
Where a rescue fits, and where it does not
A good fit
- Odoo is live, or your data is already loaded, and the system needs an owner.
- The partner is gone, slow, or too expensive, and you want the server, code and backups in your own name.
- The customizations have grown past what anyone understands, and you want a smaller system you can keep.
- Odoo 16 and later, Community or Enterprise, on Odoo.sh, a partner's server or your own (an older version is upgraded first). On Odoo Online, a major version (such as 18.0 or 19.0), not an intermediate one.
Better served elsewhere
- A project that has not yet decided how the business should run in Odoo, and needs process design, training and change management across departments. A full-service implementation partner fits better, and we are glad to suggest one.
- Anyone looking for a promise about the outcome before the system has been seen. The scan and the copy come first, and any further work is quoted after them.
What a rescue costs
Every number is on the pricing page, and each one comes from something you can count in your own Odoo.
Rescue and rehost
- $750 per database, billed as $250 at signing, at cutover and at handover
- $125 for each additional company in the database, billed at cutover
- Start milestone refunded if we cannot get your database running on the new server
If the system needs more
- Customization cleanup from $750 for 1 to 50 customizations
- Upgrade from the published module, version and Enterprise app prices
- Other work at $150 an hour, quoted before it starts
After cutover
- Managed Odoo, $75 a month for one company plus $15 per internal user, month to month
- Server and backups billed to you directly by Hetzner and Backblaze
- Or run it yourself from the runbook
If the partner holds your system
Odoo's own agreements allow for changing partners. The Enterprise Subscription Agreement (version 13 of September 24, 2026) says the customer "can decide at any time to work with a different Odoo Partner, or to work with Odoo SA directly (subject to prior notice)" (section 2), with 30 days' written notice to Odoo S.A. before changing the main contact (section 6.1). Your contract with the partner may add its own terms, so read it too.
What makes a change hard is when the partner holds the code, the server or the passwords. Our switching Odoo partners page sets out what to collect and in what order, so the conversation about leaving is a conversation, not a negotiation.
Leaving a hosted platform at the same time
A rescue often includes a move: off Odoo.sh, off Odoo Online, or off the partner's server. The migration page lists what does not travel with the database, such as mail, payment webhooks and single sign-on, and the version limit on leaving Odoo Online.
We move first and upgrade later, never both at once, so that when something differs, everyone knows which change caused it.
Questions people ask
Can you take over a half-finished Odoo implementation?
Often, yes, when the system exists: a database with your data in it, even if go-live has slipped. We restore a copy on a server in your name, see what works, and give you a written plan for the move. A project that still needs its processes designed across several departments is better served by a full-service implementation partner, and we say so when we see it.
Do we have to leave our partner first?
No. Collect a full backup, the code and your admin access first, as ordinary requests. You can decide about the partner after you have seen the copy running and the plan. Our switching partners page has the order that keeps it friendly.
What if we have no access to the custom code?
Custom modules are files on the server, not part of the database, so a database backup alone does not include them. Ask the partner for the repository or a copy of the modules, or for server access. Changes made with Studio are part of the database itself and travel with the backup.
How long does a rescue take?
Usually two to six weeks from signing to cutover, depending on size, most of it a parallel run where your team checks its own work on the new server. Handover follows within 30 days of cutover. A partner who is slow to release assets stretches the first step.
Is the price fixed?
The rescue itself is $750 per database plus $125 for each additional company in it, billed in three milestones. Cleanup and upgrade work are priced from the published tables, and the project fees in the free scan's quote are binding for what the scan counts.
Can you promise the rescue will work?
Nobody can honestly promise that before seeing the system. What we commit to in writing: if we cannot get your database running on the new server, the start milestone is refunded, unless the cause is on your side or a third party refuses to release your data, and every step before production happens on a copy.
Will you fix our accounting?
Fixing the Odoo side, such as bank statement imports that fail, reconciliation tools that do not work, reports that are wrong or settings that were never finished, is quoted as separate work after the rescue. The reconciling itself stays with your team or your accountant.
Tell us where your Odoo project stands
The free scan shows what is installed and customized, and you can run it today. If you would rather talk first, tell us your version, where it runs, who holds the code and what is not working. We usually reply within one business day with the first questions to ask.
- Plans, add-ons and hourly rates are published; larger projects are quoted up front, and the project fees in the free scan's quote are binding for what the scan counts.
- On a move, the start milestone is refunded if your database cannot run on the new server, unless the cause is on your side or a third party refuses to release your data (conditions).
- Managed Odoo is month to month: thirty days' notice, no minimum term.
- Your server, code, backups and credentials are in your company's name.
Or call us: +1 515-644-1400, any time. How to start.