An Odoo 20 migration is a business-continuity project. When your teams rely on Odoo for manufacturing, inventory, purchasing, sales, accounting, and customer commitments, an unplanned change can interrupt work at the worst possible time.
For Canadian manufacturers managing volatile input costs, cross-border supply chains, labour constraints, and customer delivery commitments, the Odoo 20 migration checklist should be a shared plan for business leaders, IT teams, and operational managers. That plan should cover your current setup, custom work, third-party apps, data, users, testing, and the production cutover, especially during busy fall schedules, Q4 planning, inventory activity, and year-end preparation.
Start with Scope and Ownership
Odoo’s upgrade service supports the database upgrade process for standard, supported Odoo components. That is an important starting point, but an upgraded database is not automatically ready for production. Odoo’s upgrade service handles the technical database upgrade, while businesses and their partners still need to validate custom modules, integrations, reports, approval flows, and day-to-day workflows before production.
Clear ownership should be established before migration work begins. Your internal team knows the real-world workflows, while your Odoo partner can assess technical impacts, test custom code, and help plan the deployment. Integration vendors may also need to confirm compatibility and provide support during testing.
A simple responsibility matrix should identify who is responsible for:
- Reviewing Odoo custom modules, fields, automated actions, and reports
- Confirming third-party app and integration compatibility
- Testing business workflows and approving results
- Fixing issues, retesting changes, and approving production deployment
Before any upgrade work starts, audit the current Odoo environment. Record the version, hosting model, installed apps, user groups, integrations, custom modules, reports, scheduled jobs, security rules, and business-critical workflows. Teams should also flag old workarounds and unused customizations. Some may no longer be worth carrying forward if standard Odoo 20 functions now cover the same need.
Review Odoo 20 Changes, Code, and Connections
Odoo 20-specific changes deserve attention before general upgrade work begins. Manufacturing teams should compare current processes with Odoo 20 Manufacturing Order behaviour, including draft versus confirmed Manufacturing Orders, BoM consumption, scheduling, changed buttons, and user actions. Small screen-level changes can affect how shop-floor staff reserve materials, report consumption, schedule work, or complete production steps.
For manufacturers, the revised workflow must still support production scheduling, inventory reservations, material consumption, traceability, reporting, and the roles assigned to each user.
Custom development can add another layer to the Odoo 20 upgrade process. Review custom fields, workflows, automated actions, reports, security settings, and dependencies between modules. Customizations that support a real operational requirement may need updates. Others may be legacy workarounds that can be retired.
Third-party apps and integrations need the same review. This includes Odoo Community modules, e-commerce connectors, payment systems, shipping platforms, EDI exchanges, BI tools, external APIs, and Canadian tax or accounting connections for GST/HST, PST, QST, payroll, and cross-border transactions where they apply. Before the migration window is selected, confirm the app version, integration owner, vendor support contact, credentials, and testing responsibility.
Odoo’s documentation and release notes can help your team identify product changes, but they do not replace testing against your own processes. Your environment may include custom code or connected systems that change the result.
Test Data and Workflows Before Production
A backup is only useful if it can be restored. Before migration, confirm that backups include the database, attachments, documents, integration settings, and operating data your teams need. For on-premise deployments, also review server capacity, storage, operating system dependencies, monitoring, and internal IT access.
Production should never be the first place where you validate an Odoo 20 upgrade. Use an upgraded copy of the database in a controlled environment to test Odoo 20-specific workflow changes, custom modules, third-party apps, scheduled jobs, permissions, reports, integrations, and data integrity before the production cutover.
Screen-by-screen testing is not enough. Complete business scenarios that mirror how your team actually works:
- Convert a sales order through purchasing, manufacturing, delivery, invoicing, and payment
- Receive materials, reserve components, and consume them through a Manufacturing Order
- Process inventory adjustments, transfers, returns, and traceability checks
- Run accounting reports and complete month-end review tasks
- Test user permissions, approvals, automated actions, and exception handling
User acceptance testing matters because the people doing the work often notice issues that technical checks miss. Log each issue, assign an owner, confirm the fix, retest it, and obtain formal business sign-off before approving production.
Plan the Cutover and Use This Checklist
A production Odoo 20 upgrade needs a realistic window. Avoid month-end close, external audits, physical inventory counts, major customer shipments, production peaks, and year-end preparation. Canadian businesses should also account for statutory holidays, fiscal-year reporting deadlines, and periods when cross-border shipping or supplier lead times may affect operations. Late fall can bring extra pressure as teams prepare for Q4 demand and fiscal reporting, so planning ahead gives everyone more room to test and respond.
Your cutover plan should include a final backup, user communications, expected downtime or process limits, escalation contacts, decision authority, and post-upgrade validation. Users should know in advance which screens, buttons, Manufacturing Order steps, or reports may look different after the upgrade.
Use this Odoo upgrade checklist before approving the production date:
- Audit the current Odoo environment, document custom modules, and assess customizations for ongoing value
- Review Odoo 20 workflow changes, third-party apps, integrations, support contacts, and compatibility
- Check data quality, restore backups successfully, and complete a test migration
- Validate critical workflows, resolve issues, retest fixes, and collect business sign-off
- Confirm responsibilities, approve the production window, prepare communications, and assign post-upgrade validation
If you are running Odoo 17, confirm the support status that applies to your edition and hosting model against Odoo’s current policy. Odoo’s support schedule lists September 2026 as the planned end of standard support for Odoo 17.0.
Know When You Are Ready to Move Forward
Being upgrade-ready means more than completing the technical Odoo database upgrade. Your organisation should understand its current environment, know which customizations and integrations require attention, test the workflows that keep the business moving, and resolve material issues before the production cutover.
A safe Odoo migration process also has clear owners, prepared users, restored backups, tested contingency plans, and a production window that respects operational reality. When those pieces are in place, the move to Odoo 20 can support your business without turning a planned upgrade into an operational surprise.
Turn Migration Planning Into Operational Confidence
Use our Odoo 20 migration checklist to assess the business decisions, technical dependencies, and readiness criteria that deserve attention before your upgrade. Kodershop helps Canadian organizations align their ERP transition with day-to-day operational needs and long-term goals. If you need guidance tailored to your environment, contact us to discuss your migration priorities with our team.