We have now build a database of hard numbers that define the true costs of migrating to the Cloud. The Business cases are built around minimising the exposure to the hybrid world paying for both the on premise and cloud simultaneously. Only when the final component / user is migrated can the benefits be realised and the legacy environments be decommissioned releasing the savings
​​
Our Business cases to date have covered migrating from/to:
-
Google to Microsoft 365
-
On premise to Microsoft 365
-
On premise to Google
-
Managed desktop to VDI and vice versa
-
On premise infrastructure to the Cloud
-
On premise infrastructure to on premise infrastructure
Other cost models and Business cases include LAN, WAN, Wi-Fi, remediation and voice.
​
The starting point to developing the Business case is understanding the 'as is' and 'to be' technology stacks which defines the components for change.
​
From this base we then apply the cost of Transform then migrate to the Cloud. This ensure the Cloud costs are optimised for consumption based pricing. Migrating an 'as is' infrastructure without first consolidate and optimising makes cloud prohibitively expensive. Likewise, migrating a user based to Cloud without being clear on the exact user base can result in over allocation of licensing.
​
The next stage is defining the readiness criteria costs. Cloud consumption requires changes to sub-components in the technology stack which are often overlooked in Business cases. These can include upgrading firewalls and bandwidth to manage increased internet traffic, changes to the application estate to where applications are mapped to on premise systems or drives or removing customisation.
​
Finally, the last two components are the cost of migration and importantly the expected savings as a result of decommissioning the legacy environments.
​