Over the years I’ve seen many implementations of Learning and Talent Management Systems – some good, some bad and a lot that were, well simply average. In each case, there was a contributing factor that was repeated time and time again to impact on these implementations. A factor that was not obvious or just ignored and failed to be called out as being a major contributor to a project’s success. Yet when viewed in hindsight, most people acknowledged it as pivotal and provoked the response – ‘I wish we’d thought about this before we started’.  So, it made sense for me to share this knowledge to help improve the success of future implementations by highlighting the danger areas and pitfalls, as well as outlining best practice to mitigate this factor.

In the next few blogs, I’ll cover each component of this factor in detail to provide you with an insight and framework that will dramatically improve your implementation and the resulting performance of your deployed system. So what factor am I talking about? Data Migration. Simply put, it’s the data the system uses. It’s the data that was identified to be transferred from your old legacy system to the new target system. The same data that was then transformed to meet the new system’s requirement. And the very same data that was finally migrated into your new shiny system in the expectation (more hope) that it will deliver all the benefits promised in the investment business case and delight the end users. A big ask considering the whole process of Data Migration Services, was not really called out in the Statement of Work (SoW) and certainly not budgeted for.

And why does this sorry situation exist? Well to be honest and I maybe raising a question about my own personality – data is dull, really dull and to compound matters, it’s also complex to understand, manipulate and manage and is invariably an unknown at the start of any project. So, read on and I promise a scintillating romp through Data Migration Best Practice to improve your implementation and reduce subsequent trouble tickets raised by those pesky end users, as well as your stress levels…