The odoo migration cutover is the riskiest 48 hours in any ERP project. This guide covers how to plan the freeze window, choose between a parallel run and hard cutover, sequence the import, reconcile balances, and activate a rollback if something fails.
Key Takeaways
- A prepared odoo migration cutover runs Friday freeze, Saturday import, Sunday validation, Monday live, but only when data was cleaned during staging.
- The freeze window stops all transactions in the old system so the final export is accurate and not stale.
- Parallel run keeps both systems live for two to four weeks. Hard cutover ends the old system immediately. Choose based on complexity.
- Define the rollback plan before the cutover starts. If validation fails, the old system is reactivated and no data is lost.
- Partner support on the first business day is mandatory. Critical issues must be reachable within 15 minutes.
Table of Contents
Why the Odoo Migration Cutover Is the Riskiest Phase
Most ERP projects fail during the transition, not during configuration. Data that looked correct in staging reveals gaps under live conditions, and teams that seemed trained freeze when real transactions must be processed. The cutover concentrates all of these risks into a single weekend.
- From the cutover moment, Odoo holds the authoritative data and every transaction happens in Odoo only.
- Data gaps discovered live are expensive. An unreconciled receivable means payment allocations are wrong from day one, and correcting them takes weeks.
- Teams that have run the import script in staging and rehearsed the rollback procedure are executing a rehearsed plan, not taking a risk.
The odoo migration cutover is only as reliable as the staging work that preceded it. Problems surfacing on the weekend should have been fixed weeks earlier.
Planning the Freeze Window
The freeze window is when the old system stops accepting new transactions, making the final export accurate.
What happens during the freeze
- The old system is locked. No new orders, invoices, or stock movements are accepted after the freeze time.
- All pending invoices, deliveries, and payments must be completed before the freeze time.
- Open items that cannot be completed are documented separately and imported manually into Odoo.
- The final data export runs immediately after the freeze and becomes the source for the production import.
- The freeze typically starts Friday evening to allow the full weekend for import and validation.
Communicate the freeze date at least two weeks in advance. Sales must close open orders. Purchase must confirm pending receipts. Finance must post all unposted entries. Any transaction created after the freeze but before import creates a data gap that is difficult to trace.
Parallel Run vs Hard Cutover
Parallel Run
- Both systems run simultaneously for two to four weeks with teams entering transactions in both
- Results are compared each week and discrepancies investigated before the next cycle
- Odoo becomes the sole system once parallel results match consistently
- Catches data gaps and builds team confidence but requires double data entry
Hard Cutover
- Old system stops and Odoo starts with no overlap between the two
- All transactions from the cutover date forward happen only in Odoo
- Old system is kept in a read only mode for historical reference
- Faster and cleaner but carries higher risk if staging validation was incomplete
Recommendation: Use a parallel run for manufacturing, multi-warehouse, or multi-entity businesses. A hard cutover suits smaller businesses where staging validation was thorough. Either approach must fit within the overall implementation timeline.
Import Sequencing During the Cutover
The import order is not flexible. Master data must exist before transactions can reference it. Importing in the wrong sequence creates orphaned records that cause errors under live conditions.
Correct import order
- Chart of accounts first so every transaction has an account to reference
- Customers and vendors second so invoices and orders have a valid counterparty
- Products and categories third before stock quantities and orders
- Warehouses and locations fourth before any stock movement is recorded
- Opening balances fifth covering trial balance, receivables, payables, bank, and stock
- Open transactions last covering pending orders, unpaid invoices, and outstanding bills
Importing transactions before master data causes orphaned records. An invoice referencing a customer not yet in the system will fail or create a blank record. These errors compound quickly.
Reconciliation Before Go-Live
Every balance in Odoo must match the source system on the cutover date. Review the Odoo accounting configuration checklist before running reconciliation to confirm all accounts are mapped correctly.
Required reconciliation checks
- Trial balance must match the source system to the rupee on the cutover date
- Outstanding invoices must match customer by customer above a defined threshold
- Outstanding bills must match vendor by vendor
- Each bank account must match the actual bank statement balance on the freeze date
- Stock value per warehouse must match the source system and any physical count performed
- Count and value of pending orders must match between both systems
If any reconciliation check fails, do not go live. Fix the data, reimport the corrected records, and revalidate. Going live with unreconciled balances means every financial report is unreliable from day one.
Rollback Planning for the Cutover
A rollback plan must exist before the odoo migration cutover begins. Review your Odoo database backup and restore procedures in advance so the team knows exactly how to restore the system to its frozen state.
Rollback plan components
- Define exact trigger conditions such as a trial balance mismatch above a set threshold or more than five percent of records failing validation
- The rollback action reactivates the old system from its frozen state. No data is lost because the system was frozen rather than deleted.
- Set the decision deadline at Sunday evening. Once Monday transactions begin, rolling back becomes exponentially harder.
- Prepare a template to notify all teams within 30 minutes with instructions on which system to use.
Communicating the Switch to Your Teams
The odoo migration cutover is an organizational change, not just a technical one. Every department is affected, and poor communication is one of the most common causes of chaos on the first day.
- Two weeks out, announce the cutover date, freeze time, and departmental tasks to complete beforehand
- One week out, confirm that Odoo team training is complete, distribute login credentials, and share the Monday checklist
- On freeze day, confirm all pending transactions are completed or documented, then send the freeze announcement
- On Monday, run a brief morning meeting, walk through the first transaction, and clarify the escalation path
First-Day Support After the Odoo Migration Cutover
The Odoo implementation partner must be available on the first day of live operations. A critical issue with no one to fix it is the most expensive outcome of any odoo migration cutover.
What the partner must provide on day one
- A named contact reachable within 15 minutes for any blocking issue
- Blocking issues resolved within two hours, lower priority issues addressed the same day
- Transaction support for sales through the first order, finance through the first invoice, and warehouse through the first receipt
- End of day verification to confirm all transactions before day two begins
First-day support transitions to a 30-day hypercare period with same-day response, covering the critical early adoption window.
Common Odoo Migration Cutover Mistakes
- Cutting over on the 15th instead of the 1st splits accounting data and creates GST complications
- Skipping the freeze window lets teams keep entering data while the import runs, making production data stale
- Skipping staging imports means errors surface under live pressure with no rehearsed fix procedure
- Having no rollback plan turns a critical issue Sunday night into Monday morning chaos
- Training after cutover means errors are committed into the live database while teams are still learning
- Decommissioning the old system on cutover day removes historical lookup capability. Keep it available for at least 90 days.
Weekend Runbook for the Odoo Migration Cutover
Each phase of the cutover weekend depends on the previous one completing successfully. Review the Odoo go live timeline to ensure the runbook fits within the broader project plan.
Friday Evening
- Freeze announced and old system locked for new entries
- All pending transactions confirmed as complete or documented as open items
- Final data export from the old system begins
Saturday
- Import master data covering chart of accounts, customers, vendors, and products
- Validate master data for record counts, mandatory fields, and duplicates
- Import opening balances covering trial balance, receivables, payables, and stock
- Import open transactions covering pending orders, unpaid invoices, and outstanding bills
- Run an initial reconciliation pass on trial balance and receivable and payable totals
Sunday
- Run detailed reconciliation customer by customer and vendor by vendor
- Fix discrepancies and reimport corrected records
- Revalidate all checks after fixes are applied
- Make the go or rollback decision by early evening
- If go is confirmed, send the announcement to all teams with Monday instructions
Monday Morning
- Morning meeting to walk through the first transaction with the full team
- First real transaction in Odoo with partner on call
- End of day check to confirm all transactions before day two
Cutover Planning
Need a Partner Who Plans the Cutover, Not Just the Build?
Tatvamasi Labs handles odoo migration cutovers end to end with freeze windows, staging validation, rollback protocols, and partner support so the switch is rehearsed before it is executed.
Plan Your Cutover with UsFrequently Asked Questions
An odoo migration cutover is the moment your business stops using the old system and starts on Odoo. It includes a data freeze, final export, production import, balance reconciliation, and the first live transaction in the new system.
A well-prepared cutover takes one to two days following the pattern of Friday freeze, Saturday import, Sunday validation, and Monday go-live. Without staging prep, it can extend to a full week.
The freeze window is when the old system stops accepting new transactions. Nothing enters or leaves after the freeze time, ensuring the final export is accurate and not outdated by the time Odoo goes live.
A parallel run keeps both systems live for two to four weeks and suits businesses with complex operations. A hard cutover ends the old system immediately and suits simpler setups. The choice depends on operational complexity and how thoroughly staging validation was completed.
If critical checks fail, the rollback plan is activated and the old system is reactivated from its frozen state. No data is lost because the system was frozen rather than deleted. The cutover is rescheduled after the root cause is fixed.
April 1 is ideal for Indian businesses as it aligns with the new financial year and avoids split-period GST complications. If April 1 is not possible, the first day of any month avoids mid-month accounting issues.
The trial balance must match the source system to the rupee. Receivables must match customer by customer and payables vendor by vendor. Bank balances, stock values per warehouse, and open order counts and values must all align between both systems.
Prefer a quick chat? Reach the Tatvamasi Labs team directly on WhatsApp.
CHAT ON WHATSAPP
