All services in the cloud:

• Start-up organization
• New line of business

One-off migrations:

• Individual systems, services, business processes, or functionalities migrated in the cloud
• No cohesive strategy
• Each project is planned, costed, and executed independently by the team responsible

Evolutionary migrations:

• Migrating components of the operating model to the cloud over time using the guiding principle (progress iteratively with feedback)
• Which systems, services, processes, and functionalities best delivered using the cloud and which be kept in-house
• Focus on cloud compatible components or urgent migration
• Individually planned and migrated with reference to the cloud strategy
• Reviewed at closure and issues addressed in the next phase, also the strategy is reviewed regularly
• Require established business practices and regulatory risk management
• Good for organizations using large volumes of data that can be managed in parallel between the cloud and in-house environments
• Transition to new facilities to be planned smoothly and the legacy system offboarded when new processes are functioning and managed with little risk

Big-bang migrations:

• Disruption situation (for example, increased competition or mergers and acquisitions)
• New capabilities quickly realized
• Simplifies system mergers
• Focus on moving all identified components into the cloud as quickly as possible
• High risk
• Rapid re-engineering
• Use for urgent change or potentially catastrophic situation

Existing solutions in-house

Only new services in the cloud

In the future, may consider migrating some or all of the in-house systems to the cloud (one-off, evolutionary, or big-bang)