Implementation · Partner handover

How to switch Odoo partners mid-project without losing work

Changing Odoo partners halfway through a project is survivable if you secure access, code and documents before you give notice. Here is what to collect for each hosting type, what to read in the contract, and how to keep the business running while the new team learns your system.

By Octagotech Team9 min readUpdated

Key takeaways

  • Check first whether the relationship can be fixed. A switch has its own cost.
  • Get admin access to the database and the hosting before you give notice.
  • Own the Git repository and every custom module's source, with its history.
  • Odoo lets you change the partner on your Enterprise subscription; check the notice the agreement requires.
  • The new partner should diagnose the system before it quotes a fixed price.

Businesses often wait too long to switch Odoo partners mid-project, because they are afraid of losing what has been built. The work is rarely lost. It sits in a database, a hosting account, a Git repository and a set of documents, and each can be secured. What goes wrong is the order: a company gives notice, then finds that the partner owns the hosting account, the code lives in the partner's GitHub organization, and the only copy of the scope is in someone's inbox.

This guide covers when a switch is the right call, what to secure before you say anything, the contract points to read, a handover checklist, and the new partner's first weeks. It is general guidance, not legal advice.

Switch, or fix the relationship first?

A switch has a cost. The new partner has to learn your system before it can change anything safely, and decisions that lived in the old team's heads have to be rebuilt from documents. So first ask whether the problem is the partner or the way the project is set up.

Fixing the relationship is usually cheaper when the partner is competent but the structure has failed. If scope has grown without change orders, approvals sit for weeks, or nobody at your company owns the project, a new partner inherits the same problem. A reset meeting that names one internal owner, freezes scope, and puts a dated plan and a weekly status report in writing can fix that without a handover.

A switch is the right call when the partner cannot or will not deliver: the people who knew your system have left, go-live has moved twice without a credible reason, custom code arrives that nobody can explain, or scope and price never get put in writing. So is being unable to get a straight answer about access to your own system. The warning signs on our Odoo rescue page are a useful test. One of them can be a bad week. Two or more usually means the plan has stopped working.

Secure access before you give notice

Do this while the relationship still works. Asking for admin access mid-project is a normal request; after notice it becomes a negotiation. What "access" means depends on where Odoo runs.

Odoo Online. Odoo hosts the database, and Odoo Online cannot run custom modules or apps from the Odoo Apps Store, so your customization is configuration and Studio work inside the database. You need two things: an administrator user in the database, and control of the database in Odoo's database manager at odoo.com/my/databases, where backups are downloaded, plans are switched and the database can be renamed or deleted. If the partner created the database under its own odoo.com account, ask Odoo to transfer ownership to your account. Then download a backup yourself.

Odoo.sh. Here there are three layers. The first is an administrator user in the database. The second is the Odoo.sh project, where collaborators are GitHub users with one of three roles. Roles limit what each collaborator can do, and only an Admin manages the project settings. Make sure someone at your company holds Admin. The third layer is the GitHub repository the project builds from. If it lives in the partner's GitHub organization, you do not control your own code, so plan with the new partner how it moves to one you own. Odoo.sh makes automatic backups of production, so your data is rarely at risk; what you are securing is the right to reach it, and a backup you have downloaded yourself.

On-premise. Access means the server itself: an SSH login, the hosting or cloud account in your company's name, the PostgreSQL database, the filestore where attachments live, and the Odoo configuration file, which holds the master password for the database manager. A zip backup from the database manager at /web/database/manager includes the filestore and needs that password. If the database manager has been disabled, you need someone who can take a PostgreSQL dump and copy the filestore. Find out where scheduled backups go and who pays for that storage.

Whatever the hosting, restore the backup somewhere and open it. A backup nobody has restored is a hope, not a backup.

Back up, restore, then give notice. If the relationship sours, a restored copy of the database and a full clone of the code mean the worst case is a delay, not a loss.

The Odoo subscription and the partner of record

Your Enterprise subscription is a contract with Odoo SA, and a partner can be attached to it. Under Odoo's Enterprise Subscription Agreement, you can work with a partner as your main point of contact for bug fixes, support and upgrade services, or work with Odoo directly, and you can decide to work with a different partner. Read the agreement for the written notice Odoo requires when you change your main point of contact.

In practice, find your subscription code and confirm the subscription is in your company's name, not the partner's. Check who invoices it, Odoo or the partner. Then write to Odoo, through your account manager if you have one, naming the new partner and the date. On-premise, the database is registered with the subscription code, so keep the code where the next partner can find it.

Code, Studio work and the paper trail

On Odoo.sh and on-premise, the source of every custom module is the most valuable thing the partner holds. Ask for the Git repository with its full history and every branch, not a zip of the current state. History shows why a change was made, and it is often the only documentation a module has. Then compare what is installed in the database with what is in the repository. Modules copied onto a server and never committed are exactly the ones nobody can explain later. List the marketplace apps too, with their versions and the account that bought them.

Studio customizations are different. They live in the database, not in the repository, so they move with the database and are not lost when the partner leaves. Odoo keeps them in a module called studio_customization, which can be exported from Studio as a ZIP for your records, and Odoo's upgrade service covers Studio customizations as long as Studio is still installed and the subscription is active. What gets lost is the reason behind each change, so ask for any notes.

Then the documents. The new partner will need whatever exists of these:

  • scope documents, the fit-gap analysis and the log of changes that were agreed
  • test scripts and acceptance-testing results, including the failed runs
  • the open ticket or bug list, with status and owner
  • data migration scripts, mapping files and the source extracts
  • credentials for every integration: payment providers, carriers, banks, EDI, e-commerce, email and DNS

Inventory the credentials, then rotate each one after the handover. Removing the old partner's Odoo users does not revoke keys they hold for your payment provider, carrier or bank.

Contract points to read before you give notice

Read the contract before the conversation. This is general guidance; have a lawyer who knows your jurisdiction read the actual terms.

Start with ownership of the custom code. Some contracts assign the code to you on payment; others leave ownership with the partner and grant you a license to use it. The license key in each module's manifest, such as LGPL-3 or OPL-1, states license terms; it is not evidence of who owns the code. If the contract is silent, ask for a written assignment as part of the exit.

Then the notice period and how termination works: whether you can end the engagement for convenience, what you owe for work in progress, and how a fixed-price milestone that is half done gets paid. Look for handover obligations, meaning documentation, knowledge-transfer sessions and the rate for them, and add them to the exit agreement if they are missing. And keep payment disputes separate from access. Withholding a payment to force a handover, or withholding access to force a payment, stalls both.

The handover checklist

Use this as the agenda for the exit meeting. Each item has a test for done, because "we sent it over" is not the same as "we have it and it works".

ItemWhy it mattersDone when
Database administratorYou can configure and fix the live systemYour own admin login works, not a shared one
Hosting controlOnline: database owner. Odoo.sh: Admin role. On-premise: server and cloud accountSomeone at your company holds it
Full backup with filestoreYour data, outside anyone else's controlRestored on a separate instance and opened
Git repositoryThe custom code and the reasons behind itIn an account you own, every branch, full history
Installed vs committed modulesCode copied onto a server outside GitEvery installed custom module is in the repository
Marketplace appsVersions and licenses for the next upgradeListed with version, vendor and buying account
Studio customizationsConfiguration that lives only in the databaseExported, with notes on why each change exists
Subscription and partner of recordSupport, upgrades and who Odoo talks toSubscription in your name, Odoo notified in writing
Scope, fit-gap and change logWhat was agreed and what was notFiled where the new partner can read it
Test scripts and resultsWhat has been proven to workLatest run received, failures included
Open ticketsKnown problems nobody should rediscoverExported with status and owner
Integration credentialsThe connections that keep orders and payments movingInventoried, then rotated after handover

What the new partner should do in the first weeks

A good new partner does not start by building. It starts with a diagnosis of the live system, the custom code, the data, the integrations and the way people use it, with the root cause named in writing. Our walkthrough of what the diagnostic audit checks covers that area by area.

Be wary of a fixed price quoted before anyone has read the code. It is either padded for unseen risk or renegotiated once the risk shows up. On our Odoo rescue engagements, the diagnosis comes before any quote, each module is sorted into keep, repair or rebuild, and the recovery is quoted at a fixed price wherever the scope can be pinned down. Where undocumented custom code makes that impossible, we say so and propose time and materials.

After the diagnosis comes stabilization: whatever stops daily work gets fixed first, then the dated repair plan starts. If the project was never scoped properly, our guide to preventing implementation failure explains the checkpoints the new plan should include.

Keep the business running during the switch

The riskiest weeks fall between the old partner stepping back and the new one knowing the system. Agree in writing who handles production problems on each date, so a failed invoice run never belongs to nobody. Freeze non-urgent changes to production until the new partner has reviewed the code, and route any urgent change through one named person on your side.

Avoid switching in the week of a month-end or year-end close, a peak season, or another module's go-live. When the backup, code and documents are confirmed, remove the old partner's user accounts, Odoo.sh roles and server keys, and rotate the credentials on your inventory. Then tell your users who to call. Support should come from a desk briefed on your system before its first ticket, which is how our Odoo support handoffs work.

Frequently asked questions

Can we change Odoo partners in the middle of an implementation?

Yes. Odoo's Enterprise Subscription Agreement lets you work with a different partner, or with Odoo directly. Check the agreement for the written notice Odoo requires, and give it before the change. Your contract with the current partner sets the notice period and handover terms on that side.

Who owns the custom code our previous partner wrote?

Your contract decides. Some contracts assign the code to you on payment, others only grant a license to use it, and where a contract is silent, the default rules where you operate apply, which may leave ownership with the partner. The license key in a module's manifest does not settle ownership. Either way, ask for a written assignment and have a lawyer review it.

Will we lose our Studio customizations if we switch partners?

No. Studio changes live in the database, so they move with it. They can also be exported from Studio as a module, and Odoo's upgrade service covers them as long as Studio stays installed and the subscription is active.

Should a new Odoo partner quote a fixed price right away?

Not before it has seen the system. A price given before anyone reads the code is guesswork. We quote a rescue after the diagnosis: a fixed price where the scope can be pinned down, time and materials where undocumented code makes that impossible.

Octagotech Team

Certified Odoo Ready partner · San Francisco, New York, Ahmedabad and Rajkot

Our New York project managers and Ahmedabad engineers take over Odoo projects that other partners started, beginning with a diagnosis of the live system before any quote. About Octagotech, Odoo Ready partner.

Changing Odoo partners? Plan the handover first.

The first call takes 30 minutes.

Or email sales@octagotech.com