Earlier this year we may the modernise our bathrooms – which dated back to when the house was built sometime in the 1960’s.
In many ways the bathrooms were functional – but with dated decor and some layout issues it was time.
As we began planning we received a sound piece advice from the plumber. “Never lay new tiles over old pipes.”
With the original galvanised pipes over 60 years old it was surprising how good their condition was. Yet, as we dug them out we found at least one slow leak, and a number of areas where a burst pipe was imminent. Now, we have shiny new copper piping and can rest assured that our investment in the new tiles and sanitaryware is protected.
How many of us modernise our systems without resolving underlying data issues?
Poor quality data can be seen as the leaky, corroded pipes sitting in the new application, waiting to burst.
A data migration approach that does not address underlying data quality issues is like setting up a new bath room without addressing the plumbing issues. In many cases, the issues that may have lead to the system replacement may be migrated with the bad data into the new system.
Don’t introduce problems
In practise, the activities of demolition and remodelling can create leaks in pipes that may not have existed previously. The bumps, knocks and vibrations can loosen seams or break pipes.
Similarly, migrating data to a new structure can introduce data issues that maynot have existed (or been substantial) in the source. New data types, consolidations of reference data, and new data structures can all create risks that must be addressed during the migration in order to prevent down stream issues.
Are you planning a system migration?
Chat to us to understand how to address data quality issues as part of your migration, and keep data clean going forward.