Over the years, I’ve collected up some pretty gnarly tales of data migrations. But the really great part is what they do to handle the gnarly migrations.
That’s what I love, anyway. Here are a few of my favorite examples:
Worcestershire County Council in the UK was doing a migration in which they completely changed up the folder naming conventions. It wasn’t just a simple change of drive letter, and it was quite a process. Links were a mix of simple cell references to other spreadsheets, cell references in complex formulas, references in data names, pivot tables and VBA. There were also data connections to some Access databases. (Phew!) Needless to say, their work was cut out for them! Here’s how they solved it, using LinkTek’s LinkFixer Advanced:
The State of Vermont government IT office did not simply have one migration to do. Oh no, that would have been much too simple.
They had a file system migration to do for the Department of Finance and Management. This one had one particular directory tree that had about… oh, maybe… 500,000 links in several thousand spreadsheets that were linked to files throughout tree.
When performing this migration, their intent was to homogenize the directory naming conventions as well as collapse multiple trees (including the one with all of the links) into a single contiguous tree. They quickly realized that by doing this it would break all of these links, but the file system was so disorganized that it needed to be done. Here’s how they used LinkFixer Advanced to save their tails:
Our good friend, Christine from Calgary, Alberta, had a beast of a migration to get done. She had to face the problem of broken links in her migration head on. She said, and I quote, “Broken links can cause high blood pressure.” We definitely reminded her that LinkFixer Advanced is not an FDA approved treatment for high blood pressure… But here’s her story on how she wrestled that data migration (and won):