Odoo implementation checklist: 26 checkpoints from preparation to go-live

Search for an Odoo implementation checklist and you will mostly find lists of thirty loose tips. The problem of an implementation is rarely a missing tip - it is a missing order. So below is not a tips list but the runbook: seven phases, 26 checkpoints, from appointing your project lead to closing the project after the buffer period. Free to use, whichever partner you work with - and downloadable as a checkable PDF, no form in front of it.

Download the checklist as a PDF

Download the Odoo implementation checklist (PDF) - checkable, in colour, with links to the matching tools. Print it and pin it to the project board. Also available in Dutch and German.

Phase 0 - Preparation

The phase most often skipped, and the phase where the project is already won or lost. Before anyone configures anything:

Appoint one internal project lead (SPOC) and make their availability explicit - it sets the pace more than any technical choice.
Assign a key user per process who decides, tests and later supports colleagues - what a key user actually does.
Pick your go-live date and count back, including two months of buffer for testing and overrun - the go-live planner does it in a minute.
Set a budget frame based on scope, not the other way round - what an implementation costs.

Phase 1 - Fit-gap & scope

This is where the project gets made predictable - or not. It is the phase we spend the most time on, for a reason:

Map per process what actually happens, not what the manual says.
Record per line: standard, configuration or custom. This becomes the scoping table that turns the project into a predictable one - the core of our TARGET method.
Name every integration separately and request the specifications now. Third parties set their own pace; whoever requests specs during the build, waits during the build.
Assess data quality honestly. Migrating clean data is a task; cleaning it first is a sub-project.
Agree a definition of done per process before anything gets built.
Decide what goes live in phase one and what deliberately comes later. Scope is a dial, not a given.

Phase 2 - Configuration

Set up the chart of accounts and reporting structure first - everything books back to it, and redistributing afterwards is manual labour.
Configure roles and permissions before the first user enters the system.
Build the main flow working end to end: quote, order, delivery, invoice.
Start integrations as early as possible and test them with real data.

Phase 3 - Data

Clean the source data in the old system, not during the migration.
Run a trial migration and have key users validate the outcome - they recognise what is missing.
Agree a date after which the old system is frozen. Two living systems is not a transition but a second administration.

Phase 4 - Testing & training

Have key users test with real scenarios from their own practice, not demo data.
Collect findings on one list and triage: blocking, before go-live, or after.
Train end users on their own work, not on the whole system.

Phase 5 - Go-live

Fix go/no-go criteria up front and agree who decides.
Write a cutover runbook: what moves when, and what the fallback is.
Plan hypercare: short lines and daily check-ins in the first weeks.

Phase 6 - After go-live

The phase missing from most checklists, and the difference between a system that lands and a system that gets tolerated:

Keep one wish list and schedule further development in a fixed rhythm.
Evaluate with the key users after a month: what works, what grates.
Close the project only once the buffer-period findings are resolved.

The honest footnote to every checklist

A checklist feels like grip, but the paper is not the work. The two checkpoints projects genuinely strand on are not the technical ones: they are the project lead who is not given the time, and the scoping table that gets skipped because “we know what we want”. Take those two seriously and you can work through the rest of this list with confidence - skip them, and no checklist will save you.

Want the complete approach behind this checklist, with the why per step: it is in our book “How we do Odoo” - free to download, and also without a form full of mandatory fields.

Rather walk the checklist along your own situation together? Book a free Odoo scan - we go through the phases with your processes as the starting point, and we are honest about where the risks sit.

Frequently asked questions

What belongs in a good Odoo implementation checklist?

The order, not just the tasks. Seven phases: preparation (project lead, key users, date, budget), fit-gap and scope (the scoping table), configuration, data, testing and training, go-live, and aftercare. Most failed implementations do not skip tasks but phases - especially the fit-gap up front and the evaluation afterwards.

What is the most important step of an ERP implementation?

The most boring one: recording up front, per process, what works standard, what is configuration and what genuinely has to be built - the scoping table. Nearly everything that goes wrong later traces back to something left unsaid in that step. The second most important: an internal project lead who genuinely gets the time.

Does this checklist also work for other ERP systems?

Largely, yes. The phases - preparation, fit-gap, configuration, data, testing, go-live, aftercare - apply to any serious ERP implementation, from Odoo to Dynamics or SAP. What differs per system is how much counts as "standard" in the scoping table; with Odoo that share is large, and that helps in every phase after it.

Why is there a two-month buffer in the planning?

Because every go-live runs into three things you cannot schedule: test findings that genuinely need fixing, wishes that only surface once people see the system, and plain overrun. Planning without a buffer means trading quality under pressure - exactly in the weeks that decide whether users embrace the system.

Can I download this checklist as a PDF?

Yes, free and without a form: the checklist is available as a checkable PDF at fanatics.nl/downloads/odoo-implementation-checklist-en.pdf, in house style, with links to the matching tools and deep-dives. Print it, pin it to the project board, and tick away.

What if a checkpoint turns out to be unfeasible for us?

Then that is a signal, not a failure. A checkpoint that stays open - the project lead gets no time, the data turns out dirty, an integration has no specifications - points to a risk that is cheap to address now and expensive during go-live. Discuss it, shift the planning or the scope, and only tick it once it genuinely stands.

Recognize this from your own setup?

A 30-min scan turns hunches into a concrete view, what stays standard Odoo, what becomes custom, what doesn’t need code at all.

Get in touch ← Back to blog