As the pace of digital transformation accelerates, our partnership with VMware continues to focus on helping customers successfully navigate their cloud journey and achieve their business objectives through seamless and rapid migration of business critical VMware workloads.

We announced the general availability of Google Cloud VMware Engine in May 2020. Since then we have worked closely with VMware to make it easier for customers to quickly migrate and run business-critical, VMware-based workloads on Google Cloud. Customers are already leveraging the service across a variety of use cases including application migration, datacenter exit, virtual desktop infrastructure, disaster recovery, and spinning up new capacity quickly to meet business needs.

For example, retailer Carrefour migrated its on-premises VMware workloads to Google Cloud without disruption to shoppers or employees while reducing operating costs by 40% and energy consumption by 45%. Once in the cloud, Carrefour was able to leverage its data and AI to deliver innovative customer experiences across online and in-store channels. Similarly, telecommunications provider Mitel migrated thousands of VMware instances across 30 data centers to Google Cloud in less than 90 days, quickly achieving increased stability, scale, and security.

Today, we announced the continued growth of the Google Cloud and VMware partnership with the addition of Google Cloud VMware Engine within VMware Cloud Universal. Google Cloud VMware Engine delivers a cloud-native VMware experience and enables you to rapidly migrate to the cloud without changes to your apps, policies, or tools. Once you migrate your VMware workloads to Google Cloud, you can accelerate digital transformation through seamless access to services such as BigQuery for real-time data analytics and cloud-native container-based architectures on Kubernetes.

With VMware Cloud Universal, you will be able to accelerate migrations of your workloads and applications to Google Cloud through purchase of Google Cloud VMware Engine from VMware and its partners, allowing you to flexibly purchase credits, and leverage existing spend and unused VMware Cloud Universal credits. The program will offer the following benefits:

• Financial flexibility by letting you redeem VMware Cloud Universal credits for Google Cloud VMware Engine
• Streamlined consumption by enabling you to burn down your Google Cloud commits while purchasing from VMware
• Use of existing VMware licensing investments through the VMware Cloud Universal program for Google Cloud VMware Engine

With Google Cloud VMware Engine, you can take advantage of Google Cloud’s highly performant, scalable infrastructure with fully redundant and dedicated 100 Gbps networking, providing 99.99% availability to meet the needs of the most demanding workloads at very low costs. By providing a consistent VMware environment natively in Google Cloud, you can quickly migrate your VMware workloads to Google Cloud without changes. Deep and unique networking integrations and capabilities such as multi-region and multi-VPC connectivity, further ease the migration of complex enterprise networking topologies to Google Cloud. With rapid provisioning of private clouds across 13 global regions, you can also take advantage of on-demand capacity to serve your infrastructure needs with a cloud-native VMware environment in Google Cloud.Once in the cloud, you can take advantage of other Google Cloud services such as BigQuery and Cloud Operations to gain data-driven insights and unify operations.

Getting started

With Google Cloud VMware Engine as part of VMware Cloud Universal, Google Cloud is a compelling cloud destination for your VMware workloads. You can learn more about how to get started with the service and get additional detail around use cases and pricing on our website.

The COVID-19 pandemic brought dramatic changes to the financial services industry. Already under pressure from nimble young fintechs to modernize, established banks and insurers were undergoing incremental digital transformation. But in 2020, they hit the gas pedal. Branches closed and remote work became the norm. Almost overnight, employees needed secure remote access to corporate systems, and customers expected to be able to complete even complex transactions whenever they wanted, on whatever device. Even as things return to normal, many of these shifts are likely to be permanent. According to Forrester Research, nearly 90% of global financial services CIOs and SVPs believe that improving their application portfolio is key to improving customer experience and driving revenue.¹ The problem? Replacing legacy systems with cloud-based SaaS enterprise software is a massive, time- and resource-intensive process. 

IDG’s recently completed white paper, Financial Services Spotlight: Elevating agility and security in the cloud, highlights an alternative to the all-or-nothing approach to replatforming: “lifting and shifting” on-premises applications and workloads to the cloud without rewriting them. In this way, you keep your organization’s familiar architecture, but give it the scalability and cutting-edge technology of a modern cloud environment. That’s the promise of Google Cloud VMware Engine brings to the financial services industry.

Here’s a quick overview of the insights that the IDG study uncovers. Download the complete white paper.

Simpler migration, rich rewards

Google Cloud VMware Engine helps financial services companies seamlessly migrate and run 

VMware workloads natively on Google Cloud. Once in the cloud, firms can take advantage of Google Cloud services, access a robust third-party cloud ecosystem, and use the same VMware tools, processes, and policies their teams already know. The IDG study found that migrating to Google Cloud with Google Cloud VMware Engine offers multiple benefits:

1. Create new customer experiences. Migrating to Google Cloud puts modern, cloud-native architectures and technologies — such as containers and microservices — easily within reach. These make it possible for financial institutions to quickly and securely launch new applications and update them on a continuous basis using DevOps pipelines. They also allow firms to craft more personalized customer experiences across channels using Google Cloud’s native AI and data analytics.
2. Deliver new services. After migrating, financial services organizations can connect to multiple third-party service providers via cloud-based APIs to bring new, diverse services to their customers — without having to build from scratch. 
3. Make the best use of IT resources. When your data and applications reside in Google Cloud, you’re no longer constrained by the physical storage and compute limits of on-premises infrastructure. This means your company can match capacity to demand — even during unexpected peaks. You also gain more visibility into your hybrid cloud environment with Google Cloud’s operations suite, which offers intelligent analysis and easier troubleshooting for your platform and applications.
4. Gain fresh insights. The key to understanding what customers need and when they need it resides within your data, and data analytics in the cloud help you uncover those insights. Your company can connect to Google Cloud’s serverless data warehouse, BigQuery, which leverages data to deliver valuable insights for personalized customer experiences, rich compliance reporting, new product development, intelligent fraud detection, and more. 
5. Choose what to move. Data governance regulations and requirements specific to the financial services industry mean that some data must remain on premises. Google Cloud VMware Engine lets you easily manage a hybrid cloud/on-premises environment to keep sensitive data fully under your control.
6. Become more resilient. Google Cloud VMware Engine gives financial services firms a distributed architecture and centralized control for their applications to support vital business continuity functions, such as backup and disaster recovery. This is on top of the performance and availability of Google Cloud’s global infrastructure.
7. Improve security. Using cloud-native application frameworks, administrators can issue patches and software updates centrally and automatically across their organizations. This reduces the risk of errors and security vulnerabilities. Firms also tap into the security features and capabilities of Google Cloud, including always-on encryption and AI-powered threat detection.
8. Redirect IT resources. Migrating virtualized workloads to the cloud can free up talent and budget to develop new products and services — time that was previously spent on maintaining complex on-premises infrastructure. That means less effort spent keeping the lights on, and more resources directed toward creating innovative and differentiating customer experiences.

IDG research concluded that migrating business applications to Google Cloud with Google Cloud VMware Engine can help financial services companies stay ahead of change without incurring further technical debt from their legacy IT systems. Working with cloud-based systems can give your financial services company much of the scale, speed, and agility of a startup while still enjoying the benefits of being an established organization.

Read the complete white paper to learn more about the ways in which Google and VMware work together to accelerate digital transformation for financial services firms.

^{1. Vmware-forrester-financial-services-modern-app-report.pdf, A commissioned study conducted by Forrester Consulting on behalf of VMware, 2020}

Accelerating digital transformation

Digital transformation is what propels businesses and industries forward. Organizations of all sizes—from startups to global enterprises—focus on digital transformation not only to make scaled improvements, but also to drive significant change and fully embrace the digital age. The pandemic has jump started and pushed many organizations into full gear to digitize their business models and transform with increased business agility, resiliency, and velocity, while driving new innovation and business values for the customers.

However, according to the Boston Consulting Group, only about 30% of companies navigate a digital transformation successfully. Many large scale digital transformation programs failed because of lack of clear business priorities, top-down executive sponsorship, or dedicated resources and commitment to see it through.

Laying the foundation for digital transformation success

Digital transformation drives foundational change in how an organization operates, optimizes internal resources, and delivers value to customers; however, this doesn’t just happen overnight. Digital transformation requires a programmatic approach through an incremental yet agile, cost-effective, value-driven, and sustainable strategy to drive successful transformation across the organization.

One of the critical factors foundational to success is Cloud FinOps (Cloud Financial Operations). Cloud FinOps is an operational framework and cultural shift that brings technology, finance, and business together to drive financial accountability and accelerate business value realization through cloud transformation. In the context of Digital Transformation, it requires new ways of working and operating models to drive behaviors and cultural change that foster cross-functional collaboration, drive accountability, provide greater cost transparency, and promote a blameless culture.

Most importantly, Cloud FinOps serves as an enabling function to drive successful digital transformation programs and enable business agility by breaking down the boundaries between technology, finance, and business teams. Through this cross-functional team collaboration, technology leaders partner with finance and business leaders to better understand the technology investments to create sustainable business outcomes. By doing so, business priorities become more clear and the focus shifts to value creation, customer-centricity, and innovation.

As such, companies are reinventing their business models to fund value streams and connect cloud technology investments to strategic business outcomes. With the increased visibility of the cloud costs, finance teams are also gaining greater accuracy in tracking cloud spend against budgets. Organizations can align the TCO of the technology services to the value metrics to make better informed future investment decisions and forecast demand.

Cloud FinOps to accelerate business value realization

The successful deployment and implementation of Cloud FinOps building blocks will enable organizations to accelerate digital transformation beyond cost savings, including the ability to:

• Accelerate business value realization and innovation
• Drive financial accountability and visibility
• Optimize cloud usage and cost efficiency
• Enable cross organizational trust and collaboration
• Prevent cloud spend sprawl
• Break down of departmental silos

Organizations that are successful in digital transformation most often have established processes to measure and track business value. One of the key building blocks of Cloud FinOps is “Measurement & Realization.” By establishing a robust value measurement approach to track and monitor the business value metrics toward business goals, we are bringing technology, finance, and business leaders together through the discipline of Cloud FinOps to show how digital transformation is enabling the organization to create new innovative capabilities and generate top-line revenue.

Business value metrics fall across several factors: cost efficiency, resiliency, velocity, innovation, and sustainability. We suggest assigning KPIs to the following metric categories:

Cost efficiency: Measure cost efficiency through infrastructure savings, migration, and support costs. Customers will commonly start with metrics such as cost of compute and storage per day-week-month, and evolve to unit metrics such as cost per customer served or cost per transaction, where the cost of an application stack is aligned to customer drivers.

Resiliency: Enhance operational resiliency with improvement in service quality and security risk posture. Traditional measures such as system service level and the frequency and duration of critical downtime events are effective measures of IT durability. Customers can also augment these metrics by associating a cost per minute of downtime events, reflecting not only the direct impact of these events but opportunity costs as well.

Velocity: Decrease time to market by accelerating fluidity in product and service delivery. By moving to a cloud-based microservices architecture, customers commonly achieve benefits of increasing software release frequency, as well as being able to run many more test scenarios prior to release, resulting in higher quality code. As an example, our recent Google’s State of DevOps Report 2021, shows that elite performers have 973x more frequent code deployment and release frequency than the low performers.

Innovation: Enable a culture of rapid experimentation to drive innovation and cloud transformation. With cloud technology, companies can avoid the financial constraints of fixed cost investments and lengthy procurement lead times. As a result, the marginal cost of experimentation and time from ideation to experimentation can drop significantly while the number of experiments per unit of time can grow dramatically.

Sustainability: Embed true environmental and social sustainability metrics across the organization by adopting a circular economy strategy and building sustainability into everything we do – from running applications on zero net emissions virtual machines to reducing carbon footprint with enhanced productivity and collaboration services. According to Accenture, companies with average on-premise to cloud migrations can drive 65% energy reduction and carbon emission reduction of 84%1.

Getting started

The Cloud FinOps journey starts with defining or updating your metrics. Since business goals and strategic imperatives will likely change over time, it is important to review the Cloud FinOps metrics whenever the goals change. The review of metrics should include the changes in business goals when there are changes in the internal priorities of the team. Executive leaders need to identify dependency relationships between technology and business outcomes to improve the impact of metrics on decision making and to better prioritize and invest in evolving business and technology capabilities. Defining good metrics is not just about aligning to business goals and demonstrating value. It is also important to help prioritize strategic initiatives, guide effective resource allocation, and generate awareness across the organization to drive a shift in mindset with the new way of operating in the cloud.

The pandemic has accelerated the need for companies to modernize their digital capabilities. With technology-driven disruptions across all industries, it has never been more important for organizations to transform themselves, embrace an agile mindset, and make bold investments in cloud technology and capabilities to achieve sustainable business outcomes.

So, where are you now in your cloud FinOps journey, and how do you move beyond the challenges ahead? Google can help you start the conversation and accelerate your path to maximizing business value with the cloud.

No matter where you are on the cloud transformation journey, through an interactive session with Google, we can bring executives across the organization together to work toward a shared vision and a plan to accelerate and realize business value in the cloud. If you are interested in more information, please contact us.

Special thanks to Pathik Sharma, Bruce Warner, Jon Naseath, and Nihar Jhawar for their contributions and sharing their domain expertise to this important Cloud FinOps topic.

Congratulations! Your company just acquired or merged with another organization, beginning an important new chapter in its history. But like with many business deals, the devil is in the details — particularly when it comes to integrating the two companies’ cloud domains and organizations. In this blog post, we look at how to approach mergers and acquisitions (M&A) from the perspective of Google Cloud. These are the best practices that your Google Cloud Technical Account Managers follow — or that we recommend you follow if you plan to perform the integration yourself.
Although there are various M&A scenarios, here are the two most common ones we will focus on:

• Both entities engaged in the M&A have some presence on Google Cloud and are looking for some level of integration
• Only one of the entities has a presence on Google Cloud, and is looking at best ways to work together

Depending on your situation, your approach to integrating the two companies will vary substantially.

When both companies have a Google Cloud presence

In the first scenario, let’s assume company A is acquiring company B. Prior to the M&A, both companies have their own Google Cloud Organizations — the top level structures in the Google Cloud resource hierarchy — and have one or more billing accounts associated with them. There are also various Folders and Projects below each Google Cloud Organization. In this scenario, here are the key questions to ask:

• How do you plan to integrate/consolidate two distinct Google Cloud Organizations?
• How do you plan to organize the billing structure?
• How do you handle Projects under the two Organizations?
• What is the identity management strategy for the two Organizations?

For each of these key questions, go ahead and formulate a detailed plan of action. If you have access to the Technical Account Manager service through Google Cloud Premium Support, you can reach out to them to further develop this plan.

Understanding Google Cloud Organizations

From an organizational integration standpoint, when each entity in an M&A has its own Google Cloud Organization, you have various options: no integration, partial, or full.

No integration – When company B operates as an independent entity from company A, no migration is required. One caveat is if company A has negotiated better pricing terms/discounts and support packages with Google Cloud. In that case, you can sign an affiliate addendum by working with your Google Cloud account team to help unlock the same benefits for company B.

Partial integration – Some projects move over to company A from company B and others stay with Company B. There can be some shared access between the two companies and each of the organizations can continue to use their existing identity providers. This can be a self-serve or a paid services engagement with Google Cloud depending on the complexity of the two companies and how many project migrations need to take place between them.

Full integration – Company B is fully incorporated into company A. This means you go through a full billing, Google Workspace identity and project migration from company B into company A. This can be a complex process and we highly recommend engaging your Google Cloud account teams to scope out a paid services engagement to go through this transition.

Planning your project migration

No matter what you want your end state to look like, project migration requires careful planning. Again, if you have an assigned Technical Account Manager, please reach out to them to ensure that you have a conversation around best practices before starting this migration.

If you’re taking a self-service approach, at a high level, we recommend leveraging the Resource Manager API to manage your project migrations. Do keep in mind that there are several prerequisites and required permissions documented here that need to be assigned before going down this path.
In addition, please be sure to read the billing and identity management considerations below to ensure that you are covering all of the bases associated with such a migration, as your choices can fundamentally alter your Google Cloud footprint.

Billing considerations

When deciding how to structure your Organizations and billing accounts, our recommendation is to always limit the number of Organization nodes and use the Folder structure to manage departments/teams within it. Creating additional Organization nodes is only advised in cases where you require a level of isolation for certain Projects from central administration for a specific business reason, for example, if the company being acquired already has their own Organization node and there is a business justification to let it operate as a standalone entity.

Warning: If you have multiple Organization nodes, be aware that you will not have central visibility across all your organizational resources, and that policy management across different Organization nodes can be cumbersome. You will also have to manage multiple Workspace accounts and manage identities across them, which can be difficult, especially when operating at scale.

From a billing account management perspective, our recommendation is to create one central billing account that lives within the Organization node with tags and labels incorporated for additional granularity. However, there are a few business cases which warrant the creation of additional billing accounts such as:

• You need to split charges for legal or accounting purposes
• Invoices are paid in multiple currencies
• You need to segregate usage to draw down on a Google Cloud promotional credit
• Subsidiaries need their own invoice

Keep in mind that committed-use and spend-based discounts and promotional credits cannot be shared across billing accounts and are provisioned on a per-billing-account basis. As such, more billing accounts can make it harder to leverage these discounts and credits.

Identity management

As you might expect, merging two entities has identity management implications. Cloud Identity is the solution leveraged by Google Cloud to help you manage your user and group identities. Even if the acquired company only uses the productivity products that are part of Google Workspace, the identities would still be managed by Cloud Identity.

Google Workspace considerations

To move large amounts of content into a Google Workspace domain, we recommend one of three options, depending on your end goal and data complexity:

• For general migrations: Leverage Google Workspace Migrate to move data into your Workspace domain from either another Workspace domain or a third-party productivity solution
• For manual migrations: Use the Export tool to move your organization’s data to a Cloud Storage archive so you can selectively download exported data by user and service
• For complex Google Workspace scenarios: Speak with your Google Cloud Technical Account Manager about the possibility of using a custom scoped engagement to merge two Google Workspace environments without business interruption

When only one company is on Google Cloud

Now, let’s consider the scenario where only company A has a presence on Google Cloud but company B does not. The approach you take to integrate the two organizations largely depends on your desired end state — full, partial or no integration.
If the plan is to eventually integrate company B into company A, your approach here will have a lot of similarities with the ‘full integration’ option mentioned above — just at a later point in time.
You may also run into a scenario where company B has a presence on an alternative cloud platform and you need to migrate resources into or out of Google Cloud. Again, similar to the partial integration option called out above, a paid engagement or a self-service exercise would be a good fit depending on the complexity of the desired end state.

Here to help

A merger or acquisition is an exciting milestone for any company, but one that needs to be managed carefully. Once you carefully review these considerations, develop a plan of action for your organization. You can also engage Google’s Professional Services for a paid engagement or Google’s Technical Account Management Service for a self-managed process to achieve the desired results.
If you are going through or considering going through M&A at your organization and have a different scenario than what we have discussed, please feel free to reach out to your account teams for guidance or contact us at https://cloud.google.com/contact.