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 DigitalOcean

Move from DigitalOcean to DotMoose

Map your applications, volumes and managed-service dependencies before moving. A VPS migration may also need separate database and object-storage work.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

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.

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

Taking a Droplet apart before moving

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.

01

Attached services inventory

List volumes, managed databases, Spaces buckets, load balancers and firewalls beside each Droplet. Every item needs a destination equivalent or an export.

02

Secrets and cloud-init

Save cloud-init and user data scripts plus environment files. They hold the package list and configuration that a bare file copy misses.

03

DNS inside the account

DigitalOcean may also host the DNS zone. Capture the full zone early so DNS can move on its own schedule.

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 from DigitalOcean 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