Add to Favourites

Migrate Company Data

Migrating your company data to the latest release of TallyPrime is seamless. Being on the latest release of TallyPrime enables you to use a host of features, like enhanced experience of defining GST Rates at different levels, creating multiple GST registrations for your company, handling data exceptions, and so on. Whether you want to migrate your company data from TallyPrime releases (such as TallyPrime 2.1 or earlier), Tally.ERP 9 releases, or Tally releases to TallyPrime Release 3.0 or later, all your transactions, along with your company features, masters, security settings, and so on, will be carried forward seamlessly. When you migrate to the latest release of TallyPrime:

• Your company data is seamlessly moved to the latest release of TallyPrime, while keeping a copy of the data of your earlier release safe.
• After migration, the company is available with a 6-digit Company Number.
• A summary of the migration is displayed with before and after migration statistics, as all the masters and vouchers are safely migrated with or without any data exception.

In case you are using TDL customisations, contact your Partner to understand its compatibility with TallyPrime Release 3.0.

Recommendations for Data Migration

To facilitate the slew of new features in TallyPrime Release 3.0 like faster GST reports, revamped GST Reconciliation, Multi-GSTIN companies and so on, we have made a few changes to the way the data will be migrated. Migration to Release 3.0 will result in creation of a new 6-digit company that is compatible with the latest release of TallyPrime. However, because of this change, the migrated data might take up a slightly larger disk space than your existing 5-digit company data. 

Moreover, the time taken for migrating the company data depends on various factors, such as number of vouchers and masters, the RAM capacity, other applications running simultaneously during migration, and so on. The following is an estimation of the migration time per voucher. This is compiled based on our observations in performing migration of different company data of India-based businesses, which have GST feature enabled.

You can use this estimation to calculate the approximate time that TallyPrime will take for migrating the company data. For example, if you have 1,00,000 vouchers, in the best scenario, migrating the vouchers will take approximately (0.00167 x 100000) 167 minutes.

The migration performance for International companies and companies where GST is disabled, are expected to be better than the figures above.

Considering the different scenarios such as volume of data and time for migration, and to avoid any interruptions in your business operations, refer to the following recommendations.

Recommendations before migration

Migrating the company data to TallyPrime Release 3.0 might take time depending on your data size.

RAM Capacity

For a seamless migration, ensure there is minimum 4-GB RAM in your computer.
There can be a performance boost while using a computer with a higher RAM capacity and a hard disk that uses an SSD storage.

We have performed migration performance testing on different Company datasets successfully in an environment with the following system configuration

• Intel(R) Core(TM) i5 / 4.0 GB RAM / Windows 7 (64-bit OS) with HDD storage.
• A company with the maximum of 2.5 lakh vouchers and 1 lakh masters have been tested successfully in this configuration.

Disk Space

During migration, in case the application encounters less space for the data, you will be prompted about the low disk space for migration. Ensure to free up disk space accordingly and migrate.
If you are using Group Companies, note that you will need to have sufficient free disk space available, migrating multiple member companies in a single action will require good amount of space.

Other recommendations

1. Verify the Company GST details: Ensure that the GSTIN, State, and Registration type are correct in the F11 (Features) of the source company.
2. Take a backup of the data: Before migration, it is highly recommended to take a back up of the company data.
3. Split Company Data: If you have large volume of data – more than 1 lakh transactions per year across multiple financial years, split the data.
   1. Split the parent company (for example P1) into two:
      • Company for the current financial period where you need to continue data entry (for example, C1).
      • Company for the previous financial years, for which you have closed the books of account (for example, C2).
   2. Migrate the data of C1 to TallyPrime Release 3.0 and continue to record your transactions as usual.
      • You can consider migrating the parent company (P1) at a later stage, as per your convenience.
4. Migrate during non-working hours or over the weekends: This helps eliminate any disruptions to your business operations during the working hours as migration may slow down other applications depending on the data size.
5. Close other applications if not needed at that point to optimise system resources

Recommendations during migration

If you need to record transactions during migration

Migration of the company data to TallyPrime Release 3.0 might take time. Meanwhile, you may want to continue your business operations using the backed up data. Such transactions can be easily imported to the migrated data. To know more, refer to the Import masters and transactions section.

1. Avoid making changes to the existing transactions. In case you must make changes, keep a note of the changes so that you can easily identify such transactions, import them post migration and verify.
   • Importing the vouchers or masters will not import the corresponding Edit Log information.
   • Some of the imported vouchers might move into Uncertain transactions category, which will import the GST reports. Press Alt+G (Go To) > GSTR-1/GSTR-3B/CMP-08/GSTR-4 > Uncertain Transactions, and resolve any uncertain transactions before starting to work on the migrated company data.
2. Avoid creating or altering any masters and deleting or marking any voucher as Optional in the data that you are migrating. Such changes will need to be done separately again in the latest release. 
3. If you have created new vouchers in the backed up company, ensure to keep a track of the voucher numbers, so that you can validate them after importing to the latest release.

During migration, you will not be able to make any changes to the data in migration, as you will not be able to open the company being migrated. 

If you are using TallyPrime on AWS, click here.

If you are accessing data in a LAN environment, click here.

If you are using TallyPrime Server, click here.

Recommendations after data migration

TallyPrime ensure to take care of your business data in the best possible way after migration. To make your after migration experience smooth and simple, we recommend the following:

Licensing

1. Access company data seamlessly with your existing license.
   Have a hassle-free experience of using the latest TallyPrime Release 3.0 with your existing license.

Handle exceptions and differences in data

If you data had any aberrations in the previous release, there might be some data loss. Therefore:

1. Verify and compare the statistics of Company Data before and after migration.
   In case there is any difference, repair the data in the latest release to validate if any data was lost due to data corruption. 
2. Validate your edit log information: All the company data, including edit log, will be migrated to TallyPrime Release 3.0. However, in case you notice any inconsistencies in the data from the financial reports or statistics report, it is possible that the inconsistencies were due to certain company-level configurations. To know more, refer to Impact of migration on Edit Log.
   Repair your 5-digit company data prior to migration and ensure that such inconsistencies do not exist.
3. Validate differences in data before migration and after migration: Refer to Data exceptions found during migration.
   In case any of your data is under exceptions, refer to Data Exceptions in TallyPrime.

Import transactions and masters

In case you have created any data in the backed up company, during the migration process:

Step 1: Identify the newly created transactions. Click here.

Step 2: Export the newly added transactions. Click here.

Step 3: Import the transactions back to the company in TallyPrime Release 3.0. Click here.

It is recommended to import the transactions/masters before you start using the migrated data in TallyPrime Release 3.0, to ensure that the vouchers numbers are intact as expected.

Downgrade from TallyPrime. 4.0 to TallyPrime 3.0.1 through to TallyPrime 2.0

If you are downgrading from Release 4.0, and then need to view the saved views of your reports

• Copy the folder from config > reportviews to ReportViews under the TallyPrime installation folder.

Migrate Company Data to the Latest Release of TallyPrime

Migration of your company data involves a few simple steps. TallyPrime ensures that the migration is smooth without any data loss. Whether you have one company or multiple companies, you can migrate all of them as per your business needs. In TallyPrime, you can migrate a company by selecting a company from the earlier TallyPrime release or use the migrate feature from F1 (Help) or Alt+Y (Data) and select the company to migrate.

If you are migrating the company data from TallyPrime Release 2.1 or earlier, TallyPrime migrates the data to a new company with a 6-digit Company Number. A copy of the company with 5-digit Company Number from the previous release is retained as is in case you need to use the data in the previous release of TallyPrime.  

In this section

• Migrate data to latest TallyPrime release
• Outcome of migration – Statistics & Company Data
• Impact of migration on Edit Log
• Migrate damaged data from earlier release to latest TallyPrime release

Migrate data to the latest TallyPrime release 

Migrating your company data from a 5-digit company will recreate the company data with a 6-digit company. At the same time, the process will retain the existing 5-digit company data. You can continue to use the company data same in their respective releases.        

1. Press F1 (Help) > Troubleshooting > Migrate > select a company.
   Alternatively, press Alt+Y (Data) > Migrate > select a company.
   

   You can also press F3 (Company) and select the company showing Migration Required status.

   

2. Configure for backup and difference in tax values, if needed. 
   1. Set Backup Company Data before Migration to Yes.
      It is recommended to backup the company before you migrate.
   2. Backup Destination Path: Select a path where the backed up data should be stored.
   3. Ignore difference in tax value up to: This value ensures that your transactions are appropriately included in the GST Returns post migration.
      This is a one-time change while migrating from Release 2.1 to Release 3.0 and later. Retaining this field as is during migration might move your transaction into Uncertain category in your Returns. After migration, you can set the difference in tax value value from F11 (Company Features). This configuration is applicable only if you had:
      
      • Set the country for your Company as India
      • Enabled GST for the Company
3. Press M (Migrate) to migrate the data.
   
   Migration may take a while, according to the size of your company data. 

Once you migrate to TallyPrime Release 3.0, a copy of the 5-digit company is retained and renamed to a folder. For example, if you migrate the company 10000, the company is retained as a folder and renamed to 10000-migrated-to-3.0. The new company after migration is renumbered as 010000. 

The company data in the latest release of TallyPrime will be available as a 6-digit company number. For your easy reference the, the company number of the source data is prefixed with a zero (0) so that you can easily identify which company was migrated. In addition, the 5-digit source company is retained in the same data location and renamed as a folder.

For example, if you migrate the company National Enterprises (10000) to TallyPrime Release 3.0, the migrated company data is numbered as National Enterprises (010000), and the source company is retained but renamed as ‘10000-migrated-to-3.0’. 

Renaming the source company helps in identifying the the company data has already been migrated. The renaming will occur only when the source company is closed or shut in the earlier release of TallyPrime while you migrate the company data.      

Low disk space during migration and backup

To successfully migrate the company data and to take a backup of the data, you need to have the recommended disk space in your computer. If there is low disk space that is not sufficient either for migration or backup, TallyPrime prompts you with the corresponding information:

If you still attempt to migrate or backup, TallyPrime displays the following error message:

Ensure to free up the disk space in your computer and then migrate the company data.

Outcome of migration – Statistics & Company Data

• Statistics: On migrating the data, TallyPrime displays the count of masters and vouchers before and after migration. This helps you to ensure that your data is intact and migrated without any data loss. For detailed information, refer to the <Statistics> section.    
• Company Number: Migrating data from a previous TallyPrime release will update the Company Number from 5 digits to 6 digits. A copy of the 5-digit data from the previous version is retained. 
  If you are migrating data from the earlier versions to Release 2.1, there is no change in the Company Number.
• GST Registration master: A separate GST Registration master applicable from this release is added to the Total Masters count after migrating the Company Data, to support multiple GSTINs/UINs.
• Voucher numbering:  For voucher types with Automatic or Multi-user (Auto) numbering method, the option Numbering behaviour on insertion/deletion is set to Retain Original Voucher No. You can change it to Renumber Vouchers, if needed, by altering the relevant voucher types.
  If you are migrating data from earlier versions to Release 2.1, with EL enabled, the voucher numbering is updated from Automatic to Automatic (Manual Override). 

Impact of migration on Edit Log

• If you are migrating data to an Edit Log version,
  • TallyPrime will start creating an Edit Log for transactions, stock items, ledgers, and accounting groups for all activities.
  • Data Migration gets recorded as an activity in the Edit Log of the Company. To know more about this, refer to Activities Affecting Edit Log.
  • Updates in voucher numbering option leads to creation of Edit Log for subsequent vouchers whenever you add, insert, duplicate, or delete a voucher. 
• If you have migrated data from an Edit Log version of TallyPrime, the edit logs will continue to be available in the latest TallyPrime release.

The impact on Edit Log will depend on the version your data belonged to and the version that you are migrating to.

Migrate damaged data from an earlier release to the latest TallyPrime release

If your company data is damaged or corrupt while using in the earlier release, and you want to attempt using the same data now in the latest release, TallyPrime makes it hassle-free for you. You can migrate the damaged data to the latest release where migration will first attempt to recover the damaged data and then migrates all the data successfully. However, if any data is damaged beyond recovery, TallyPrime does not migrate such data. 

Once migration is complete, TallyPrime displays the result of the migrated data in a summary report. Depending on the level of damage in your data, the report displays the number of vouchers and masters before and after migration.
If you are on Release 2.1 or earlier, this is not applicable. In this case, after a successful migration, TallyPrime directly opens the company. 

If you are on TallyPrime Release 2.1 and migrating your Company Data from any of the earlier TallyPrime releases, click here.

Statistics of Company Data after Migration | Summary of Migrated Data

Once you have migrated the company data to Release 3.0 or later, TallyPrime displays the statistics of the voucher and master count before and after migration. This enables you verify the results of migration and take necessary actions on your data, if any, before you start using it.

If you have migrated data that was already corrupt in your previous release, any damaged data that could not be recovered is not considered for migration and therefore not included in the summary report post migration. 

Once the migration is complete, you will see the following details on the migration summary screen. 

• If your company was GST-enabled, you will find difference in the number of masters created after migration as GST Registration appears as a separate master. In TallyPrime Release 3.0 and later, you can use the GST Registration master to create multiple registrations for the company, if needed.
• If your existing data has certain settings/configurations that could not be migrated as is, <or any other reason>, nothing to worry! The data still gets migrated. The Statistics report shows the number of masters and vouchers successfully migrated. Vouchers or masters that had exceptions are moved to the Exceptions report, which you can resolve anytime in just a few steps. Refer to the Data Exceptions & Resolutions topic for more information. 

• Your company data is available as a 6-digit Company Number.

If you are using Release 2.1 or earlier, you will not see any summary report. On successful migration, you can continue to use the migrated data as usual. If migration gets completed with exceptions in data, you will need to repair your company data in the earlier release and migrate again. 

In this section

• View Statistics post migration
• Data exceptions caused in migration

View Statistics post migration

On successful migration, the following Statistics report is displayed and your company data is ready for use.

During migration, if TallyPrime identifies any exception in your data, on completion of migration the following screen appears:

You can resolve the exceptions easily. In the Summary screen, press Alt+X (Repair/Migrate Exception).

Refer to the Data Exceptions & Resolutions topic for more information. 

• In case of migration with exception, all the previous Edit Log data, if any, gets migrated. However, any existing edit logs for the masters and vouchers that are in exception gets removed.
• Data Path: Displays the path or folder where the migrated company data is located.
• Backup Destination Path
  • If you had set Backup Company Data before Migrate to Yes, on the summary report Backup Destination Path displays the folder location where the backup of your earlier data was taken.
  • If the option was set to No. this label does not appear on the summary report post migration.
• Statistics: The table displays the count of total masters and vouchers before and after the migration process. This count includes all the data that was eligible for migration, including optional vouchers, cancelled vouchers, and so on.  
  • On successful migration, the count before migration matches the count after migration. In TallyPrime Release 3.0, GST Tax Registration is a separate master available to create multiple registrations (multi-GSTIN), if needed. Therefore, if you had enabled GST in the company data before migration, an additional master with the registration details is added to the total count of masters.
    Press Alt+F5 to view the Statistics in detailed format.
  • If migration is completed with exceptions, you will see a mismatch in the count of masters or vouchers or both. The report by default appears in detailed mode displaying the comparison for each master type and voucher type.
    Press Alt+F5 to view the Statistics in condensed format.
• Updates in Company Data: This section lists the necessary changes made in the company data due to migration to ensure that your data is compatible with the latest version. These updates are displayed based on the TallyPrime release your data belonged to and the preferences and settings you had done. 

Data exceptions found during migration

TallyPrime ensures that all your data is migrated safely to the latest release. However, depending on your data and settings for your company and transactions, you may encounter certain exceptions and mismatches.

In this section

• Vouchers and masters with exceptions
• Mismatch in count of masters and vouchers
• Mismatch in voucher and master details before and after migration

Vouchers and masters with exceptions 

While migrating the data, any data (vouchers and masters) that is found to have an exception is moved into an exception report. TallyPrime allows you to view all those exceptions and resolve them, as appropriate.

1. From the Summary report after migration, press Alt+X (Migrate/Repair).
   The Migrate/Repair Exceptions report appears.
2. Drill down from the exceptions to view further details and resolve them, as needed.

 In case you have closed the Summary report after migration, you can still open the report.

1. Select F1 (Help) > Troubleshooting > Migrate/Repair Exceptions. 
   Alternatively, Alt+Y (Data) > All Exceptions > Migrate/Repair Exceptions.
   The Migrate/Repair Exceptions report appears. 
2. Drill down from the exceptions to view further details and resolve them, as needed.

For more information, refer to the Data Exceptions & Resolutions topic.

If you are on the TallyPrime 2.1 or earlier, this is not applicable.

Mismatch in count of masters and vouchers

You may experience a successful migration where the Summary report displays equal count of masters and vouchers post migration. However, the Statistics report might display a different count of masters and vouchers compared with the post-migration Summary report.

1. From the Statistics report, identify the group in which the masters or voucher count is different.
2. Open Day Book or Chart of Accounts and attempt to open the identified masters or vouchers. 
   It is possible that you are not able to open them or the data is damaged.
3. If you identify any damaged transaction or master, repair the data in the release from where the company data has been migrated.
4. After a successful repair, migrate the data to the latest release of TallyPrime.

Mismatch in voucher and master details before and after migration

After migration, you may notice that that details entered in certain vouchers or masters before migration are different after migration. You may observe the following mismatches:

• Mismatch due to a change in the master configuration after recording the transactions.
• Transactions are migrated successfully but some information that was not available earlier in the master/transaction has got added.
• Transactions are migrated successfully but some information that was available in the transaction is dropped.

Causes of mismatch

• If you have recorded any transactions using stock items and later enabled one or more of the following configuration in the stock items.
  • Treat all purchases as consumed.
  • Treat all rejections inward as scrap.
  • Treat all sales as newly manufactured.
• If you have recorded any transactions and later altered the related ledger appropriation configurations, such as Appropriate tax values in Purchase invoice, Method of appropriation to Allocate Additional Costs, and so on.
• Difference in Balance Sheet: Current Assets and Stock Summary values, before and after migration. This happens in companies where:
  • Godown is enabled 
  • A particular step is followed to record stock journal transaction
  • Data is split
  • Data is migrated after split
• Pending bills in the Outstanding report that were available in the source data are not shown in the migrated data.
• Payroll vouchers in Bank Reconciliation report that were available in the source data are not shown in the migrated data.
• Purchase Order/Sales Order link object that was not available in the source data is shown in the migrated data.

Solution

In all the above-mentioned cases, you can do the following:

1. Repair the data in the release from where the data has been migrated.
2. On successful repair, compare the data of Balance Sheet and Trial Balance between the source data and the migrated data.

Additionally, a mismatch may occur when TallyPrime displays any Inventory/Accounting allocations in a voucher in the migrated data. In this case:

• In the 5-digit company data, verify Day Book, Balance Sheet, and Trial Balance to see if you see any difference in the values compared to same reports in the migrated data. This will help you identify the vouchers that are causing the mismatch.
• Reaccept any vouchers that you had opened to verify.
• Again compare the Balance Sheet and Trial Balance between the earlier-version data and the migrated data.

Migrate Company Data from Tally 5.4, 6.3 and 7.2 to TallyPrime

The latest release of TallyPrime can detect if your data is from earlier releases (such as Tally 9 to Tally.ERP 9), and guide you in the migration process. All your transactions, along with your company features, masters, security settings, and so on, will be carried forward seamlessly. Migrating the Tally 5.4, 6.3, and 7.2 data to the latest TallyPrime release is a 2-step process.

In this section

• Migrate from Tally 5.4, 6.3 and 7.2 to Tally.ERP 9 
• Migrate from Tally.ERP 9 to the Latest TallyPrime Release

Step 1: Migrate from Tally 5.4, 6.3 and 7.2 to Tally.ERP 9 

If you are using older releases of Tally (such as 5.4, 6.3, and 7.2), you cannot migrate your data directly to TallyPrime. You will have to first migrate your data to Tally.ERP 9, and then migrate to TallyPrime.

To migrate data from releases below Tally.ERP 9, you need the migration tool tally72migration.exe that is available in Tally.ERP 9 installation folder. Before migrating data, it is recommended that you backup your data.

1. Copy the company data of Tally 5.4, 6.3, or 7.2 to the data folder in Tally.ERP 9.
2. Start the migration tool (tally72migration.exe) from the location where it is available.
3. Select Migrate Data in the ERP 9 Data Migration Tool screen as shown below:
   
4. Enter the company data path in the Directory field and select the company in the Name field.
5. Press Enter when the Rewrite? message appears, and press Enter when the message Backup before rewriting? appears. The data is backed up before being rewritten to Tally 7.2 format for migration.
6. Press Enter when the Migrate? message appears.
   On successful migration, the message Migration Completed, Check Statistics appears. Compare the statistics and ensure that data migration is complete.

   The migrated company number is prefixed with an additional 0 and appears in five digits. When you open the data in the latest release, you will be will prompted to migrate to Release 6.x. Press Enter to migrate.

Step 2: Migrate from Tally.ERP 9 to the Latest TallyPrime Release

Once you have migrated your company data to Tally.ERP 9, now migrating from Tally.ERP 9 to the latest release of TallyPrime is seamless. Refer to Migrate Company Data to the Latest Release of TallyPrime.

Migrating your company data to the latest release of TallyPrime provides you the flexibility to use the latest features seamlessly. Migration helps in making your old data compatible with the latest release, so that you can continue to work on your data without any hassles. For more information on the Release Highlights and Feature enhancements, refer to Release Notes for TallyPrime Release 3.0.