Skip to Content

Take over a stalled implementation

Odoo implementation stalled? We get it running again.

You're not the first, and you don't have to start over. We take over stalled Odoo implementations: first a 45-minute diagnosis, then a plan that sets out in black and white what stays, what can go and what it costs.

Free 45-minute diagnosisYou'll hear from us quicklyOdoo 10 to 19

Sound familiar?

Six signs that your Odoo no longer works for you

Most companies that call us don't have a software problem. They have a problem with choices that were made at some point and never reversed: too much customisation, too little documentation, and a team that has meanwhile come up with its own workarounds.

If you recognise two or more of the points alongside, a diagnosis is worthwhile. Whatever we build afterwards, we build using the same approach as for a new Odoo implementation — except this time we start by clearing up.

Consultant looking over someone's shoulder at a laptop showing an Odoo dashboard
First look at what is really running, then decide.

We're still on an old version and don't dare to migrate

Every version you skip makes the jump bigger. We first map out what is blocking the migration, and only then do we plan it.

Our custom modules break with every update

Customisation that overrides the standard instead of extending it is guaranteed to break. We determine per module whether it can go back to standard.

The project has been overrunning for months and nobody can say why

Usually there is no scope that everyone knows. We make the open items visible and give them an order and an owner.

Our partner no longer responds

We take over the management without you having to cancel anything first. We handle the handover properly, even if contact is difficult.

Half our team still just works in Excel

Shadow administration is a symptom, not laziness. We find out which step in Odoo is too slow or too illogical and fix that first.

We pay licences for apps nobody uses

We set usage against licences and show you which apps you can switch off or finally set up properly.

The first week

What we do in the first week

No thirty-page quote before we've seen your system. We start by looking, listening and measuring. By the end of week one you know what's going on and what the options are.

Day 1Day 5

Five steps, five working days, one fixed point of contact.

45-minute intro call

You tell us what's going wrong, we ask follow-up questions. By the end of the conversation you already know which three things we would investigate first.

Technical assessment

Version, installed apps, custom modules, integrations and the state of your data. We read the code, not just the documentation.

Conversations with the users

We talk to the people who work in it every day. They know exactly where the friction is and which step everyone skips.

Risks and quick wins at a glance

What can already be better next week, and what is a real risk to your continuity? We keep those two lists strictly separate.

Plan with three routes

Repair, back to standard, or take over and build on. Each route states what it delivers and what it asks of your team.

Workshop with whiteboard and post-its during the inventory

Clear agreements

What we do — and what we don't

What we do

  • Diagnosis first, tools later. We don't touch anything until we know why it was built that way.
  • Back to standard where possible. Every module that returns to standard comes along with the next update.
  • Document custom work. What stays, we record: what it does, why it exists and what breaks if you remove it.
  • Map out the migration path. A route to a supported version, with test moments and a fallback option.

What we do not do

  • Criticise your current partner. We assess the system, not the people who built it.
  • Rebuild everything. A rebuild is almost never necessary and costs you the knowledge already in the system.
  • Chain you to us. Documentation and access are yours. If you want to continue with someone else, you hand everything over without us.
  • Starting work without a price. You know in advance what each step costs and when we stop to consult you.
Hands on a keyboard with a teal reflection during the technical inventory

Three routes

Which route suits your situation?

Fix what hurts now

Your version is still supported and the customisation is manageable, but a few processes are getting stuck. We fix those without touching the rest: shortest route, smallest impact on your team.

  • Blocking errors first
  • Permissions and roles reset
  • Short refresher training for key users
Abstract network of nodes in navy and teal

Back to standard, then migrate

Your customisation breaks with every update. We determine per module whether a standard feature from a newer version now takes over, rebuild the rest properly as an extension, and then migrate in one go on a test environment.

  • Assessed module by module
  • Test environment before anything goes live
  • Fallback option on migration day
Data centre with blue and teal lights

Take over and build on

There is no longer anyone managing your environment. We take over the management, clear the backlog and then pick up the apps that were never finished — on the same terms as on €1,000 per app.

  • Access and documentation in order
  • Fixed point of contact for your team
  • Overdue apps delivered after all
Abstract light bridge between two systems

After the diagnosis

What it costs afterwards

Repair work starts with reconfiguring, and the same rate applies as for a new implementation: €1,000 per app. You can read exactly what that covers on €1,000 per app. If it turns out to require real custom work, that goes through our custom project with a separate estimate per module.

Any amounts other than €1,000 per app follow from the diagnosis and are set out in your plan.
ComponentPrice
45-minute diagnosisFree
Reconfigure standard app€1,000 per app
Repair or phase out a custom moduleenter amount
Migration to a newer Odoo versionenter amount
Ongoing management and supportenter amount

Your environment in numbers

After the diagnosis you fill in these three lines together with us. We don't fill them in beforehand with figures we don't know.

Rescued implementationsenter number
Average recovery lead timeenter period
Customers who stayedenter percentage

“enter customer quote”

Frequently asked questions

What customers ask us before the diagnosis

Yes. We take over Odoo implementations that were started or abandoned by another partner. You don't need to prove anything: we start with a diagnosis of your current environment and tell you exactly what we find, even if that means there is little wrong.

The 45-minute diagnosis is free and without obligation. Afterwards you receive a short written summary with the main risks and three possible routes. Only if you choose to go further do we draw up a plan with a price per step.

No. You don't need to cancel the contract with your current partner before we take a look. Only once you decide to go further with us do we discuss together how the handover of access, code and documentation is done properly.

Yes. A migration to a newer Odoo version can be a stand-alone assignment. We take stock of your customisations and integrations, determine what can come along and what is dropped, and first run the migration on a test environment with a fallback option.

Then we say so, and we show you the alternative straight away. In many cases a standard feature in a newer Odoo version now covers what the customisation once solved, so you can retire the module instead of rebuilding it.

You'll hear from us quickly after your request. We schedule the diagnosis in consultation with you; the start date of the repair work depends on the scope and is agreed together in the plan.

We can help then too. We first check whether your processes can be handled on Community with standard features or an OCA module, and say explicitly when an Enterprise feature is the better choice.

Let a fresh pair of eyes take a look

Tell us in 45 minutes what's going wrong. You'll hear from us quickly, and after the conversation you get a summary you can use even without us. Want to know more about who you'll be talking to? Read about us or view our cases and results.

Handshake at the end of an intro meeting