Odoo rescue · Success Pack, partner or self-implemented
Odoo implementation rescue in Australia
An Odoo implementation that has stalled, slipped or gone live without being trusted can usually be recovered on the licence you already pay for. We start with a fixed-fee Rescue Assessment from $1,200 that audits configuration, data, custom code and the gap to how your business runs, then give you three costed paths: stabilise, rebuild in place, or change hosting or platform. Most Australian rescues take the second path.
This is the Odoo-specific side of our ERP implementation rescue service.
At a glance
- Who it is for
- Australian businesses on Odoo Enterprise or Community whose implementation was delivered by an Odoo Success Pack, a partner they have lost confidence in, or their own team, and is late, over budget or live but not trusted
- Problem it solves
- Nobody can tell you whether the project is salvageable, what it will cost to finish, or whether the platform was the wrong call
- Platforms
- Odoo 15 to 20, Enterprise and Community, on Odoo Online, Odoo.sh or self-hosted
- Typical cost
- Rescue Assessment fixed fee from $1,200 ex GST; rescue phases scoped from the findings against our published implementation bands (Essentials $25,000 to $50,000, Growth $50,000 to $120,000)
- Typical timeline
- Assessment in 1 to 2 weeks; stabilisation measured in weeks; a rebuild in place typically 6 to 16 weeks depending on scope
- Last verified
- 22 October 2026 against the Odoo partner directory, the Odoo Partnership Agreement and the Odoo Success Pack and hosting documentation (links in the body)
The market
Why do so many Odoo implementations need rescuing in Australia?
The ecosystem grew faster than the experience in it. Odoo's own about page counts 21,000+ partners worldwide as at 22 October 2026, while the official partner directory lists 4,505 partners with public visibility. The gap is Learning partners, which the Odoo Partnership Agreement (version 11, 19 May 2023) describes as "without visibility as an official partner until they get the required experience". The Australian directory shows 38 official partners: 1 Gold, 11 Silver and 26 Ready as at 22 October 2026. Ready is the entry level: 10 net new Odoo Enterprise users sold in a year and one certified employee, with no retention requirement. Silver requires 75 users, three certified staff and 70% retention; Gold 300, six and 80%. Two in three visible Australian partners are at the entry tier. That is not a criticism of any firm; it is the shape of a market that doubled its demand before it trained its consultants.
Odoo's own Success Packs are a second route in, and they are built for a different job. A pack is a block of consultant hours, from 4 hours at A$915 to 200 hours at A$37,000 for returning customers, with 15% off a new customer's first pack as shown to Australian visitors on 22 October 2026, delivered "over the telephone or online" with onsite time billed on top. The page states that "Extra monthly charges apply for the maintenance of extra modules / lines of code" and that performance work "require[s] a success pack of minimum 50 hours". Hours-based remote delivery works for a clean standard setup. It runs out on a business with Australian GST coding to get right, legacy data to clean and a warehouse that does not match the demo.
The third route is hosting chosen before scope was understood. Odoo's documentation says Odoo Online is "incompatible with custom modules or modules from the Odoo Apps Store" and supports only "customizations that do not require custom code". A business that signs up on Online and then discovers it needs an Apps Store connector or a custom module has two choices: rebuild the requirement in Studio, or move to Odoo.sh by downloading a backup and importing it. Many stalled projects are stuck exactly here.
Capterra found that fewer than one in three Australian businesses successfully adopt new software (Capterra, 281 Australian decision-makers, October 2025). Odoo is not special in failing; it is special in how recoverable it is, because the licence, the data and the source code stay yours.
The signs
What does a failed Odoo implementation look like?
- Go-live has slipped more than twice and the next date has no plan behind it.
- The business runs two systems. Odoo is live, the old accounting file or spreadsheets still carry the truth, and month end takes longer than before.
- The Success Pack hours ran out with modules installed but not configured for Australia: tax codes half mapped, the Business Activity Statement (BAS) report never reconciled, bank feeds never connected.
- Studio changes nobody can explain, or custom modules with no repository and no author still contactable.
- Stuck on an old version because custom modules block the upgrade: Odoo's docs say a database with custom modules "cannot be upgraded until a version of your custom modules is available for the target version" (upgrade documentation).
- Integrations that re-key. The Shopify, Xero or 3PL connection was "working" at handover and is now a daily CSV.
- No internal owner. The person who championed the project has left, or never had the hours.
Health check
Is your Odoo project salvageable? A 3-minute health check
Twelve questions, scored as you go. You get a verdict, the path we would most likely recommend and an indicative budget band from our published pricing, before you give us any contact details. If you want the written triage notes, add your email at the end.
The paths
The three Odoo rescue paths
Path 1
Stabilise
Reconcile the ledger, fix tax codes and the BAS report, repair permissions, reconnect bank feeds, get stock counted and corrected. Weeks, not months. The business can trust the numbers while the bigger decisions get made.
Path 2
Rebuild in place
The most common outcome. Keep the Odoo subscription and the data, strip the Studio and custom-code workarounds that fight the standard flows, reconfigure against how the business actually runs, migrate clean master data, retrain by role. Where a custom module blocks an upgrade, we rewrite or retire it so the free Enterprise upgrade service works again. Broken connectors go through our Odoo integration services; stranded versions through our Odoo upgrade services.
Path 3
Change hosting or platform
If the requirement needs custom code and the database is on Odoo Online, the fix is a move to Odoo.sh or self-hosting, which Odoo documents as a backup download and import. If the platform itself does not fit, we implement both Odoo and MYOB Acumatica and will say so; see Odoo vs MYOB Acumatica.
Changing partner
What transfers when you change Odoo partner?
- The subscription is yours. Odoo bills the customer, not the partner. Changing partner does not change your licence or your data.
- The database is yours. On Odoo Online you can download a backup from the database manager; on Odoo.sh the project is linked to a GitHub repository you authorise; self-hosted, you hold it already.
- Enterprise source code and support are not partner-gated. Enterprise subscribers can access the Enterprise code from Odoo's download page and GitHub Enterprise repository (source install docs), contact Odoo support directly, and use the upgrade service free. A partner adds capacity and accountability, not exclusive access.
- What we ask the outgoing party for. Admin credentials, the custom code repository or module zips, Studio export, any functional documentation, the data import files and the list of open tickets. Where we cannot get them, the assessment includes recovering them from the live database.
- No blame. We do not bill hours litigating what happened. The assessment states facts; you decide what to do with them.
Cost
What does an Odoo rescue cost?
Rescue Assessment: fixed fee from $1,200 ex GST, 1 to 2 weeks, written diagnosis and three costed paths, yours to use with us or anyone else.
Rescue phases: scoped from the findings and approved one at a time against our Odoo implementation cost in Australia bands. A rebuild in place for a 10 to 30 user business usually lands inside the Essentials band ($25,000 to $50,000); 30 to 100 users inside Growth ($50,000 to $120,000). Stabilise-only work is less. Figures ex GST, Odoo licences billed separately by Odoo. We do this work as an Odoo partner in Brisbane, working Australia-wide.
| Delivery route | How it usually fails | What the rescue does first |
|---|---|---|
| Odoo Success Pack (remote hours) | Hours run out before Australian tax, data and warehouse setup are finished; onsite time billed separately | Finish the configuration against a written scope; reconcile the BAS; connect bank feeds |
| Entry-tier partner | Scope agreed from a demo; Studio and custom code used where standard flows existed; no staging | Audit the customisations; retire what fights the standard; set up staging before anything else changes |
| Self-implemented | Nobody owned the data migration or the cut-over plan; two systems running | Stabilise the ledger; plan a dated cut-over; name an internal owner |
| Any route on Odoo Online needing custom code | Requirement cannot be met without a module; project stalls | Decide: rebuild in Studio, or move to Odoo.sh via backup and import |
FAQ
Odoo implementation rescue: common questions
Can a failed Odoo implementation be saved?
Usually, yes. In most Odoo rescues we take on, the platform is capable and the configuration, data or delivery model is what failed. A fixed-fee assessment separates the salvageable from the mismatched before any more money moves, and the licence, data and source code stay yours throughout.
Our Odoo Success Pack hours ran out and the system is not finished. What now?
Get a written list of what is configured, what is not, and what was built in Studio. A partner can pick up from there without restarting; the Success Pack work is not wasted, it is just incomplete. Our assessment produces that list and prices the remaining work in phases.
Can we change Odoo partner mid-project?
Yes. The subscription and database belong to you, not the partner. You download or export the database, hand over credentials and any code repository, and the new partner audits before touching anything. Odoo support, the upgrade service and Enterprise source access are available to every Enterprise subscriber regardless of partner.
We are on Odoo Online and need a custom module. Is the project dead?
No. Odoo Online does not run custom modules or Apps Store modules, so you either rebuild the requirement with Studio or move the database to Odoo.sh or self-hosting, which Odoo documents as a backup download and import. The assessment tells you which is cheaper for your case.
How much does an Odoo rescue cost in Australia?
The assessment is a fixed fee from $1,200 ex GST. Rescue work after that is scoped in phases against our published implementation bands: rebuilds for 10 to 30 user businesses usually land inside $25,000 to $50,000, larger sites inside $50,000 to $120,000, and stabilise-only work costs less.
Do you work with Odoo Community as well as Enterprise?
Yes. Community rescues are common where a business self-implemented to avoid licence fees and then hit the limits of what it could build itself. See our Odoo Community support page for how we work on Community sites.
Further reading
Three posts behind this page
- Odoo implementation failed? The seven Odoo-specific reasons Australian projects stall and how a rescue works
Josh Craig
- How to change Odoo partner mid-project in Australia: what transfers, what it costs and the takeover checklist
Bill Alvarez
- Odoo Success Packs vs partner implementation: what Australian businesses are actually buying
Bill Alvarez
Odoo project off the rails?
Talk to us before the next steering meeting. We rescue Odoo implementations for Australian businesses from Brisbane, starting with a fixed-fee assessment that tells you where the project really stands. Bring the war stories; we will not bill for listening to them.