Migration isn’t often viewed as an IT project with a hefty ROI. In fact, in can bring shudders to IT professionals. Of course the devil is in the details. Is the objective just to move content? Say from SharePoint to Office 365? Or is it to ‘intelligently’ migrate content, regardless of the platform so information is more usable, organized, and efficiently retrieved? All questions, only the organization can answer and what the specific project requires. According to a snippet I found, 84% of migration projects fail (Bloor).
At the basic level, migration is needed to move content, but at the deeper level to enable access for business users who need to find the information to support their job functions. That’s where the ROI can be achieved. This places most of the effort on pre-migration activities, such as identifying content to be used, cleansing the content, and moving it to an organized hierarchy that will enable it to be used after migration. Our approach is to use auto-classification to one or more taxonomies before the migration. This enables the ‘tweaking’ of the taxonomy to ensure documents are migrated accurately during the migration process.
This does represent an ROI which is based on the same criteria for calculating an ROI for enterprise search. Pre-migration activities are critically important and many organizations can achieve long term benefits and not simply moving content from one repository to another.
Do you prepare an ROI for migrations?