How to Change Odoo Partner Mid-Project in Australia: What Transfers, What It Costs and the Takeover Checklist

You can change Odoo partner at any point in a project because the subscription, the database and the Enterprise source code belong to you, not to the partner. The takeover runs in three steps: collect credentials, backups and code; commission a fixed-fee assessment (from $1,200 ex GST with us) before anything changes; then approve rescue work in phases. Most Australian takeovers keep the existing subscription and hosting.

Switching partner mid-implementation feels like starting again. It is not, as long as you know what you own, what to collect and what a competent takeover looks like. This is the checklist we use when a business arrives with a half-finished Odoo site and a partner relationship that has run out, whether that partner was a local firm, an offshore team or an Odoo Success Pack consultant.

At a glance

• Who it is for: Australian businesses part-way through an Odoo implementation, or recently live, who have lost confidence in the partner delivering it or can no longer reach them
• Problem it solves: knowing what transfers, what to ask for before the relationship ends, and what a takeover costs, so the change does not become a second failed project
• 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; takeover phases scoped against our published Odoo implementation cost in Australia bands; Odoo licence fees unchanged
• Typical timeline: one to two weeks to collect access and complete the assessment; stabilisation in weeks; a rebuild in place typically 6 to 16 weeks
• Last verified: 22 October 2026 against Odoo’s Odoo Online, Odoo.sh, source install and upgrade documentation and the Partnership Agreement

Can you change Odoo partner in the middle of an implementation?

Yes. Nothing in Odoo’s model ties a customer to a partner. Odoo bills the subscription to the customer; the partner is a reseller and implementer, and the Partnership Agreement measures partners on net new users sold, certified staff and customer retention, not on any right over the customer’s system. Your contract with the partner governs what you owe them for work done; it does not govern whether you can leave.

The practical question is timing. The cleanest moment is at a phase boundary, after a deliverable has been accepted or rejected in writing. The second cleanest is now, if the alternative is another month of hours with no plan. What you want to avoid is leaving during a cut-over, with half the data in the new system and nobody accountable for the other half.

What belongs to you when you leave an Odoo partner?

More than most businesses realise. This is the part to read before the difficult conversation.

• The subscription. It is in your company’s name and billed to you. Changing partner does not change your licence, your user count or your renewal date. If the partner bought the subscription on your behalf, ask Odoo to confirm the account holder; that is a question for Odoo’s account team, not the partner.
• The database, wherever it is hosted. On Odoo Online, the database manager lets you download a backup, duplicate, rename or delete the database yourself. On Odoo.sh, the project is linked to a GitHub repository that you authorised when the project was created, and the deploy form takes your Enterprise subscription code. Self-hosted, you hold the server. If the partner created the Odoo.sh project under their own GitHub organisation, the repository transfer is the first item on the checklist below.
• The Enterprise source code. Enterprise subscribers can obtain the Enterprise edition from Odoo’s download page and the GitHub Enterprise repository (source install documentation). Partners get GitHub access for version-controlled development; they do not get exclusive access to anything you cannot obtain as a subscriber.
• Support and upgrades. Any Enterprise customer can contact Odoo support directly, and the upgrade service is free with Odoo Enterprise. A partner adds second-level escalation and someone who knows your configuration; it is not a gate.
• The custom code, usually. Check your contract. Most implementation agreements assign custom modules and Studio work to the client on payment; some retain partner ownership of reusable modules and licence them. Either way, the module code deployed on your database is needed to upgrade it, because Odoo will not upgrade a database “until a version of your custom modules is available for the target version”.

What should you collect from the outgoing partner?

Ask for everything below in one written request, before you tell them you are leaving if you can, and certainly before the final invoice is settled. Where an item cannot be produced, note it; the assessment will recover what it can from the live database.

How does a new Odoo partner take over without restarting?

A competent takeover does not start with a proposal. It starts with an audit. Ours is a fixed-fee Rescue Assessment, from $1,200 ex GST, that reads the configuration, the custom code, the data quality and the gap between what was built and how the business actually runs, then sets out three costed paths. That document is yours to act on with us or anyone else, which is also how you know the diagnosis is not shaped by what we would like to sell.

“The worst thing a new partner can do is rip out the previous partner’s work on day one. Half of it is usually fine. The job is to find out which half, on a staging copy, before anything touches production.” Bill Alvarez, Practice Manager, Auboros

The rules that stop a takeover becoming a second failure are the same ones on our ERP implementation rescue page. Scope in writing before work starts. Changes proven on a staging copy before production. Your team inside the project, because they run the system afterwards. And no hours spent litigating the previous partner, because it bills time and fixes nothing. Where the previous work was sound, we keep it and say so.

What does changing Odoo partner cost?

The assessment is fixed. After that, work is approved in phases against the same bands as a new implementation. A business of 10 to 30 users rebuilding in place usually lands inside our Essentials band of $25,000 to $50,000; 30 to 100 users inside Growth at $50,000 to $120,000; stabilise-only work costs less. The licence does not change. If the project also needs a hosting move, say from Odoo Online to Odoo.sh because a custom module is required, Odoo documents that as a backup download and import, and the Odoo.sh hosting fee is a new line on your Odoo bill, not ours.

Two costs people forget. First, any outstanding invoices from the outgoing partner for accepted work should be settled; disputes about unaccepted work are a separate matter and should not hold the handover hostage. Second, if the outgoing partner owns reusable modules under licence, the assessment prices a replacement so you are not dependent on them.

When the previous partner was Odoo itself

A growing share of takeovers come from Success Packs, which are hour-based blocks delivered remotely by Odoo consultants. The hours were spent in good faith; they ran out. The good news is that the handover is simpler: there is no third-party repository, the configuration is standard or Studio, and the data is on Odoo Online. The assessment starts from a written inventory of what was configured and what was not, and the Success Pack work is treated as a head start rather than a write-off. Our Success Packs vs partner implementation comparison explains why the model runs out where it does.

How do you pick the next partner so you do not do this twice?

Look past the badge. The Australian directory lists 38 official partners as at 22 October 2026, 26 of them at the entry Ready tier, which requires 10 net new users a year and one certified employee. Ask any candidate, including us, for the certified people by name, two Australian references at a similar size who went live in the last two years, their staging and scope-change rules, and what happens at the first major upgrade to anything they build. Our consultant vs certified partner post has the full question list, and our Odoo partner in Brisbane page shows how we answer them. The Odoo-specific failure patterns a takeover has to repair are on our Odoo implementation rescue in Australia page.

Goes well with

• Odoo Implementation Failed? The Seven Odoo-Specific Reasons Projects Stall if you are still deciding whether the project is the partner’s fault or the plan’s.
• Odoo Version Upgrades in Australia for what a takeover has to do about custom modules before the next version.
• Odoo Data Migration Checklist for Australian Businesses for the reconciliation the first partner may have skipped.

Thinking about changing Odoo partner?

We take over Odoo implementations for businesses across Brisbane, Queensland and the rest of Australia, starting with a fixed-fee assessment and a staging copy, never with a rip-and-replace. If you want a second opinion on where the project stands before you make the call, book a free consultation. Bring the contract and the ticket list; we will tell you what we would do first.