Otog outdoor: 171,041 rows of data, none of them lost
Otog outdoor, an outdoor and hiking gear store, moved from its old program to Meridian in two weeks. Here is how the numbers showed that nothing was left behind.
171,041rows moved without lossEvery business about to change its software starts with the same question: “What happens to our old data?” Sales history, stock on hand, customer balances: nobody wants to leave behind what took years to build up. Otog outdoor’s migration answered that question in numbers.
The client
Otog outdoor is an outdoor and hiking gear store. Today its tills, accounting and stock run on Meridian ERP, and its online store runs on Meridian’s e-commerce platform.
How the migration was done
Register everything
Every table and column of the old system was listed and registered: 425 of 425 columns, so no field was left unaccounted for.
Move, then reconcile
After the move, row counts and account balances were checked against the old system. 171,041 of 171,041 rows arrived.
Acceptance tests
Before going live, 20 acceptance tests were run, and 20 passed.
- 171,041 / 171,041rows moved
- 425 / 425columns registered
- 20 / 20acceptance tests passed
The result
Otog outdoor was working on the new system within two weeks. Its financial history, balances and customers came along.
What to take from it
- Accept a migration by its numbers, not by “it should be fine”: row counts and account balances must be equal in both systems.
- Register the tables and columns before you move anything. You will not be hunting for a missing field afterwards.
- Run the acceptance tests on everyday work: make a sale, make a return, pull a report.
