Odoo audit: how to rescue a project that has stalled

An Odoo audit is an independent review of a system that already exists, whether it is live, half-deployed or abandoned. Its purpose is simple: establish what you actually have, what is wrong with it, and what it would take to make it work. If your project has stalled, the audit is usually the first step towards an Odoo project rescue, and the evidence you need before deciding whether to stay with your current integrator.

Nothing here assumes the technology is at fault. Odoo is a broad, modular ERP, and most problems we see described in troubled projects come from scoping, data, over-customisation or a breakdown in the working relationship. An audit separates those causes so you do not pay twice for the same mistake.

Signs that an Odoo audit is overdue

You do not need a disaster to justify a review. Several quieter symptoms point the same way:

• Go-live keeps moving. The date has slipped more than once and nobody can explain what remains.
• Users work around the system. Spreadsheets reappear next to Odoo, and the finance team re-keys figures to trust them.
• Every change is a project. Small requests take weeks, or the integrator quotes a development for something that sounds like configuration.
• The system is slow. Screens hang during stock moves, invoicing runs or month-end.
• Reports disagree. Sales, stock and the ledger tell different stories, and your accountant no longer trusts the output.
• Nobody can say how it works. The knowledge sits with one consultant, and there is no usable documentation.
• The version is falling behind. The upgrade has been postponed repeatedly because nobody dares touch it.

If three or more of these sound familiar, an audit will pay for itself. If the cause is a broken relationship rather than broken software, the audit is also the neutral document that lets you move on without recrimination.

What an Odoo audit examines

A proper audit is structured, not a general impression. It should cover the following areas, and the report should say plainly where evidence was thin.

Configuration and business fit

The auditor compares how Odoo is set up with how the company actually trades. Are the apps in use the ones you need, and are they used consistently? Are approval flows, price lists, warehouse locations and fiscal settings in line with your operations? A frequent finding is an application installed with default settings that no one adapted, or a process bent to fit a module when a small configuration change would have sufficed. For a view of what each area normally involves, see the Odoo modules overview.

Data quality

Data is where many rescues are won or lost. The audit looks at duplicates in customers and suppliers, product and unit-of-measure structures, opening balances, stock valuations and the way historic data was imported. Poor data cannot be fixed by good code, and it quietly undermines every report. If the migration itself was weak, the Odoo migration guide explains what a sound transfer looks like.

Custom developments

Every custom module is a liability as well as an asset. The review checks what has been built, whether it duplicates standard features, how it is tested, and whether it will survive the next version. The auditor should read the code or at least sample it, check for hard-coded values, and judge how tightly it is tied to Odoo internals. Our page on Odoo customisation sets out when development is justified and when it is not.

Performance

Slowness has several possible causes: an undersized server, heavy scheduled actions, badly written custom code, an oversized database or too many unnecessary integrations. The audit should measure rather than guess, identifying the screens and processes that hurt, then tracing each to its cause.

Security and access

The auditor checks user rights, the separation of duties between ordering, receiving and paying, administrator accounts left open after the project, backup arrangements and where the data is hosted. Because the UK has strict expectations on personal data, you should also confirm who has access to employee and customer records and under what terms. Hosting choices are covered in Odoo hosting and cloud.

Version, licence and upgrade path

Odoo Community 19 is released under the LGPLv3 licence, while Odoo 19 Enterprise is under the Odoo Enterprise Edition licence, which can be used only with a valid Enterprise subscription for the right number of users. An audit therefore also checks that your licensing matches what is installed, since an unnoticed mismatch becomes a commercial problem later.

Version matters for support too. Each major version receives three years of standard support after release, and security fixes are provided only during that period. Extended support is paid for and is available only on Odoo.sh and on-premise installations. According to Odoo's supported-versions page, version 17.0 reaches the end of standard support in September 2026, so a company still running it needs a plan now. On Odoo Online and Odoo.sh, upgrading to a major version is mandatory every two years. See Odoo versions and editions for how to read the calendar.

What the audit report should contain

Insist on a written deliverable, not a presentation alone. A useful report holds:

Be wary of any report that simply recommends a rebuild without showing evidence. Equally, be wary of one that reassures without having touched the data.

Changing Odoo integrator without starting again

Changing Odoo integrator is less drastic than it sounds, because Odoo is not locked to one supplier. The database, the code and the configuration belong to you in principle, though your contract decides the details. The aim is continuity: the business keeps trading while responsibility moves.

Documents and access to secure first

Before you give notice or open a difficult conversation, gather what you can control and request what you cannot:

• Administrator access to the Odoo instance, the hosting account and the domain, held by someone in your own company.
• A recent full backup of the database and filestore, stored outside the integrator's environment.
• The source code repository with all custom modules, and read access to the branch history.
• The signed scope and specification documents, change requests and any acceptance reports.
• Configuration documentation: chart of accounts, tax set-up, price lists, warehouse structure, roles and approval flows.
• Integration details for payment providers, banks, couriers, e-commerce and HMRC-related connections, including credentials ownership.
• Subscription and licence records showing who is registered as the contracting party with Odoo.
• The contract and its termination terms, including notice, handover obligations and intellectual property clauses.

Check your Making Tax Digital and payroll connections in particular. If VAT submissions or RTI payroll filings run through a connector the integrator controls, make sure the credentials and agent authorisations are transferred, or your accountant may find filing blocked at the worst moment. The guides on Making Tax Digital and ERP and payroll and RTI explain what needs to stay connected.

A sensible handover sequence

1. Freeze the scope. Agree with the outgoing integrator what is in progress and stop new development while the audit runs.
2. Commission the audit from the incoming firm. Ask them to review the system before they quote for the rescue, so their price rests on evidence.
3. Agree a transition period. Ideally the old and new integrator overlap briefly, with documented questions and answers.
4. Move hosting and repository ownership to accounts you control.
5. Restart with a short, visible win. Fix the most painful issue first so the team sees progress.

Where the relationship is already tense, keep communication factual and in writing. A professional integrator will not resist a reasonable handover, and a solicitor can review the contract if there is a dispute about code or fees.

A redress plan for a troubled Odoo project

The audit gives you options; the plan turns the chosen one into work. A workable redress plan has a recognisable shape.

Stabilise

Stop the bleeding before improving anything. Take reliable backups, close open administrator accounts, apply any pending security fixes and make sure the system is on a supported version. Put the most critical process, often invoicing, stock or payroll, on a safe footing.

Reset the scope

Go back to what the business needs. Use the findings to separate must-haves from preferences, and retire customisations that duplicate standard features. A shorter, honest scope is easier to deliver than a long list nobody believes. Our ERP requirements template helps rebuild that list quickly.

Repair the data and configuration

Correct master data, reconcile opening balances and stock, and align configuration with reality. This is often the stage that restores confidence among finance users, because the numbers begin to agree again.

Train and hand over

Many failed projects were never badly built, only badly adopted. People received a short demonstration and were left alone. Plan role-based training and keep a living procedures document. The page on Odoo training covers formats to consider.

Put support on a proper footing

A recovered system needs an owner afterwards. Agree who handles incidents, who plans upgrades and how change requests are approved. See Odoo support and maintenance for what a support agreement should include.

Repair, rework or rebuild?

The audit should lead to one of three decisions, and it helps to know what each means in practice.

Do not treat a rebuild as a reset button. Without better governance, clearer scope and a named internal owner, the same pattern tends to return. The reasons projects fail are catalogued in common ERP project mistakes.

Choosing who carries out the rescue

A rescue calls for different strengths from a first implementation: diagnostic discipline, willingness to say what is wrong, and respect for work already done. When assessing candidates, ask how they would audit before quoting, whether they have taken over projects before, and how they handle another firm's code. Odoo's UK partner directory lets you filter by sector and company size, and shows project success rates, sizes of typical projects, references and numbers of certified experts per version, which gives you something to check rather than a sales pitch. Our guides to choosing an Odoo partner and choosing an ERP integrator go through the questions to ask.

ERP Integrator is not affiliated with Odoo and does not carry out projects ourselves. We introduce your business to an integrator suited to the situation, at no cost to you, so you can discuss an audit or a takeover with a firm that has relevant experience in your sector and region. How the introduction works is explained in a few steps, and our page on Odoo in the UK covers local considerations such as VAT, Making Tax Digital and payroll.

Before you start the conversation

Prepare a short brief so the audit is focused from the first day: what you expected from Odoo, what has gone wrong, which processes are critical, who inside the company can take decisions, and what you have already spent in time and effort. Avoid blaming language. An auditor needs facts, and your own team's account of how they use the system is often the most valuable evidence of all.

An audit does not commit you to anything. It gives you a clear view of the system, a reasoned option and a plan you can hold any integrator to, which is exactly what a stalled project lacks.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.