Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

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.

Your requirements

What does your project need?

01

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.

02

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.

03

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.

04

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.

Field guide

Unpacking a Google Cloud project first

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.

01

Serverless pieces listed

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.

02

Cloud DNS capture

Export the Cloud DNS zone in full, including mail, verification and DKIM records. Recreate it at the destination before nameservers change.

03

Static address release

Note reserved external addresses and who allowlists them. Release or replace each one only after the new address is live and tested.

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

We will handle the move. You check it first.

Your 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.

Start my free moveSee plans and prices
See pricesFree move