Innofactor has developed a secure cloud migration framework and a cloud transformation process based on Microsoft best-practices. Our experience indicates that in order to achieve the desired goal within a reasonable time and without large cost overruns, it is critical to have a good process and method.
Innofactor is a recommended Microsoft Azure Partner and has a reputation of being one of the leading migration experts in the Nordics. Our team consists of 200 experienced Azure consultants in the Nordics incl. some superstars with MVP-status.
Cloud transformation is 20 percent technology and 80 percent business. That's why a successful transformation must be rooted in the business needs of the customer.
A clear picture of the current state
The first phase is a mapping phase. The purpose of this phase is to uncover the migration goals, as well as produce a data basis that allows you to make fact-based decisions against how to realize the target image.
We help you clarify the current state
Define goals - Innofactor needs to gain insight into ongoing processes. This involves insight into specific objectives, strategy and KPIs. We reveal this by conducting interviews with key people.
An actionable plan for going forward
The most important premise for Innofactor's part in this process is that we sit on the customer's side of the table, and that our objectivity is maintained.
Innofactor secure cloud migration process is a framework developed based on experience and best practice through hundreds of deliveries across industries and sectors. The framework has been developed because it reduces risk and uncertainty for the customer through the process, in addition to providing a clear and distinct path towards achieving expected results.
Driving Microsoft cloud with top Nordic customers - Read our customer stories
Phase 1 - Assessment & Storyboard
The first phase is a mapping phase. The purpose of this phase is to uncover a end goals, as well as produce a data basis that allows you to make fact-based decisions against how to realize the goals.
The end result of this phase will contain information about the current situation and define a goal picture. In this phase, activities are carried out such as:
- Technical mapping and interviews with key people
- Carry out a technical mapping of applications, services and other important dependencies
- Define goals - Innofactor needs to gain insight into ongoing processes. This involves insight into specific objectives, strategy and KPIs. We reveal this by conducting interviews with key people
- Storyboard - What a modern platform looks like today, and the possibilities for modernization in a simple way. Introduction to new technology such as "serverless", containers, PaaS services or Azure in general
Objectives for the phase:
- Understand customers' vision and strategy
- Understand the customers' current situation
- Provide high-level roadmaps with proposed solutions for implementation
Phase 2 - Foundation
The second phase is about building a foundation on which the new services will be produced. This is done first by building a governance model that takes into account the company's internal and external requirements for the services to be produced. The model takes into account the business requirements for the IT platform, such as uptime on services, security requirements, requirements for third-party applications, naming standards, etc.
The governance model also ensures that the IT platform develops in accordance with the business' defined requirements. It can be used as a requirements specification when procuring new services, as a basis for internal and external audits and as a tool for reducing risk and uncertainty regarding future IT.
Once the Governance model has been established, an Azure platform and MS365 platform will be built based on our best practice and the company's identified requirements in accordance with the Governance model.
Objectives for the phase:
- Map out laws and regulations for an Azure Governance Model
- Create and document the Governance model
- Create architecture at a high level
- Security, identity, infrastructure, etc.
- Build a framework for a DevOps organization
Phase 3 - Implementation
The next phase is to start the work of moving services. This is the most time-consuming phase.
Innofactor uses a framework based on Gartner's 6 R1r. This means taking service for service, and evaluating whether to:
- Repurchase (SaaS)
- Refactor (rewrite the application for PaaS or Containers)
- Replatform (Lift & Reshape)
- Rehost (Lift & Shift)
- Retire (wind up)
- Retain (leave it as it is)
On the basis of the analysis phase, Innofactor will prepare and document an implementation model for the transformation and migration of traditional IT services to modern cloud-based services (public cloud). The decision on what to do with the application is anchored in the customer requirements and the Governance framework. Once it has been decided what to do with a service, Innofactor executes it. Prioritization of services is revealed in the "Storyboard" phase.
Objectives for the phase:
- Design solutions based on high-level architecture and governance
- Security, identity, infrastructure, application, client, management etc.
- Implement the solution to the goals around Business and Compliance
Phase 4 - Adoption
A new IT platform will require a change in the usage pattern of both the business and IT. The purpose of this phase is to enable the organization to deploy and manage the platform in accordance with existing Governance frameworks.
Examples of training that can be given can be:
- User training of new tools, such as Azure, Office 365, Teams etc.
- Innofactor tailors workshops based on wishes
- Cloud management for IT resources
- Adoption of DevOps
Phase 5 - Managed Services
The IT platform must be operated, monitored, maintained and taken care of. The goal of building a new IT platform is to build it in such a way that as much as possible is purchased as a service or is automated, so that the need for operation is minimized.