Signs it is time to move on from Tally
Tally is fast for bookkeeping and familiar to almost every accountant in India. The pressure usually comes from the rest of the business rather than from accounting. If several of the signs below sound familiar, an ERP such as Business Central is worth a serious look.
- Several companies or GST registrations, with consolidation done in spreadsheets.
- Sales, purchasing and warehouse teams working outside the accounting system and re-keying data.
- No reliable approval workflow for purchase orders, payments or credit limits.
- Stock across several locations that is hard to see in one place.
- Management reports assembled by hand every month.
- Integrations with e-commerce, banks or CRM built on exports and imports rather than live connections.
What moves across and what stays behind
Tally and Business Central are built differently. Tally organises everything around ledgers and groups; Business Central separates the general ledger from customers, vendors, items, bank accounts and fixed assets, each with its own records and posting setup. Migration is therefore a mapping exercise, not a copy.
Masters move across after cleansing. That includes the chart of accounts, rebuilt from Tally groups and ledgers; customers and vendors with their GSTINs, PAN and state codes; stock items with HSN codes and units of measure; and fixed assets. Tally can export masters and reports to Excel or XML, which gives you a starting point for mapping.
Transaction history usually stays behind. Most companies bring across monthly balances for the comparison period and keep Tally available, read-only, for look-ups and audit queries. Detailed vouchers rarely justify the migration effort.
Clean up masters before you load them
Years of Tally use tend to leave duplicate parties, ledgers created for one-off transactions and stock items with inconsistent names or units. Moving these across unchanged carries the clutter into the new system and makes reports harder to trust.
Use the migration as a chance to tidy up. Merge duplicates, retire inactive parties and items, check that every customer and vendor has a valid GSTIN and state where one applies, and agree naming rules for items and accounts. Do this in spreadsheets during discovery, so the cleansed files are ready for practice loads into a test company.
Set up GST, TDS and TCS before migrating data
Business Central has a Microsoft India localisation that covers GST, TDS and TCS. Tax setup needs to be in place before masters are loaded, because customer, vendor and item records refer to it.
For GST, that means a registration number for each state where you are registered, assigned to the relevant locations; GST group codes and HSN or SAC codes for goods and services; and the customer and vendor details that decide place of supply and whether reverse charge applies. For TDS and TCS, it means sections, nature of collection codes and the vendor and customer details that drive deductions.
E-invoicing and e-way bills need a separate decision. Business Central's India localisation can prepare the data, but a direct connection to the Invoice Registration Portal and e-way bill system is normally made through a GST Suvidha Provider or a partner app. Choose and test this before go-live, since it affects every outgoing invoice.
Getting opening balances right
Opening balances are where a migration earns or loses the finance team's trust. Close the books in Tally at the cut-over date, then load balances in a way that keeps detail where you need it.
- General ledger: the trial balance at the cut-over date, mapped to the new chart of accounts.
- Customers and vendors: each open invoice and advance loaded individually, not as one balance, so ageing, payments and TDS work from the first day.
- Inventory: quantity and value for each item at each location, reconciled to the stock ledger.
- Fixed assets: acquisition cost and accumulated depreciation for each asset.
- Bank accounts: balances with a list of uncleared cheques and deposits for the first reconciliation.
- GST: balances on input credit and output tax ledgers, so the first return after go-live reconciles.
Running Tally and Business Central in parallel
A parallel run means entering the same transactions in both systems for a period and comparing results. It is the best way to prove that tax calculations, stock valuation and reports are correct before Tally is retired.
Keep the parallel period short and focused. Comparing one month's trial balance, GST liability, TDS deducted and stock value is usually enough to find any setup problems. Running in parallel for months doubles your team's workload and tends to delay the decision rather than improve it. Agree in advance what must match, who signs off and what happens to any differences.
Choosing the cut-over date
The start of the financial year on 1 April is the cleanest date, because the new year opens in Business Central and the old year closes in Tally. It is not essential. A quarter or month start also works well, as long as balances are closed and reconciled at that date.
Avoid dates close to GST return deadlines, TDS quarterly filings, the statutory audit or your busiest trading period. Your finance team will need time to learn new routines during the first close.
Training and the first month-end close
Accountants who know Tally well can find Business Central unfamiliar at first, because entries happen through documents such as sales invoices and purchase orders rather than vouchers alone. Train each role on the tasks it performs, using your own data in a test company, and give people time to practise before go-live.
Plan close support through the first month-end close and the first GST and TDS returns from Business Central. These are the points where questions appear, and fast answers at that stage decide whether the team trusts the new system.