Moving 3.3 TB of Odoo data across six major versions, with zero loss
Measured outcomes
Reported outcomes and the attribution attached to this project record.
AttributionThis migration was delivered by Kama Adhitia, our core team's ERP Engineering Lead, at a previous employer before Invero was founded.
- 01of transactional data migrated
- 3.3 TB
- 02records lost during the migration
- 0
- 03average query response time
- < 1 s
- 04uptime SLA after go-live
- 99.9%
Context
A company was running its day-to-day operations on Odoo v12, with Odoo v18 as the migration target. Years of activity had accumulated into 3.3 TB of transactional data. Any disruption to the system meant direct disruption to the business.
Challenge
Jumping six major versions in one move carried real risk to data integrity. The business could not stop, so extended downtime was off the table. And at 3.3 TB, query performance had to hold up after the move.
Solution
Before Invero was founded, Kama Adhitia led a phased Odoo v12-to-v18 migration covering 3.3 TB of transactional data. The switch ran as a zero-downtime deployment, so operations continued as normal throughout. Post-migration, PostgreSQL queries were tuned to an average response time below 1 second. The engagement used a 99.9% uptime SLA target after go-live.
Architecture & stack
Technologies and system components named in this project record.
- 01Odoo v12 → v18Component
- 02PostgreSQLComponent
Attribution
This migration was delivered by Kama Adhitia, our core team's ERP Engineering Lead, at a previous employer before Invero was founded.