What needs to move
Check moving from GCP by identifying Compute Engine workloads plus VPC rules, service accounts, Cloud Storage, managed databases, load balancing, DNS, serverless services, and other dependencies that need destination equivalents.
Migrate from GCP
Map your compute, storage, database and identity dependencies. Check which components can move directly and which need changes.
Hosting options
Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →02Tell us what you need to host and when it needs to be ready.
See Ask about your project →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →Your requirements
Check moving from GCP by identifying Compute Engine workloads plus VPC rules, service accounts, Cloud Storage, managed databases, load balancing, DNS, serverless services, and other dependencies that need destination equivalents.
Copy the site or application to the new host and test it privately. Check logins, forms, database writes, scheduled jobs, email and any external integrations.
Choose when to stop or synchronize new writes. Include orders, uploads and mail that arrived after the first copy. Avoid letting both systems accept independent changes.
Save the old DNS and routing settings. Switch traffic after the final tests, monitor the result and keep the old service until the agreed rollback period has passed.
Field guide
A Google Cloud project holds Compute Engine instances alongside platform services: VPC firewall rules, Cloud Storage buckets, Cloud SQL databases, load balancers, Cloud DNS zones and service accounts that applications run as. Inventory the project service by service. Instance data exports as files and database dumps, while platform services each need an export and a destination equivalent.
Service accounts are the silent dependency. Code on the old instances often reads storage or sends mail using permissions granted to the instance itself, with no key file anywhere to copy. List what each service account can reach, create destination credentials for the same jobs, and test storage reads, database connections and mail sending before the DNS change.
Check for Cloud Functions, Cloud Run services and scheduled jobs tied to the instances. They keep running, and billing, after the servers move unless someone closes them.
Export the Cloud DNS zone in full, including mail, verification and DKIM records. Recreate it at the destination before nameservers change.
Note reserved external addresses and who allowlists them. Release or replace each one only after the new address is live and tested.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.