Implementation · Go-live
The 12-point pre-go-live checklist we run on every Odoo project
The checklist our project managers sign off on before we flip the switch on any Odoo deployment, and what goes wrong when each point is skipped.
The 12 points at a glance
- Data migration dry-run and sign-off
- UAT with real workflows
- Integrations on production credentials
- Cutover plan with rollback
- Security roles reviewed by department heads
- Chart of accounts and opening balances
- Email and SMTP tested
- Scheduled actions reviewed
- Key reports compared to legacy output
- Training verified per department
- Support and escalation path confirmed
- Backup and recovery tested
In our experience, go-live problems are rarely caused by technical bugs. They're caused by skipped preparation steps: things every experienced team knows to check but sometimes doesn't, because the project was running late or the client was pushing to cut corners.
This is the actual checklist our project managers sign off on before we flip the switch on any Odoo deployment. It's not exhaustive, since every project has its own specifics, but it covers the checks that are easiest to skip under deadline pressure.
Data and migration readiness
1. Data migration dry-run completed and sign-off obtained
Running the migration script once in staging is not enough. We require at least two full dry-runs: one early in the project to surface structural issues, and one final run against a near-production dataset no more than a week before go-live. After the final run, a business stakeholder, not just the IT lead, must review the migrated records and sign off that the data looks correct. What goes wrong if you skip this: surprises on day one, like open purchase orders with wrong supplier references or customer balances that don't match your AR aging report.
2. User acceptance testing with real workflows, not demo data
UAT done on demo data is worse than no UAT at all. It creates false confidence. Every test scenario must use your actual product catalog, your real customer accounts, and your genuine workflow edge cases: the three-way match that breaks when a PO line gets partially received, the payroll run for employees with mid-month start dates, the manufacturing order for a product with nested sub-assemblies. If your users can't reproduce their hardest weekly task in the staging environment, go-live is not ready.
The most common sign that UAT wasn't thorough enough: users saying "this worked in testing" when something breaks on day one. It usually means they tested a simplified version of the workflow, not the real one.
Integrations and infrastructure
3. Integration endpoints tested with production credentials
Staging integrations almost always use sandbox API keys, test webhooks, and dummy credentials. Before go-live, every integration (your payment gateway, shipping carrier API, EDI connection, third-party WMS, or accounting sync) must be re-tested against real production endpoints. Token expiry, IP whitelisting, and rate limits behave differently in production. For example, a staging Stripe connection can work perfectly while the live key has a webhook URL mismatch that nobody catches until the first real sale.
4. Cutover plan documented with rollback procedure
Your cutover plan should be a step-by-step document with timestamps, responsible names, and explicit go/no-go decision points. It should answer: What is the last moment we can abort and revert to the legacy system? Who makes that call? How long does a rollback take, and what data entered in Odoo since cutover started would be lost? If you can't answer those three questions, you don't have a real cutover plan yet.
Key takeaway: A tested rollback procedure is what gives you the confidence to proceed. Teams that have a tested rollback path make cleaner go/no-go decisions under pressure.
Security and financial configuration
5. Security roles and access rights reviewed by department heads
Odoo's permission model is granular and powerful, which means it's also easy to misconfigure. The IT team can set up roles, but only department heads know whether those roles reflect actual job responsibilities. A warehouse picker should not have access to vendor pricing. An accounts payable clerk should not be able to post journal entries directly. Have each department head log in with a test account at their permission level and attempt three things they should not be able to do. If any of them succeed, the role hasn't been configured correctly.
6. Chart of accounts mapped and opening balances verified
The chart of accounts migration is one of the highest-risk pieces of any Odoo implementation. Every account in your legacy system must map cleanly to the new structure, and opening balances must be entered and verified before the first real transaction posts. Run a trial balance in both systems for the same period and reconcile the difference to zero, or document any intentional adjustments. Discovering a discrepancy in your retained earnings balance two weeks after go-live is a bad day for everyone.
Operations and automation
7. Email and SMTP configured and tested
Odoo sends a large volume of automated emails: sales order confirmations, purchase order emails to suppliers, invoice reminders, picking notifications, and more. Every one of these depends on a correctly configured outbound mail server. Before go-live, send a test email from every major document type (sales order, invoice, purchase order, delivery) and confirm it arrives correctly formatted in an external inbox. Also verify that inbound email aliases (for support tickets or sales inquiries) are routing correctly.
8. Scheduled actions reviewed: know what runs automatically
Odoo's scheduler runs dozens of automated tasks: payment follow-ups, stock replenishment rules, subscription renewals, payroll batch jobs, EDI syncs. Many of these are enabled by default and fire immediately once you're in production. Before go-live, open the Scheduled Actions list and audit every enabled action. Confirm you want it running, understand its frequency, and know what it will do to live data on its first execution. An automated overdue payment reminder that fires at 2 AM on day one, before your AR team has even been trained, is a predictable problem that's easy to prevent.
Reporting and training
9. Key reports compared to legacy system output
Pick five to ten reports your business relies on weekly (inventory valuation, sales by product category, aged receivables, payroll summary, production efficiency) and run them in both systems against the same period of historical data. The numbers don't have to match exactly (methodology differences are normal), but every variance must be explainable. If you can't explain why the numbers differ, you don't understand the new reports well enough to trust them. This comparison also surfaces misconfigured accounting settings that wouldn't otherwise appear until month-end close.
10. Training completion verified per department
Signing off that "training happened" is not the same as verifying that users can actually operate their workflows in Odoo. For each department, designate one power user who can demonstrate the end-to-end workflow without help from the implementation team. Warehouse: receive a purchase order, put it away, and pick against a sales order. Accounting: enter a vendor bill, match it to a PO, and run a payment batch. If your power users can't do this independently, your broader user base definitely can't, and your support load on day one will be unsustainable.
Support and recovery
11. Support contact and escalation path confirmed
Every user going live should know two things: who to call when something breaks, and what "something critical is broken" means in terms of response time. Document your support tiers before go-live. Tier 1 (user confusion, how-to questions) goes to your internal power user or help desk. Tier 2 (configuration issue, unexpected behavior) goes to your implementation partner. Tier 3 (data corruption, system down) is an emergency escalation with a defined response SLA. At Octagotech, critical issues on the Enterprise tier reach an on-call engineer 24/7 through our support desk, but the escalation path only works if it's been communicated and tested before the pressure is on.
12. Backup and recovery tested
This one is frequently acknowledged and rarely actually tested. "We have backups" and "we can restore from backup in under two hours" are very different statements. Before go-live, execute a full restore drill: take your most recent database backup, restore it to a clean environment, and verify that the application comes up correctly with all data intact. Time the process. If it takes six hours, that's critical information that changes your contingency planning. On Odoo.sh deployments this is straightforward; on self-hosted instances it requires more deliberate process.
Why this matters more than it sounds
Each of these 12 points can be skipped in under a minute: just check the box and move on. The problem is that the downstream cost of skipping any one of them is typically measured in days of recovery work, not hours. A missed data migration sign-off leads to a week of manual corrections. An untested rollback procedure means a botched cutover has no recovery path. Undertrained users generate a support volume that overwhelms both the internal team and the implementation partner simultaneously.
The checklist exists because project pressure compresses timelines and pushes even experienced teams to make optimistic assumptions. Having a signed-off checklist turns assumptions into documented facts.
If you're approaching go-live on an Odoo project and want a second set of eyes on your readiness, or if you're earlier in the process and want to understand how we structure implementation projects to make go-live less stressful, book a discovery call with our team. We're happy to do a pre-launch review or talk through your specific situation.
Approaching go-live?
30 minutes with a second set of eyes on your readiness before you flip the switch.
Book a discovery callKeep going
Related services and articles
A go-live with a date on it
Scoping, configuration, data migration, training and go-live on a dated plan at a fixed price.
Odoo implementation servicesTake the checklist with you
The pre-go-live checklist as a standalone guide for your project team.
Pre-go-live checklist guide ImplementationHow to prevent Odoo implementation failure: 3 essential checkpoints
Why rollouts stall, and the three checkpoints that keep a go-live on time and on budget.
ImplementationMigrating from QuickBooks to Odoo: the complete 2026 guide
What transfers cleanly, what you must clean first, and a four-phase method for a clean go-live.
Get a pre-launch review before you go live
The first call takes 30 minutes.
Or email sales@octagotech.com- USA +1 917 254 9416
- India +91 8153897751