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.
Migrate from Vultr
Inventory your Vultr instance, disks, firewall rules and application data. Plan new network settings and a tested cutover.
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 Vultr by documenting instance disks, block storage, firewall rules, DNS, reserved addressing, startup configuration, backups or snapshots, and any provider-specific network assumptions.
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 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.
Copy the startup script and any cloud config out of the account. It documents packages and setup steps the disk copy hides.
Confirm whether application data lives on the boot disk or attached block storage. Each volume gets its own copy and mount check.
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
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.