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 OVHcloud

Move from OVHcloud to DotMoose

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

Compare the services for your project.

Your requirements

What does your project need?

01

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.

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

Separating OVHcloud services before traffic moves

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.

01

Additional IP list

Record every additional address routed to the server and what uses it. Sites, mail and VPNs bound to those addresses need a plan each.

02

Hardware assumptions check

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.

03

Failover address timing

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

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