What happens to years of historical data?

Transactional history usually stays in Tally, which is where auditors expect to find it. Masters — items, parties, price lists, cost centres — are migrated and cleaned, because they are what the new platform actually operates on. Cleaning them is typically the longest task in the project and the one most often underestimated.

How long before we see anything working?

First working module in eight to twelve weeks, in production with real users. Full replacement of the spreadsheet layer takes four to seven months depending on how many units and how deep the customisation runs.

Our Tally is heavily customised with TDL. Does that transfer?

Not directly, and that is usually a gain rather than a loss. TDL customisations are the clearest inventory of what Tally could not do out of the box — we read them as a requirements document for the new platform rather than trying to port them.

Moving off Tally

When Tally stopped being your ERP and became your ledger

Tally is excellent accounting software. It was never meant to run production planning, multi-branch inventory, project costing or a sales pipeline — and the spreadsheets filling those gaps are where the real system now lives.

Talk it through How we engage

The short answer

Move off Tally when the business has outgrown what it records rather than what it computes — when planning, inventory, costing and approvals have migrated into spreadsheets that only two people understand. Keep Tally for statutory accounting and GST if you want; the migration that matters is moving operations onto a platform and integrating back, not replacing your books.

Signals

How you know it is time.

If more than two of these describe your week, the spreadsheets have already become the system.

Month-end takes a week, and most of it is reconciling spreadsheets against Tally rather than closing books.
The real production plan, price list or project cost sheet lives in an Excel file with one owner and no backup.
Branches or units each keep their own Tally company, and the group view is assembled by hand.
You have added the third or fourth Tally add-on and they do not know about each other.
A new hire cannot be told where a number comes from without being walked through a chain of files.

Cost of staying

What it costs to change nothing.

The price of the migration is quoted. This is the price of the alternative, which never is.

The spreadsheet layer is unpriced risk

Every workaround around Tally is software you already own, without tests, access control, audit trail or a second person who understands it. It is not free — it is unbudgeted and uninsured, and it fails on the day the person who wrote it is on leave.

You cannot report on what you never structured

Tally records transactions well. It does not model a work order, a project stage, a dealer scheme or an approval chain — so questions about those cannot be answered from data and get answered from memory.

Integration keeps getting quoted as a project

Every new system — CRM, e-commerce, weighbridge, payroll — needs a Tally bridge built by hand, because there is no platform in the middle. The fourth integration costs as much as the first.

Method

How the migration runs.

01
Map what is actually running
Not the Tally data — the spreadsheets, the add-ons and the WhatsApp approvals. That is the system being replaced, and it is never documented anywhere.
02
Decide what Tally keeps
Usually statutory books and GST filing. Deciding this first turns an all-or-nothing rewrite into a bounded platform build with a defined integration surface.
03
Build operations first, accounting last
The value is in planning, inventory, costing and approvals. Posting to accounts is the easy part and the part with the least upside — so it is sequenced accordingly.
04
Run parallel through one full close
One month-end where both produce the same numbers, reconciled line by line. Nobody signs off a financial system on a demo, and nobody should be asked to.
05
Cut over by unit, not by date
One branch or plant at a time, each with a rollback that works. A big-bang cutover on an ERP is how a quarter gets lost.

How to decide

What makes staying on Tally the right call.

Migrations are expensive to reverse. These are the conditions under which the switching cost outweighs what you would gain.

You are a single unit doing standard trading, and the spreadsheets are three files nobody argues about.
Your process genuinely is standard — a packaged industry ERP will be cheaper and faster than anything custom.
The pain is reporting alone. A data layer over Tally is a fraction of the cost of replacing it.
There is no internal owner for the next twelve months. A platform with no owner decays faster than the spreadsheets did.

Proof

A custom ERP that ended month-end chaos for a steel manufacturer

Replaced five disconnected systems and a wall of spreadsheets with a single custom ERP — order-to-dispatch in one flow, month-end closing down from 9 days to 2.

What does the work

Where this estate is common

Questions

What people ask before starting.

No, and most clients do not. Tally stays for statutory accounting and GST while operations move to the platform, with an integration posting entries across. Replacing your books is a separate decision from fixing your operations, and conflating the two is what makes these projects fail.

Other migrations

Replacing the spreadsheets that run the business SAP ECC: upgrade, replace, or build around Replacing a hospital information system nobody supports

Next step

Thinking about moving off Tally?

Bring the estate as it actually is, spreadsheets included. Forty-five minutes is usually enough to tell you whether it is worth doing and roughly what it would take.

Book a discovery call Send a brief instead

No sales deck
An engineer on the call, not an account manager
NDA before you share anything