Post-Migration Activities
After completing data migration, you can do the following before you start using TallyPrime to record your day-to-day transactions.
Verify Company data
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.
To Verify and compare company data statistics before and after migration,
-
From the Statistics report, identify the group in which the masters or voucher count is different.
-
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.
If you identify any damaged transaction or master, repair the data in the release from where the company data has been migrated and then try to migrate the data again.
Validate Edit Log information
- 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.
- 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 from… |
Migrate to… |
Impact on Edit Log |
|
TallyPrime 2.1 – Edit Log disabled |
TallyPrime 3.0 |
|
|
TallyPrime 2.1 – Edit Log enabled |
TallyPrime 3.0 |
|
|
TallyPrime Edit Log 2.1 |
TallyPrime Edit Log 3.0 |
|
|
TallyPrime 3.0 – Edit Log enabled or disabled |
TallyPrime Edit Log 3.0 or later |
|
|
TallyPrime Edit Log 3.0 |
TallyPrime 3.0 or later |
|
|
TallyPrime 2.0 or earlier |
TallyPrime 3.0 or later |
|
|
TallyPrime 2.0 or earlier |
TallyPrime Edit Log 3.0 or later |
|
Resolve Exceptions after Migration
While migrating the data, any data (vouchers and masters) that is found to have an exception is moved into an Exception report.
After migration, you may observe a mismatch in vouchers and masters 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.
In the Summary screen, press Alt+X (Repair/Migrate Exception) to view the Exceptions report and resolve the exceptions easily.
By default, the Exception report displays all the errors Exception-wise under two categories, Master-Related Exceptions and Voucher-Related Exceptions. TallyPrime allows you to view all those exceptions and resolve them, as appropriate.
To know more, refer to the Data Exceptions & Resolutions.
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.
- Using TallyPrime 2.1 or earlier, open Day Book in the backed up company data.
- Press F2 and select a date or period, if you have created the new transactions on a specific date or period.
- Press Alt+F12 (Range) > Voucher Type > enter Voucher number > starting with > enter the starting digit of the voucher number > and press Enter.
The Day Book displays the newly added transactions based on the condition that you have entered for filtering. Similarly, you can also import the masters created in the backed up data. For more information, refer to Import Data.
Step 2: Export the newly added transactions. Click here.
- Press Ctrl+E (Export) > Configure.
- File Format: set as XML (Data Interchange).
- Set Include dependent masters as No, and press Ctrl+A to save the configurations.
- Select Export and press Enter.
This exports all the delta transactions as XML files. Note that depending on the filter option, you might have to export multiple XML files.
Step 3: Import the transactions back to the company in TallyPrime Release 3.0. Click here.
- Open the newly migrated 6-digit company (100000) in TallyPrime Release 3.0.
- Press Alt+O (Import) > Transactions, and select the XML file that you have exported earlier.
- Once you have imported the XML file, you will need to validate and resolve any uncertain transactions or exceptions.
- Press Alt+G (Go To) > type or enter GSTR-1/GSTR-3B > Uncertain Transactions.
If there are any uncertain transactions, update them with the appropriate details. - Press Alt+O (Import) > Exceptions.
If there are any exceptions in the transactions, drill-down and resolve the data exceptions.
It is recommended to import the transactions/masters before you start using the migrated data, to ensure that the vouchers numbers are intact as expected.
