Migration projects are in growing demand for the evolution of today’s organisations.
They come in different shapes and forms, such as
- datacentres migrations
- desktops
- operating systems, e.g. win server 2003, win xp
- applications, changing vendors, new versions of your CRM or ERP platform
The key drivers and constraints behind migration projects are costs, time, risks, as well as industry regulations.
Your typical Migration Project template
That being said we can plan our migration project around the following 7 key phases.
Migration Phases – copyright @ http://www.xceedgroup.com/
Following the best practices such as PRINCE2, every project should have an initiation phase, which includes producing and approving a business case, appointing the project team and getting the ball rolling with the PID (Project Initiation Document).
We then assess the existing environment, collect data from golden sources and double check them with a discovery exercise. Once our AS-IS is clearly defined we can work on the design of the intended TO-BE.
A migration strategy will be evaluated, discussed and approved by the steering group. Having agreed on costs, design options and timelines, we can write the plan and execute it.
The execution phase will include reports, managing risks and issues, handling delays and reviewing milestones and timelines if necessary, and it will ultimately lead to the project closure, and its handover.