Should data lineage be part of a data migration strategy?
With no visibility across data flows to guide the process, migrating from legacy systems to the cloud or adding new data sources to the cloud can become complex. In order to increase visibility and to avoid the dangers of not knowing, lineage automation shows you where data comes from, how it is used, and how it is transformed as it flows between systems.
By mapping the data inventory with lineage, you clarify what is being used and should be migrated and what should be decommissioned
What is a good data migration strategy?
A successful data migration strategy is to divide the system into smaller chunks of objects (reports, tables, workflows, etc.), which poses other challenges—how to migrate one part without breaking another, and how do we even know what pieces can be grouped together to minimize the number of external dependencies? A migration project also represents an opportunity to consolidate or entirely remove components that are no longer in use to avoid migrating worthless data. But even that is tricky, as it requires the ability to view all dependencies in the environment prior to migration. Successful organizations use data lineage to complete their migration projects 40% faster with 30% fewer resources.
Didn’t find the answers you were looking for? Get in touch with us!