Managed WordPress hosting for sites leaving OVH.
On OVH's shared plans your files and your database are on different machines, addressed by different hostnames. That single fact shapes the whole migration.
The split that catches every OVH migration.
It is a reasonable architecture and it breaks every tool that assumes the database is on localhost.
The database is on its own server
OVH shared plans address the database by a hostname of their own rather than localhost, so a dump run over SSH on the web server reaches nothing.
EU residency you may be relying on
Plenty of OVH customers chose it for European hosting specifically. If that was the reason, the replacement origin has to be chosen deliberately rather than defaulted.
Backups worth verifying, not assuming
Check what your plan's backups actually cover and how far back they go before the migration, not after. It is the cheapest thing to confirm and the worst thing to discover late.
Their own control panel
The OVH manager is not cPanel, so there is no archive to restore. Files come over SFTP and the database over the network.
Domains and DNS in the same manager
OVH is a registrar too, and the DNS zone usually lives in the same manager as the hosting — including records that have nothing to do with the site.
Dump the database where it actually lives.
The recurring OVH mistake is treating the web server as the whole site. The files are only half of it, and the other half answers on a different hostname.
- Database dumped from its own host, not the web server
- EU origin chosen deliberately if residency matters
- Full DNS zone captured from the manager
- OVH plan left running until you confirm
The database stops being a network hop.
A separate database server means every query crosses a network. Here the database sits beside the site, which is most of the difference on an uncached page.
What we change when a site arrives from OVH
The split architecture drives the export, and residency drives where the site lands.
| Setting | What we do | Why |
|---|---|---|
| Database export | Dumped from OVH's database hostname over the network | Their shared plans put the database on a separate server, so the usual dump over SSH on the web host finds no database there to export. |
| Database locality | Site and database placed on the same machine | Every query on the old plan crossed a network to another server, which is a fixed cost per query that no amount of page caching removes. |
| Origin region | EU origin chosen explicitly when residency was the reason for OVH | Customers frequently pick them for European hosting specifically, and inheriting a default region quietly discards the thing they were paying for. |
| Export route | SFTP for files, since the manager produces no restorable archive | The OVH manager is not cPanel and hands over no backup file, so the copy is assembled rather than restored. |
| DNS zone | Captured whole from the OVH manager before repointing | They are the registrar as well as the host, so the zone holds mail and verification records that go down with the site if only the A record is considered. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
My database dump comes back empty. Why?
I chose OVH for EU hosting. Can I keep that?
Will my site be faster after moving?
Should I trust my OVH backups for the migration?
OVH manages my domain too. Does it have to move?
Bring the database back next to the site.
Free migration, the remote database handled properly, and an EU origin if that is why you were there.