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
Move a Google Cloud workload to DotMoose
Map your compute, storage, database and identity dependencies. Check which components can move directly and which need changes.
Hosting options
Compare the services for your project.
01
Migration help
Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →02Ask about your project
Tell us what you need to host and when it needs to be ready.
See Ask about your project →03Domains
Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →Your requirements
What does your project need?
Test the destination
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.
Copy the final changes
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.
Switch traffic and retain rollback
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.
Planning
Access, backups and handover
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Free guide
Move a Google Cloud workload to DotMoose: planning checklist
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Help choosing
Tell us about your project.
Send us the software you use, your storage needs and your launch or moving date.
Ask about hosting