Legacy Data Migration
One of the major problems with data migration is handling the functional transfer of data that can be in various conditions. There is the challenge of evaluating the state and condition of the data in the legacy system, for example, looking at whether raw or incomplete data sets will have an adverse effect on migration or use. There is also the essential challenge of figuring out which data sets will have to be migrated — setting aside unnecessary data can decrease costs by quite a bit, but where to cut is the question. Data scientists or planners may need to spend substantial time and effort identifying key data sets to be migrated.
Some of the other challenges include ..
Proprietary Systems (Delta, Adabas to name some)
Nonstandard Tooling (Every developer has his/her own style)
Coding (able to understand how systems were set up)
Finding the right people with the right skills
Educating internal stakeholders to ensure full support for the migration
Managing budget constraints
Completing a migration without disrupting the business
Some of the other issues
A general rule of thumb is that the more outdated the system, the more difficult it will be to migrate or modernize it.
Legacy system migration can temporarily derail business operations. One of the most common migration strategies is the “rip and replace” methodology of entirely ripping out the legacy system and replacing it with the modern system. This can result in a serious loss of operational speed, which can be debilitating for organizations that must pivot quickly, such as in any fast-paced agency environment.
Migration can be expensive in terms of both time and money. Enterprise software is often quite expensive and moving to a new system often results in a brief period of overlapping transactions while you move to production.
Point-to-point integration makes it even more difficult to modernize. If you migrate systems through hand-coded point-to-point integrations, you can quickly find yourself trapped with the same system by a tangled web of brittle application architecture.