Data migration projects are really a lesson in gap management. We are effectively building a complex web of technology and understanding to bridge the gulf between the legacy world and the target world.
Most of the gap management in data migration revolves around solving data quality and mapping issues. We work tirelessly to solve the problem of getting the data to a suitable level for migration and then we figure out the pathways data must go on to land safely in the target environment.
But there is another gap that is often missing from data migration projects – one that should play a much greater role: business function gaps.
Business functions are the building blocks of any organisation. They are the core activities that drive services, revenues and operations across your organisation.
So you would think they would be well understood, right?
Well, not so, unfortunately. Data migrations are the type of project that "lay bare" not only your shortcomings with data, but just how little business leaders really understand about their business.
Functions are important because by focusing exclusively on the data aspect of a migration, you often only focus on what is presented in front of you. Frequently there are many more functions that are carried out, but they're poorly documented and may even use local data stores that aren't on any data architect’s grand plan.
Business function modelling allows you to understand the major gaps between the old world and the brave new world you want to reach. It is a great tool for spotting huge obstacles that can go overlooked when the focus is just on the data content and structure.
By performing business function modelling during the migration, you're able to quickly build a more representative logical model that allows you to identify major gaps and misplaced assumptions that can cripple your migration.
Perhaps the biggest advantage of using business function modelling on a data migration is you need to engage with the business to get results. What you create is a resource that becomes meaningful to everyone on the project, so when you link the data to the functions you start to also see how critical data quality will become if left unresolved. All too often on data migration projects there is scant attention paid to involving the business community. Some vendors even obsess with outsourcing and eliminating as much business engagement as possible.
Business functions are therefore a communication portal, connecting the migration technical team, sponsors and everyday business users. They are simple to create but have far-ranging benefits, so I would urge you to consider them in future.
