Data Migration

Why at HAL we avoid line level data migration from the legacy system?

1. We are dealing with two different systems with different formats. When compared to master data remigration the line level data like journal entries will have multiple lines of credit an debit making the data extraction, cleaning and migration to the new format of the current system very expensive.

2. The closing balances of the current date are going to be imported into the system, hence this will be more than sufficient to start daily operations. This even guarantees you accurate year-end balances.

3. Older transactions can always be referred back by exporting from the old system in an excel sheet or use the older system as such. Most Companies follow this process and within 2 months, the need to even go to the old system becomes rare.

4. Starting the new system with a closed balance sheet inevitably means the old have been verified into closing balances

5. The Hal ERP follows the IFRS standards for Chart of accounts and aims to minimize the number of ledgers required. This means there are no separate ledgers for students, employee, vendors and customers. These transaction and reports are handled in their own specific modules. If in the current system there are separate ledgers for these then migrating them will create duplicate entries and lot of confusion in future.

6. The current project scope cost doesn't include the line level data migration.