Going live on a new ERP is the moment every Odoo project is judged. Get the run-up right and go-live is a quiet, almost boring weekend. Get it wrong and you spend the first month firefighting instead of running your business.
This is the checklist we work through before go-live on every Odoo implementation we run. Use it as a template for your own rollout, whether you are doing it in-house or with an Odoo implementation partner.
1. Lock down scope and processes first
Most Odoo projects do not fail on technology. They stall because the processes were never agreed before configuration started, so the system ends up modelling confusion instead of removing it.
Before anyone configures a thing, get clear on:
- Your core workflows, end to end (order to cash, procure to pay, hire to retire)
- What stays standard Odoo and what genuinely needs to change
- The handful of numbers go-live will actually be judged on
A short Odoo consulting engagement up front almost always pays for itself here. It is far cheaper to redraw a process on a whiteboard than to rebuild it in code after go-live.
2. Treat data migration as its own workstream
Data migration is where ERP rollouts quietly go wrong. Bad data makes a good system look broken on day one, and trust is hard to win back. We cover this in depth in our guide to migrating to Odoo without losing your data, but the essentials are:
- Clean before you migrate. Do not carry years of duplicates and dead records into a fresh system.
- Map every field. Know exactly where each piece of legacy data lands in Odoo.
- Reconcile with finance. Opening balances and stock counts must be signed off by someone who owns the numbers.
- Do a full dry run. Import into a staging database and check totals before the real thing.
If you are moving off an older ERP, a structured Odoo migration plan keeps this from becoming a last-minute scramble.
3. Configure first, customize only when needed
Every customization is a line of code that someone maintains for years, and a thing that can break on the next upgrade. Favour configuration. Reach for development only when a real business need cannot be met any other way.
When you do need to extend Odoo, scope it tightly with your Odoo customization team and write down why each change exists. Future you will be grateful.
4. Connect the rest of your stack
Very few businesses run on Odoo alone. Your website, payment gateway, shipping provider and reporting tools all need to talk to it. Plan these Odoo integrations early, because they often have the longest lead times and the most edge cases.
5. Test like it is already live
User acceptance testing (UAT) is your dress rehearsal. Skipping it is how avoidable bugs reach real customers.
- Build test scripts from real scenarios, not happy-path demos
- Have actual end users run the tests, not just the project team
- Log every issue and triage by severity so nothing critical slips through
6. Train the people who will use it daily
Adoption is the real measure of success. A perfect system nobody trusts is a failed project. Run role-based training, write short guides for the tasks each team does most, and name an internal champion in every department who can answer the small questions.
7. Plan the cutover
Go-live is an event, so give it a plan:
- Pick a low-traffic window
- Freeze the old system so data cannot drift between the two
- Write an hour-by-hour runbook with named owners
- Agree rollback criteria before you start, not in the heat of the moment
8. Line up support before, not after
The first two weeks after go-live generate the most questions you will ever get. Have help ready. Agree an Odoo support plan and clear response times in advance, so your team always knows who to call.
Key takeaways
- Agree processes and scope before touching configuration
- Treat data migration as its own workstream with finance signed off
- Configure first, customize sparingly
- Make real users test and train before go-live
- Have support and a rollback plan ready on day one
Planning a rollout? Talk to our team or see how we run Odoo implementation services from first call to go-live. If you work in a specific sector, we also tailor Odoo for industries like manufacturing.
Frequently asked questions
How long does an Odoo implementation take?+
It depends on scope. A focused rollout of a few core modules can take 6 to 10 weeks, while a multi-department implementation with custom development and integrations runs longer. Agreeing scope early (step 1 above) is what keeps the timeline honest.
What is the most common reason Odoo go-lives slip?+
Data migration and untested edge cases. Both are avoidable with a proper dry run and real user acceptance testing before the cutover date.
Should we customize Odoo or stick to standard features?+
Start standard. Configure what you can, and only build custom features when a genuine business need cannot be met otherwise. Every customization is a long-term maintenance and upgrade cost.
Do we need an Odoo partner, or can we implement it ourselves?+
Smaller, standard rollouts can be done in-house with the right people. Once you have data migration, integrations or custom development in the mix, an experienced partner usually de-risks the project and pays for itself.
Have a project in mind?
Tell us what you're building and we'll reply within one business day.
- +91 86259 45569
- info@kalztech.in
- Chat on WhatsApp
- Pune, Maharashtra, India
