Migration is the one step in the 6.1 to 7.0 update that cannot be undone. Understanding it takes five minutes and removes every surprise from update day.
Every TallyPrime release keeps its company data in its own format. When 7.0 first opens a company last used in 6.1, it offers to migrate — convert — that data. People fear this step for the wrong reasons and ignore it for the wrong ones. Here is what Tally itself documents about migration, in plain words.
This company was created in an earlier release of TallyPrime.
Migration will make the data ready for Release 7.0.
Backup before migrate? — Yes (always).
Answer Yes to both questions. The backup TallyPrime takes here is in addition to your own pre-update backup, not a replacement for it. Prompt recreated.
Migration rewrites the company's stored data so the new release can read and write it. Your masters, vouchers and balances are carried across — nothing about your accounting changes. What changes is the file format underneath, and formats are not shared between releases. That is why the step deserves respect: it is quick, automatic, and permanent.
Tally's official help on data migration states it plainly: once the migration of a company is complete, the data becomes compatible only with the latest release. If someone then opens that company in the earlier release and tries to save a transaction, TallyPrime shows an error and closes the application, to protect the data from inconsistency.
In office language: after migration day, 6.1 is finished for that company. Old shortcuts, the old folder on a client's desktop, a forgotten second installation — none of them can be used for that company any more.
Tally's help specifically warns against performing these while a migration is in progress, because they can cause errors or data corruption:
And a third rule from plain experience: do not force-close TallyPrime, switch off the PC, or let a laptop sleep in the middle of it. Plug the machine in, and let the progress finish.
Power cuts do not read instructions. If migration stops halfway, the company is not destroyed: the next time you select it, TallyPrime shows it with a Continue Migration status. Select it, confirm, and the migration resumes from where it stopped. If it repeatedly fails on the same company, stop retrying, restore your pre-update backup into a separate folder, and take help from your Tally partner — repeated forced attempts help nobody.
Migration happens per company, the first time that company is opened in 7.0. The company you open once a quarter for an old assessment will simply migrate on that day instead — which is fine, as long as its pre-update backup exists and nobody opens it in 6.1 afterwards. On update day itself, deliberately open each main company once, migrate it, and compare its trial balance with your written notes. That turns five future surprises into one finished job.
The complete TallyPrime 6.1 to 7.0 update, done live on screen — backup, installation, migration and licence check included.
▶️ Watch Full VideoNo. Migration converts the storage format of the company, not its contents. Masters, vouchers and balances carry across as they were — which is why comparing the trial balance before and after is a valid and worthwhile check.
Each company migrates the first time 7.0 opens it, and after that it belongs to 7.0. A company you never open in 7.0 stays in the old format. In practice, running two releases side by side in one office causes mistakes, so most offices migrate every active company in one planned window.
Stop and do not keep forcing it. Restore your pre-update backup to a separate location and get your Tally partner or Tally support involved — a company that refuses migration may have an underlying data problem that should be repaired in the old release first, calmly, on a copy.