# Odoo Migration Checklist

Use this checklist during Odoo version upgrade planning and cutover. Mark each item when complete and note the owner and date in your project tracker.

---

## 1. Pre-Migration Assessment

- [ ] Current Odoo version and target version documented
- [ ] Custom module inventory completed (name, author, last updated, business criticality)
- [ ] Third-party apps and OCA modules reviewed for target version compatibility
- [ ] Integration endpoints inventoried (APIs, webhooks, EDI, payment gateways)
- [ ] Database size and growth trend recorded
- [ ] Staging environment provisioned with production-like data volume
- [ ] Migration approach agreed (in-place upgrade, parallel run, phased module rollout)
- [ ] Executive sponsor and project lead assigned

## 2. Custom Module & Code Review

- [ ] Each custom module classified: port, replace with standard, retire, or defer
- [ ] Deprecated API usage identified in custom Python and JavaScript
- [ ] View and report XML validated against target version schema changes
- [ ] Security rules and access rights reviewed for model changes
- [ ] Automated tests exist or test plan defined for critical custom logic
- [ ] Technical debt items logged with effort estimates

## 3. Data & Configuration

- [ ] Master data cleanup completed (duplicates, inactive records, orphaned links)
- [ ] Chart of accounts and fiscal settings validated for target version
- [ ] Sequences, email templates, and automated actions reviewed
- [ ] Scheduled actions (cron) documented with frequency and business impact
- [ ] Filestore size assessed; attachment archival policy defined if needed
- [ ] Multi-company and multi-currency settings verified

## 4. Testing Plan

- [ ] Test scenarios defined for each critical business flow
- [ ] Test data set prepared (representative orders, invoices, inventory moves)
- [ ] Regression test owners assigned by department
- [ ] Integration smoke tests scripted for production-like endpoints
- [ ] Performance baseline captured on staging before and after migration
- [ ] User acceptance testing (UAT) schedule published with sign-off criteria
- [ ] Defect triage process and severity definitions agreed

## 5. Cutover Planning

- [ ] Cutover window scheduled with minimal business disruption
- [ ] Freeze period defined for configuration changes and new customizations
- [ ] Final data sync strategy documented (delta load, downtime window)
- [ ] Rollback criteria and decision authority defined
- [ ] Communication plan drafted for internal teams and external partners
- [ ] Go/no-go checklist prepared for cutover day
- [ ] DNS, SSL, and infrastructure changes planned if hosting moves

## 6. Cutover Day

- [ ] Production backup verified and restorable
- [ ] Users notified of maintenance window
- [ ] Migration executed on staging dry-run within last 7 days
- [ ] Production migration started; progress monitored
- [ ] Post-migration smoke tests passed (login, sales order, invoice, inventory)
- [ ] Integrations re-enabled and validated
- [ ] Critical reports run and reconciled against pre-migration baselines
- [ ] Go/no-go decision recorded with sign-off

## 7. Hypercare & Post-Migration

- [ ] Hypercare support schedule defined (first 48 hours, first week, first month)
- [ ] Known issues and workarounds published to users
- [ ] Monitoring alerts configured for errors, queue depth, and slow queries
- [ ] Feedback channel open for user-reported defects
- [ ] Post-migration review scheduled within 30 days
- [ ] Remaining module ports and enhancements prioritized in backlog

---

**Notes**

| Item | Owner | Target Date | Status |
|------|-------|-------------|--------|
|      |       |             |        |
|      |       |             |        |
|      |       |             |        |