TallyPrime 7.2 Upgrade & Update from 7.1: Safe Checklist 2026

A client calls on a Monday morning. Their accountant clicked the upgrade prompt on Friday, and now three companies show Migration Required. Nobody took a backup. The upgrade itself is rarely the problem. The fifteen minutes skipped before it usually is, and that is what this checklist covers for anyone moving from TallyPrime 7.1 to 7.2.

What is the TallyPrime 7.2 upgrade?

TallyPrime 7.2 is the release that follows 7.1, the version most offices run as of 20 October 2026. Release demonstrations focus on GSTR-9 data export, e-invoice and e-way bill sessions, and print templates. Treat those as reported features until you have checked them on your own build. The upgrade replaces the program files. Your company data stays where it is, but it may need migrating to a newer data format.

How to Upgrade from TallyPrime 7.1 to 7.2 — Step by Step

1. Confirm your release and TSS status. Press F1 (Help) > About. Note the release number (it should read 7.1) and the TSS expiry date. If TSS has lapsed, the upgrade will not go through on a licensed copy. Renew it first, before you start anything else.
2. Record where your data actually lives. Press F3 to open Select Company and note the data folder location shown for each company. Tally tip: many offices have two data paths, one on a shared drive and one on the local machine. People back up one of them and forget the other.
3. Back up every company. Go to Alt+Y (Data) > Backup, select all companies, and set the destination to a folder or external drive outside the Tally data path. A backup saved inside the data folder is lost along with everything else if that drive fails mid-upgrade.
4. Run a repair on any company that has shown errors. Use Alt+Y (Data) > Repair on a company that has thrown memory-access or voucher-corruption messages in 7.1. Tally tip: it is better to find corruption now, while you still have a working 7.1, than after a migration has failed.
5. Upgrade the licensed copy. Press F1 (Help) > Upgrade, choose to upgrade now, and allow the permission prompts. TallyPrime restarts on the new release. Then go back to F1 (Help) > About and confirm the release number has changed.
6. Open each company and handle migration. In Select Company (F3), any company marked Migration Required needs to be migrated before it will open. Migrate one smaller company first. Then check its Balance Sheet and Trial Balance against the figures you noted in 7.1 before you migrate the rest.
7. Spot-check before going live. Compare closing balances, the GST registration details on one sales voucher, and one printed invoice against 7.1 output. If anything differs, stop. Restore from the backup taken in step 3 rather than correcting the migrated data by hand.

Mistakes That Cost Indian CAs Hours

• Upgrading during filing week. If a migration stalls on the 19th, GSTR-3B is due on the 20th and you have no working books. Fix: upgrade in the first week after filing, never in the window before the 20th, and never close to the 31 December GSTR-9 due date.
• Upgrading only one machine in a multi-user office. If one system is on 7.2 and the others are still on 7.1, users on the old release may not be able to open migrated data. Fix: upgrade every machine that opens the same data on the same day, starting with the server or the system that hosts the data.
• Trusting a single backup that was never tested. A backup file that will not restore is not a backup. Fix: restore one company through Alt+Y (Data) > Restore into a separate test folder, and open it there before you upgrade anything.
• Migrating every company in one go. When the 40th company fails, you will not know which earlier ones are sound. Fix: migrate one company, verify its Trial Balance, then batch the rest. Keep a simple list of which companies are done.
• Assuming the TallyPrime upgrade also covers Tally ERP 9 data. It does not. ERP 9 companies need migration into TallyPrime, and the ERP 9 folder should be left untouched. Fix: copy the ERP 9 data folder first, migrate the copy, and keep the original read-only for at least one audit cycle.

Pro Tips for 2026

Keep 7.1 on standby if you want to evaluate 7.2 before committing. The setup file offers a new installation in a separate folder, so you can name it something like TallyPrime72 and point it at a restored copy of one company, not your live data. Note the closing balances of your three largest clients before the upgrade. A two-minute comparison afterwards will catch anything a migration got wrong. Finally, leave the year-end GSTR-9 features for later. Test any new GSTR-9 export on last year's filed return first. If the export reproduces figures you already filed, you can trust it for FY 2025-26.