Business sponsors
Agree the intended outcome, users, priorities and how the work will be accepted.
YOUR GOOGLE CLOUD TEAM
VM migration to Google Cloud
Discover dependencies, assess cost and risk, and migrate Windows and Linux workloads with a tested cutover and rollback plan.
Discuss a migration ↗Cloud architecture and migration guides
Explore the capabilities, methods and practical resources for your project. Scope, licensing, timing and support are agreed with your Cloudypedia team.
VM Migration
Moving your Small or Medium business VMs to the cloud can help you escape capital-intensive refresh cycles. With on-premises discovery and analysis tools, you can understand the cost benefit of moving to the cloud.
Once you're ready, we've got the tools and processes to help you migrate using the lift and shift strategy
What is VM Migration Lift and Shift?
Replicate the environment as is (or with some improvement ) from co-locations or other cloud vendors to Google Cloud.
Benefits of Google Cloud :
Flexible cost effective compute options
Customized VMs to enable cost effectiveness
Superior network performance
Latest Intel and AMD processors
Data Center Location around the world
Support for Windows and Linux Operating systems
Benefits of Cloudypedia Services :
Google Cloud Infrastructure Specialized partner
End to end migration service including white glove service
Migrate from anything* or host to Google Cloud
Experts at migration tools such as Velostarata and Sureline
Team of Certified Google Cloud Engineers and Architects
VM Migration Project Process
Discovery
(For a free assessment click here)
Project starts with Discovery of your current environment. Can be done in 2 ways:
Manual process : We fill in a discovery with the current environment details such as VMs Sizes, Operating Systems and so on
Automated Process: Using tools to do environment discovery such as CloudPhyscis . Useful for 10+ servers discovery. Also shows an accurate cost comparison for the servers on GCP and other cloud providers
Foundation
Kick-off your new Google Cloud Platform project with a focus on your foundation architecture, technical design, long term operations and migration planning for your workloads.
Step 1: Technical infrastructure and Operation Kick-off (Workshop) :
Prepare and plan the needed configuration such as Security, Networking, Systems monitoring
Step 2: Technical and Application Design document:
Cloudypedia will provide a technical design document based on the infrastructure and Operation workshop for review
Step 3: Build the Enterprise Foundation:
Implementation of the Google Cloud Platform Project including users access, security , Billing, Networking, systems monitoring and others
Migration
Once the VMs discovery and Foundation for GCP project is setup actual data and VMs migration kicks off:
Utilizing Sureline ot Velostrata for the migration process
Update networking and other related conflagration on the go
Customer Story
Below video is a walk though Migration part for SMB followed by story from Healthcare Provider Forefront Telecare:
Customer StoryRead the document ↗Related solution
Media Solutions for Small and Medium business here
Relevant experience
Explore the context and approach behind the work. Each story describes its own scope.
Saudi Arabia · Manufacturing
Browse every customer story ↗Deemah
A Cloudypedia customer story about planning an SAP S/4HANA upgrade and Google Cloud migration for a Saudi manufacturer.
Customer story ↗Egypt · Automotive & logisticsNacita
A Cloudypedia customer story about piloting and migrating SAP infrastructure to Google Compute Engine for an Egyptian automotive and logistics business.
Customer story ↗Make the next conversation useful.
Bring the business outcome, current environment and constraints. We can then define a suitable assessment, implementation or ongoing service.
Technical teams
Review architecture, integrations, data access, security and operational ownership.
Procurement teams
Confirm scope, contracting entity, licensing route, commercial terms and support responsibilities in the proposal.
What shapes your proposal?
Workload complexity, dependencies, data location, delivery responsibilities and operating needs determine scope and timing. Licensing, billing currency, taxes, payment terms and support coverage are confirmed for the relevant market and agreement.
