• James Higgs and Jeffrey Ruck

Cloud Migrations | The Launch

Let the journey begin! By now, you have the business commitment, and the technical and business stakeholders are well informed and prepared for change. For large and complex cloud migrations, a proof of concept should be performed, and for smaller projects, enterprise architecture has completed their analysis and selected a provider. By now operations has decided on the future Service Model and the Deployment Model.

Know your trajectory, cloud migration projects are no different from other complex initiatives, and well-defined deliverables are essential. Below are four key areas requiring special attention during the Launch:

  1. Inaccurate inventory of assets: Perform discovery using appropriate tools for the project complexity and size. Having a partial inventory or manually created inventory is typical but will lead to risk. Leveraging the correct tools to discover assets, integrations, and data flows continually during your project will provide an accurate inventory and reduce the risk. Document the business processes impacted by the assets in-scope meet with the business process owners to document the expected change impact. Identify what will be retired, consolidated, changed, migrated as is, or upgraded.

  2. Identity Architecture roadmap does not exist: Addressing Multiple identity providers or technology changes before a migration. Early in the project, engage with enterprise architects to understand how your project will integrate with the existing Identity Provider "IdP." Will your current IdP provider satisfy your compatibility and security requirements such as SAML version, Single-Sign-On "SSO" and Multifactor Authentication "MFA."

  3. The appropriate project gates are missing: The Architecture changed two months into the project due to the limitation of the technology. You should know wherein a transition, and where stakeholders incur risk and expenses. Plan to place a gate in the project, ensuring the appropriate review is performed by the appropriate resource, deciding if the project may proceed or the conditions need to change.

  4. Underestimating the time and effort to execute a migration: The time allotted to understand the current state environment through discovery was underestimated, which impacted the end state architecture: It is all about the impact the project will have on the business outcome. Define a realistic duration for Discovery and Design, which may be seventy percent or more of the duration. Understand the associated risks and impacts of arbitrarily accelerating a migration. Quick migrations or taking shortcuts to introduce higher risk.

Look for our upcoming post about "Performance and Control" This series of blog posts will bring to light lessons learned from our teams in the trenches. We’ll share with you what has worked and what pitfalls to avoid, saving you valuable time and resources.

Review the series

Post 3: Cloud Migration | Focus and Communications

Post 2: Cloud Migration | Business Commitment

Post 1: Evaporate into the cloud

22 views0 comments

Recent Posts

See All