Google Cloud Adoption: Discovery and Mapping Your As-Is to Cloud, Using Cloud Migration Center

Welcome to the continuation of the Google Cloud Adoption: From Strategy to Operation series.

Let’s recap what we’ve achieved so far:

1. We’ve established our cloud strategy and defined a set of goals. We’ve integrated an open source strategy.
2. We’ve built a business case. As part of this, we’ve conducted a high level estimate of our future Google Cloud run costs using Google Cloud Migration Centre.
3. We’ve established a set of cloud adoption and cloud consumption principles. These form the foundation that all our subsequent technology decisions can build upon.

In this part we’ll focus on how to map our as-is technology to Google Cloud. I’m going to cover this in two parts. In the first part (this article), I’ll cover these topics:

• Building a view of our existing estate.
• Why it’s good to have a CMDB.
• How to Perform As-Is Discovery with Google Cloud Migration Center.
• Grouping the Discovered assets.
• Creating a TCO Report with Cloud Migration Center.

Building a View of Your Existing Estate

We need to establish the workloads we have today, and then establish how we will run these workloads in Google Cloud.