Migration guide · For manufacturers and traders on Tally and Excel
Moving from Tally to ERP: A Step-by-Step Migration Guide
Moving from Tally and Excel to an ERP means migrating your masters, opening balances and open documents — not years of history — on a planned cut-over date, then building what Tally never held: bills of materials, production, quality and multi-location stock. For a mid-size manufacturer, a Pothera ERP implementation including this migration typically takes 8–12 weeks.
Who it is for: This guide is for Indian manufacturers and traders running on Tally and Excel — typically above ₹10 crore turnover and growing — who are deciding whether and how to move to an ERP.
By [Head of Implementation], Bsquare Solutions · Published · Updated · About 10 minutes
Tally isn't the problem — your business has grown past it
Tally is excellent accounting software, and many companies should stay on it. The move to an ERP is about something else: running purchase, stores, production, quality, sales and accounts on one set of data, instead of Tally plus a dozen spreadsheets and WhatsApp groups.
| Today, on Tally + Excel | After moving to an ERP |
|---|---|
| Accounts are in Tally; production plans, BOMs and job work live in spreadsheets | Production, BOMs, job work and accounts in one system |
| Stock is updated when someone posts the voucher | Stock moves with each GRN, issue, production entry and dispatch |
| Costing is done at month-end, if at all | Costing by product, order and customer from live data |
| Sales calls the plant for delivery dates | Sales sees stock and production status |
| Approvals happen on phone and WhatsApp | Approvals and audit trail inside the system |
| Each plant or branch is a separate company or file | Multi-location operations in one system |
Have you outgrown Tally and Excel? Take the 1-minute check
Tick every statement that is true for your business today. Nothing is stored or sent.
What moves from Tally — the data-mapping table
Migrate masters, balances and open documents. Build the operational data Tally never held. Keep past years in Tally for reference and audit.
| In Tally / Excel | Becomes in the ERP | Migrate? | Watch out for |
|---|---|---|---|
| Groups and ledgers | Chart of accounts | Yes | Restructure once; don't carry over unused ledgers |
| Sundry debtors and creditors | Customer and supplier masters with GSTIN, addresses, credit terms | Yes | Duplicate parties, missing GSTINs, multiple ship-to addresses |
| Stock items, units, stock groups | Item master with units, categories and conversion factors | Yes | Duplicate items with slightly different names; units in kg vs pieces |
| Godowns | Warehouses and locations | Yes | Separate rejected, WIP and job-work locations |
| Batches (where used) | Batch / lot records | Yes, for opening stock | Expiry and batch numbers on opening stock |
| Cost centres and categories | Cost centres / departments | Yes | Align with how you want to report plant and department costs |
| HSN/SAC codes and GST rates | Tax settings on items and services | Yes | Verify rates before go-live |
| Trial balance at cut-over | Opening balances | Yes | Must tie to audited or reconciled figures |
| Outstanding bills | Open receivables and payables, bill-wise | Yes | Reconcile party balances before loading |
| Closing stock | Opening stock by item, location and batch | Yes | Physical count or verified stock at cut-over |
| Pending sales and purchase orders | Open sales and purchase orders | Yes | Only genuinely open orders |
| BOMs and routings in Excel | Bills of materials and production routes | Rebuilt | Validate with production before loading |
| Quality checklists on paper | Quality parameters and inspection plans | Rebuilt | Start with the checks customers audit |
| Past years' vouchers | — | Usually no | Keep Tally available read-only for reference and audit |
The migration in seven steps
- Choose the cut-over dateIdeally the start of a financial year, month or quarter — away from peak season and GST deadlines.
- Map processesDecide what moves, what is rebuilt and what stays in Tally for reference.
- Clean mastersRemove duplicate items and parties; fix GSTINs, units and HSN codes.
- Configure and loadSet up the ERP for your processes; load masters through templates.
- Load balancesTrial balance, bill-wise outstanding, opening stock and open orders at cut-over.
- Train and testEach team runs real transactions end to end before go-live.
- Go live and reconcileClose the first month together; compare key reports; fix quickly.
A typical 8–12 week plan
| Weeks | Phase | What happens | Your team's role |
|---|---|---|---|
| 1–2 | Discover | Process mapping across purchase, stores, production, quality, sales and accounts; migration scope agreed | Process owners available for workshops |
| 3–5 | Configure | ERP configured to your processes; masters templates shared | Clean items, parties and BOMs |
| 5–8 | Migrate & test | Masters loaded; test balances; users run real scenarios | Validate data; sign off test results |
| 7–10 | Train | Role-wise training for stores, production, quality, sales and accounts | Every user trained on their own work |
| 8–12 | Go live | Final balances at cut-over; go-live; close support through the first month-end | Reconcile first month-end with the team |
Cut-over checklist
Before cut-over
- Masters cleaned and signed off by each department
- Test run of a full order-to-invoice and purchase-to-payment cycle
- GST settings and invoice formats verified
- Users trained and logins created
- Physical stock count planned for the cut-over date
At and after cut-over
- Trial balance and bill-wise outstanding loaded and tied
- Opening stock loaded by item, location and batch
- Open sales and purchase orders loaded
- Tally closed for new entries; kept read-only for reference
- First month-end reconciled with the implementation team
Six mistakes to avoid
Migrating dirty masters
Duplicates and wrong units move straight into the new system and multiply.
Migrating all history
Years of vouchers add cost and risk; keep them in Tally for reference.
Unreconciled balances
If opening balances don't tie, trust in the ERP is lost in week one.
A long parallel run
Two systems for months doubles the work and delays adoption.
Training only accounts
Stores and production staff make or break data quality.
Copying old spreadsheets
Adopt standard ERP processes; customise only what is truly unique.
Moving from Tally to Pothera ERP
Pothera ERP is built for Indian manufacturers and traders of roughly ₹10–500 crore turnover — many of whom start exactly here, on Tally and Excel. Bsquare's own team plans the migration, configures Pothera ERP for your processes, trains your people and supports you after go-live.
- Production and planning, procurement and MRP, inventory, quality, job work, sales and distribution, and accounts in one system
- GST and e-invoicing ready; complete CRM included
- Cloud or on-premise; typical implementation 8–12 weeks
- 1,000+ clients over 25 years
Tally to ERP migration — frequently asked questions
When should a company move from Tally to an ERP?
Move when your operations have outgrown accounting software: production is planned in spreadsheets, stock differs between stores and accounts, month-end takes days, you run several plants or depots, and owners cannot see margins by product or customer. Tally remains excellent accounting software; the move is about running production, inventory, quality and sales in one system.
What data is migrated from Tally to an ERP?
Typically the chart of accounts and ledgers, customers and suppliers with GST details, stock items and units, godowns as warehouses, cost centres, opening balances, outstanding receivables and payables, open sales and purchase orders, and opening stock with batches where used. Bills of materials, routings and quality parameters are usually built fresh in the ERP because they rarely exist in full in Tally.
Is historical transaction data migrated?
Usually not in full. Most companies migrate masters, opening balances and open documents, and keep Tally data available for reference and audit for past years. Migrating years of transactions adds cost and risk for little benefit.
How long does a Tally to ERP migration take?
It depends on the number of plants, modules and data quality. A Pothera ERP implementation, including migration from Tally and Excel, typically takes 8–12 weeks.
When is the best time to move from Tally to an ERP?
The start of a financial year is the cleanest cut-over because opening balances are audited and reporting is simplest. The start of a month or quarter also works if balances are reconciled at the cut-over date. Avoid peak season and GST return deadlines.
Will GST filing be disrupted during migration?
It should not be, if the cut-over is planned around filing dates. Customer and supplier GST details are migrated with the masters, and the ERP produces GST-compliant invoices and e-invoices from go-live.
Should we run Tally and the ERP in parallel?
A short parallel period of a few weeks for key reports can build confidence, but a long parallel run doubles the work and delays adoption. Most companies test thoroughly before go-live and then reconcile closely in the first month.
Who does the data migration — us or the ERP vendor?
Both. Your team owns data accuracy and decides what moves; the vendor provides templates, loads and validates the data. At Bsquare, the implementation team plans and runs the migration as part of the Pothera ERP project.
What are the biggest risks in moving from Tally?
The biggest risks are duplicate or inconsistent item and party masters, unreconciled opening balances, too little training for stores and production staff, and trying to replicate every old spreadsheet instead of adopting standard ERP processes.
Can small companies move to an ERP from Tally?
Yes, but make sure you need to. Businesses under roughly ₹10 crore with simple buy-and-sell operations may be well served by Tally or a light ERP edition such as Pothera Lite. Pothera ERP is built for manufacturers and traders of roughly ₹10–500 crore turnover.