Odoo 19 Migration Checklist Best Practices for a Risk-Free Upgrade

How to Use This Checklist

This checklist is structured around the actual phases of an Odoo 19 migration - from pre-migration discovery through post-go-live stabilisation. Each item is a decision or action that needs a responsible owner and a completion date before the next phase begins.

If you have not already read through how Odoo migration works as a process, the checklist will be more useful after that context. Each item here maps to a phase described in detail elsewhere in this series.

Full migration process explained in: How Odoo Migration Works - A Step-by-Step Guide [2026]

Pre-Migration: Discovery and Planning

1. Current system audit

1. Document your current Odoo version and edition (Community or Enterprise)
2. List every installed module - standard, custom, and third-party
3. Record database size and record counts for: customers, vendors, products, sales orders, purchase orders, invoices, inventory moves, journal entries
4. Identify every external integration: what system, what method (API, webhook, direct DB), and who owns it
5. Document the five to ten workflows that cannot break on go-live
6. Identify who in the business is responsible for UAT in each department

2. Version and edition decision

1. Confirm the target version is Odoo 19
2. Confirm whether you are migrating Community to Enterprise or staying on the same edition
3. If switching to Enterprise: list the Enterprise modules you plan to activate and confirm your current workflows map to them
4. Confirm hosting: Odoo.sh, self-managed VPS, or cloud provider
5. Confirm your Odoo 19 licence and user count with Odoo SA or your partner

3. Scope definition

1. Categorise every custom module: migrate, refactor, rebuild, or retire
2. Categorise every third-party module: available for Odoo 19, find alternative, or retire
3. Confirm which integrations need to be updated for Odoo 19 API changes
4. Identify data cleaning work required before migration begins
5. Document the go-live date and confirm it avoids month-end, quarter-end, and peak business periods
6. Define the rollback trigger conditions  under what circumstances will you revert to the old system

Pre-Migration: Data and Environment

4. Data cleaning

1. Run a duplicate customer and vendor report - resolve or merge duplicates before migration
2. Audit product records: every product should have a category, unit of measure, and cost method
3. Check for open orders referencing deleted or archived products - resolve before migration
4. Validate accounting data: check for unbalanced journal entries, missing partner links on payables and receivables
5. For manufacturing businesses: audit all BoMs - every component should be active, and units of measure should be consistent
6. For lot/serial tracked businesses: verify that every lot and serial number has a product assignment and a current location

5. Odoo 19 environment setup

1. Provision the staging server with the same or better specs as production
2. Install Odoo 19 in the staging environment
3. Install all required standard and Enterprise modules
4. Configure localisation: country, language, chart of accounts, tax configuration
5. Set up test user accounts for each department that will run UAT

Migration Execution

6. First staging migration run

1. Export the current production database
2. Run migration scripts to transform the database schema from the current version to Odoo 19
3. Import migrated data into the staging environment
4. Run the Odoo 19 migration tool and review all warnings and errors
5. Log every error: the affected model, the record count, and the cause
6. Do not proceed to module installation until all critical data errors are resolved

7. Module installation and validation

1. Install refactored and rebuilt custom modules
2. For each module, run the module's own test suite if one exists
3. Verify that module-specific data (configuration records, default values) migrated correctly
4. Check that all external integration configurations are present and pointing to the correct endpoints

8. Data validation

1. Compare record counts: customers, vendors, products, open orders, invoices  new system should match old system
2. Reconcile financial totals: accounts receivable and payable balances should match between old and new systems
3. For inventory businesses: compare stock quantities per location between old and new systems
4. For manufacturing businesses: verify BoM count and component counts match
5. Run a sample traceability report on a lot-tracked product to confirm movement history is accessible
6. Run the second and third staging migration runs after fixing errors - repeat until the migration completes with no critical errors

Testing

9. Integration testing

1. Test the full sales cycle: quotation → order → delivery → invoice → payment
2. Test the full purchase cycle: RFQ → PO → receipt → vendor bill → payment
3. Test inventory: stock receipt, internal transfer, outgoing delivery, adjustment
4. Test accounting: journal entry, bank import, reconciliation, tax report
5. For manufacturing: test the full production cycle - BoM selection, work order creation, component consumption, production completion
6. Test every external integration under realistic transaction volume
7. Test all custom modules against their original functional specification

10. User acceptance testing

1. Distribute UAT scripts to department leads - one script per department
2. Set UAT start date, end date, and issue submission deadline
3. Collect and triage all reported issues: critical (blocks UAT), major (workaround exists), minor (cosmetic or low impact)
4. Fix all critical and major issues before UAT sign-off
5. Obtain written sign-off from each department head
6. Confirm no critical or major open issues remain before scheduling go-live

Go-Live

11. Cut-over preparation

1. Communicate go-live date and freeze schedule to all users at least two weeks in advance
2. Confirm the old system freeze time with all departments
3. Run a final data export from the old system the day before go-live
4. Run the delta migration: capture any transactions entered since the last staging run
5. Validate the delta in staging before going live
6. Confirm rollback procedure is tested and documented

12. Go-live execution

1. Execute go-live on the confirmed date - Monday morning preferred
2. Switch user access to the new system
3. Confirm all department leads can log in and access their primary workflows
4. Have technical support available for the full first business day
5. Monitor system performance throughout the first day under real production load
6. Archive the old system - do not decommission it for at least 30 days after go-live

Post Go-Live

13. Stabilisation - first 30 days

1. Run daily check-ins with department leads during the first week
2. Track all issues reported post-go-live in a central log
3. Fix critical issues within 24 hours, major issues within 5 business days
4. Monitor system performance at end of day one, end of week one, and end of week two
5. Confirm the first period-end close completes correctly in the new system
6. Confirm all integrations are running correctly under production volume
7. Conduct user training sessions for any department with low adoption or frequent issues
8. After 30 days: document lessons learned and close the migration project formally

Definition of a successful migration: The first period-end close completes correctly in the new system, all integrations are running, no critical issues remain open, and department leads confirm their teams are operational. That is the finish line.

Odoo 19-Specific Items to Check

In addition to the standard migration checklist, Odoo 19 introduced specific changes that need attention during migration and testing.

The full breakdown of what changed in Odoo 19 and which features are most relevant by business type is covered in: Why Upgrade to Odoo 19? Key Features, Benefits, and Migration ROI [2026]