What needs to move
Check moving from OVHcloud by separating VPS or dedicated-server data from Additional IP, reverse DNS, firewall, DNS, backup, private-network, and hardware-specific assumptions before changing public traffic.
Migrate from OVHcloud
Review the OVHcloud services your application depends on before moving. A new host still needs an explicit plan for data, networking and access.
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 OVHcloud by separating VPS or dedicated-server data from Additional IP, reverse DNS, firewall, DNS, backup, private-network, and hardware-specific assumptions before changing public traffic.
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
An OVHcloud setup can mix a VPS or dedicated server with services managed in the same account: additional IP addresses, reverse DNS entries, a DNS zone, backup storage and private networking between machines. Separate the list into server data and account services. Server data exports as files and database dumps, while each account service needs its own replacement arranged.
Mail breaks quietly in this move when reverse DNS is forgotten. Outgoing mail from the new server needs a reverse DNS entry that matches its sending name, and the SPF record must name the new address. Set both during destination testing, send real test messages to outside inboxes, and keep the old server live until delivery looks clean.
Record every additional address routed to the server and what uses it. Sites, mail and VPNs bound to those addresses need a plan each.
Note anything tied to the physical machine, such as mounted backup storage or private links to a second server. Those do not follow a file copy.
If an IP failover address carries the site, plan its move as a routing change with a short test window. Keep the old routing until the new one answers.
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.