One approach is to use a migration service that can help from start to finish for a smooth and successful SAP migration. This is all fine and well, but there are still issues to consider after the go-live date - is the business equipped to independently handle any ongoing data quality or integration needs down the road, or will this require another services engagement?
Another alternative is to provide the business with a re-usable, repeatable approach for SAP migration – one that also accounts for ongoing data quality and integration needs well beyond the go-live date given that data is said to degrade at 2% a month. While this may require more time and planning up-front, it’s well outweighed by the long-term benefits of a self-sufficient information management infrastructure to help ensure end user adoption and governance over time. Seeing that 2010 is also the beginning of a new decade, wouldn’t this year be a great time to start planning/preparing for a re-usable, repeatable approach for SAP migrations? As the proverb goes – “Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime.”
Whether it’s finishing/migrating left over resolutions from 2009 or making sure your enterprise has an information infrastructure in place for SAP migrations and beyond, there’s no time like a new year to get things started.