What needs to move
Check moving from DigitalOcean by identifying Droplets plus attached volumes, firewalls, DNS, databases, object storage, load balancers, private networking, snapshots, and cloud-init dependencies that may not map one-for-one.
Migrate from DigitalOcean
Map your applications, volumes and managed-service dependencies before moving. A VPS migration may also need separate database and object-storage work.
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 DigitalOcean by identifying Droplets plus attached volumes, firewalls, DNS, databases, object storage, load balancers, private networking, snapshots, and cloud-init dependencies that may not map one-for-one.
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 DigitalOcean setup is rarely one server. Alongside the Droplet there may be block storage volumes, a managed database, Spaces object storage, cloud firewall rules and DNS hosted in the same account. Inventory each piece and export data at the application level, with database dumps and file copies, because snapshots alone do not rebuild services elsewhere.
Private networking assumptions break first. Applications often reach the database or a second Droplet over a private address that will not exist at the destination, and floating IPs hide which machine actually serves traffic. Map every internal connection, replace private addresses with the new topology during the rebuild, and test each service connection before public DNS moves.
List volumes, managed databases, Spaces buckets, load balancers and firewalls beside each Droplet. Every item needs a destination equivalent or an export.
Save cloud-init and user data scripts plus environment files. They hold the package list and configuration that a bare file copy misses.
DigitalOcean may also host the DNS zone. Capture the full zone early so DNS can move on its own schedule.
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.