To upgrade to TallyPrime 7.2, first identify your installed release and licence entitlement, take and test a separate backup, then choose the appropriate installation and data-migration route. Check reports, customisations and connected services before resuming work. Updating the application and migrating company data are separate steps; neither replaces a recovery plan.
Tally released 7.2 on October 12, 2026. Its purchase-order print templates, GSTR-9 export and extended e-Invoicing sessions may matter to different teams. Check the official 7.2 release notes against the work you actually do. This guide covers the upgrade decision and handover; our TallyPrime 7 feature overview explains the earlier release's features.
Prepare an upgrade assistance brief
Which upgrade route fits your installation?
Start with the product and release shown in F1 (Help) > About, not just the desktop shortcut name. A release update, a Silver-to-Gold edition change and a TSS renewal solve different needs. Use this table to avoid buying or installing the wrong thing.
| Current situation | Plan this route | Check before proceeding |
|---|---|---|
| TallyPrime 3.0 or later | Update the application; migrate company data when required using the current migration workflow. | Confirm the installed product, entitlement, backup and add-on compatibility. |
| Tally.ERP 9 Release 5.0 or later, or TallyPrime 2.1 or earlier | Use the migration instructions for that older data format, rather than assuming the 3.0-or-later steps apply unchanged. | For an existing Tally.ERP 9 licence with active TSS, Tally documents reactivating the existing licence. A new licence is not an automatic requirement. |
| An older Tally release or an uncertain data format | Identify the exact release and follow its specific migration path with a test copy. | Do not point the latest application at the only working copy and assume a direct conversion. |
| Silver to Gold, a different computer, or an expired entitlement | Resolve the edition, activation or TSS question separately from the release update. | Silver to Gold is an edition change. Moving the licence to another system has surrender/reactivation steps; an installer alone does not complete them. |
The official upgrade instructions distinguish product installation, existing-licence reactivation and moving systems. For an edition change, use our Tally upgrade options; for an expiry or entitlement question, request a TSS renewal check. Do not assume an expired subscription makes the existing licence disappear or that installing a file grants a newer licensed release.
What must be ready before you upgrade?
A successful installer is only one part of the job. Agree who owns the backup, test results and final permission to resume entries. Record the following in your upgrade plan, especially when several users share company data.
- Installation inventory: note the current release, TallyPrime or TallyPrime Edit Log product, company count, data paths and client/server arrangement. Check the licensed release and TSS entitlement before scheduling the change.
- A recoverable backup: use the Backup option in your installed release and store the result separately from the working company data. Restore a test backup to a new, empty folder and confirm that the intended company opens in the previous compatible release. Do not overwrite the pre-upgrade copy.
- A report baseline: save dated Trial Balance, Balance Sheet, Profit & Loss, voucher counts and outstanding reports for the same period that you will compare afterwards. Note any existing discrepancies so they are not misdiagnosed as upgrade defects.
- A TDL and integration test copy: list custom TDLs, add-ons, invoice formats, imports and external integrations. Have the developer or provider test the workflows your team uses on the intended release; do not infer compatibility from the age of a TDL alone.
- A cutover owner: agree when entries stop, who tests each workflow and where staff should resume work. Coordinate all relevant workstations with the person managing your shared installation.
Tally's backup and restore guidance warns that replacing data during restoration can delete the existing copy. Use a separate empty restore location when testing recovery. Keep passwords and recovery material private; they do not belong in a support enquiry.
Pause if the test copy exposes a problem
Missing companies, unexplained balances, a failed restore or a custom invoice that no longer prints are reasons to stop the cutover and investigate. A test run establishes the work and time required for your data; this guide does not promise a universal completion time or uninterrupted access.
Update the application or install a separate copy
Tally's current product workflow displays an Upgrade to Latest Release button on the Gateway of Tally and a red dot near F1 (Help) when an update is available. Select the button, follow the on-screen steps and choose Start TallyPrime when complete. Existing licence and configuration details carry forward; follow a reactivation prompt if one appears.
Use the installer when you need a controlled installation
- Obtain the official installer through the existing TallyPrime download page. Confirm whether your business uses TallyPrime or TallyPrime Edit Log before selecting the package.
- For a separate test installation, choose Install New and specify a different application folder. Keep the test data copy separate too; a second application folder does not create a company-data backup.
- To update an existing application with the installer, use O (More Actions) > Select Application from Drive, select the intended application folder, then choose I (Update).
- Start the application and verify the release in F1 (Help) > About. Resolve any licence prompt before assuming the business is ready to resume entries.
If the licence is moving to another computer, follow Tally's surrender and reactivation instructions. If you are upgrading an eligible existing Tally.ERP 9 licence, the official instructions use Reactivate Existing License and selection of that existing licence. Do not buy a replacement serial merely because the application name has changed.
When do you migrate company data?
Use the migration route for the release your data comes from. Tally documents a specific workflow for TallyPrime 3.0 or later company data: F1 (Help) > Troubleshooting > Migrate, or Alt+Y (Data) > Migrate, then select the company.
- Confirm that you selected the intended test or cutover data path and company.
- Set Backup Company Data before Migration to Yes and choose the backup location. Retain the independently tested pre-upgrade backup as well.
- Review the migration screen, then press R (Migrate). Allow the process to finish and review its result and exceptions.
- For Tally.ERP 9 or TallyPrime 2.1-or-earlier data, use the source-version-specific instructions and review migration configurations with the person responsible for your data.
Do not treat instructions for an older release as permission to keep entering data during every migration. Tally's migration FAQ distinguishes older-format migrations from TallyPrime 3.0-or-later migrations, for which users should wait until migration finishes and then work in the latest release. Agree one controlled cutover rather than maintaining competing copies.
What proves the upgrade is ready for daily work?
Compare the same company, reporting period and report settings before and after migration. The checks below are an operational handover checklist, not a guarantee that all data or statutory exceptions have been resolved.
| Check | Evidence to review before sign-off |
|---|---|
| Accounting totals | Compare Trial Balance, Balance Sheet, Profit & Loss and voucher counts against the saved baseline. Investigate unexplained differences. |
| Open business items | Check receivables, payables, stock quantities and representative recent vouchers for the same period. |
| GST and other reports | Review relevant GST reports and migration exceptions with the person who prepares your returns. Resolve differences before relying on an export. |
| Custom daily work | Run important TDLs, an invoice print preview, add-ons and integrations using the test plan. Check company access and user permissions. |
| Connected services and recovery | Verify required access without issuing duplicate statutory documents. Check the new backup schedule and record the agreed working data location. |
Ask the responsible user to sign off on the tested workflows and record any unresolved exceptions. After that handover, direct everyone to the agreed release and company copy. An unexplained difference deserves investigation, not an assumption that the new release will fix it later.
What if migration or a business-critical test fails?
Stop the cutover and preserve the failed test or migrated copy for investigation. Tally's migration FAQ says persistent migration failures may require repair in the previous compatible release before trying again. Do not repeatedly repair the only copy or overwrite the backup. Do not open the migrated data in an older release as a shortcut.
A recovery plan uses the pre-upgrade backup with the previous compatible release, in a separate location, after checking that it opens and the baseline reports agree. If users have recorded transactions after the cutover, identify and reconcile that work before reverting; simply restoring the earlier backup would omit those entries. Agree the recovery decision and data owner before anyone resumes work.
For a failed migration or unexplained report difference, use Tally support assistance. For an add-on or print-format failure, ask your existing developer or our customisation team to assess compatibility. Avoid sharing live company data until an appropriate support process and scope have been agreed.
What should an upgrade assistance request include?
Describe the job so the first conversation can establish the right route. Share your current release and product, intended release, known TSS status, company count, number of workstations, relevant add-ons or TDLs, backup-test status and the exact issue you want help with. Include the preferred cutover window and which reports or workflows need acceptance checks.
Keep the release update, any TSS renewal, edition change and assistance scope separate when requesting a quotation. Do not send passwords, recovery keys or company data through the public form. The form does not transfer this brief automatically; add the relevant details to your message.
Request upgrade assistance or call 022 6199 2222.
Last verified: 30 October 2026. Product steps are checked against the linked TallyHelp sources. Use the instructions for your installed source release and review the current release notes before scheduling a change.




