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 Vultr

Move from Vultr to DotMoose

Inventory your Vultr instance, disks, firewall rules and application data. Plan new network settings and a tested cutover.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

What needs to move

Check moving from Vultr by documenting instance disks, block storage, firewall rules, DNS, reserved addressing, startup configuration, backups or snapshots, and any provider-specific network assumptions.

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

Documenting a Vultr instance before rebuild

A Vultr instance keeps its life in a few places: the server disk, attached block storage, firewall groups, startup scripts and snapshots. Export application data directly from the running system with database dumps and file copies, and save the startup script and firewall rules as text. Snapshots help rollback, but the rebuild runs from the exports.

Reserved addresses and DNS cause the cutover surprises. A reserved IP or a Vultr DNS zone ties traffic to the old account, and applications may allowlist the old address. Capture the DNS zone, list every place the old IP appears, and plan the address change as its own step with TTLs lowered in advance and the old instance kept running.

01

Startup script saved

Copy the startup script and any cloud config out of the account. It documents packages and setup steps the disk copy hides.

02

Block storage check

Confirm whether application data lives on the boot disk or attached block storage. Each volume gets its own copy and mount check.

03

Snapshot before shutdown

Take a final snapshot while the instance still runs. It stays in the old account as the rollback copy until the new server is proven.

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 Vultr 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