Data migration is a high-risk area in a legacy core systems migration. Prior, relevant expertise is essential. Older systems have cryptic, difficult-to-understand data representation under the covers. Data may not be normalized or in some cases it may be over normalized. Typically, this leads to significant challenges if a decision is made to automate data migration. Automated data migration is very prone to schedule slippage. The simple fact is that the state of data in legacy core systems is usually poor. While this may be an oversimplification, it is largely true. We recommend our customers perform cost benefit analysis for any automated data migration. Unless there’s an overriding reason for an automated data migration, we recommend using a combination of manual and automated processes to migrate to a new platform. For example, running off policies and billing on a legacy system and renewing policies on the new platform may be far more effective than attempting to automate migration. Historical policy and billing data may be brought across electronically in a read-only, non-transactable state. Similarly, claims may be moved using a combination of automated and manual processes. If you do decide to perform an automated data migration, here are some broad steps from our methodology that may be used: