Recently I interviewed a consulting manager who had just delivered a very large ERP data migration. What was his biggest challenge? It was getting the business users engaged early in the project. And this is a very familiar story. I have been encountering this same challenge for years in delivering application data migrations. And it cuts both ways, either the business users are unwilling to spend the time, or the IT team does not recognize the need. In this case the team was delayed significantly (the estimate was that a project that should have taken four months lasted nearly seven), as data issues reared their ugly heads at the end of the development cycle, during the first mock load of the data. Lack of collaboration? It has impacts. In the recent white paper published by Informatica, The Five Pitfalls of Data Migration, one of the pitfalls outlined was a lack of collaboration between the business users (or data experts) and the data migration technical team.
What do I mean by business/IT collaboration? Really I am talking about baking data stewardship into the process of application data migration. And the tools to support that process. (more…)
Over the next few months on the Perspectives blog, I would like to address the many facets of what makes a data migration project work, what makes it successful (and what defines success, for that matter). I am approaching this from the perspective of best practices, including processes, skills and, of course, tools. As a jumpstart, this post and the next five will cover ‘The Five Pitfalls of Data Migration’. These are five key areas that anyone starting a data migration, or in the midst of one, must consider.
First things first. What do I mean when I say data migration? Generally there are two types of data migration, the storage data migration to address a server or database upgrade, requiring little or no data transformation. The application data migration addresses an application replacement, upgrade or consolidation, and requires a significant amount of data transformation. You may be moving to a new version of your CRM application, or consolidating a single view of customer database following an acquisition. Your organization may be embarking on a modernization program, and moving from legacy bespoke applications to a new off the shelf solution. Whatever the driver, there are good sound approaches to include when planning your strategy. (more…)