Most factories do not fail their migration because the software is hard. They fail because the cut-over is a big-bang weekend with no fallback. This guide takes the opposite approach: import once, run in parallel for one settlement cycle, and switch only when both systems agree to the carat.
Day 1–2 · Import your masters
Start with the reference data every transaction depends on — parties, accounts, metals, processes and departments. These rarely change, so importing them first gives the rest of the week something stable to sit on.
- ◆Export party and account ledgers from Tally as CSV
- ◆Map rough purchase registers to lots and lot pricing
- ◆Load metal masters with their dated rate history
Day 3–4 · Load live stock
Bring in polished and rough stock as it stands today, with a date-wise snapshot so you can reconcile against your last physical tally. Barcode every packet as it lands so the floor can scan from day one.
Day 5 · Run in parallel
For one settlement cycle, enter transactions in both systems. It feels like double work for a few days, but it is the only way to prove the numbers match before anything is switched off. When the stock tally agrees to the carat, you cut over.
What to expect
A typical single-factory migration lands in five to seven working days, including barcode setup and a parallel run. Multi-site rollouts stagger one branch at a time on the same playbook.