WordPress hosting for sites moving off Convesio.
Convesio runs WordPress across containers with a clustered database in front of it. That architecture changes what an export even means, because there is no single server to copy.
An architecture that does not copy directly.
Most host migrations are a file copy and a database dump. This one starts by working out where the authoritative copy of each thing lives.
No single filesystem to take
The site runs across multiple containers, so uploads and anything written at runtime have to be collected from shared storage rather than pulled off one server.
A clustered database, exported consistently
Reading from a replica mid-write produces a dump that is internally inconsistent — orders present whose line items are not. The export is taken against a consistent point instead.
Platform features that are not plugins
Caching, scaling and some security behaviour are Convesio's own layer rather than something installed. Each has to be re-established here rather than migrated.
DNS and TLS planned around the cutover
Records are moved with a lowered TTL ahead of time and certificates issued before the switch, so the change is a redirect of traffic rather than an outage.
Scheduled work re-established
Anything Convesio was running on your behalf has to exist here explicitly, which is a deliberate step rather than something an import discovers for you.
Find the authoritative copy, then move once.
The risk in a containerised migration is copying a version of the site that was never the live one. Everything below is about establishing which copy is real.
- Shared storage collected, not just one container
- Database exported at a consistent point
- Platform-level features re-created explicitly
- TTL lowered before the cutover window
The same site, on a stack you can see.
Autoscaling hides a lot, including which queries were always slow. Moving to a fixed, tuned stack usually surfaces and then fixes them.
What we change moving from Convesio
These differ from a standard migration on the same plan, and each follows from the fact that the source is a distributed system rather than a server.
| Setting | What we do | Why |
|---|---|---|
| Filesystem collection | Uploads and runtime writes gathered from shared storage across containers | A containerised site has no single disk that holds everything, so copying one container's filesystem produces a site that is missing whatever was written by the others. |
| Database export | Taken as a consistent snapshot rather than a live read from a cluster member | Reading a clustered database while it is being written produces a dump where related rows disagree with each other, and the damage shows up as orders whose line items are missing rather than as an error. |
| Cache layer | Object and page caching re-established explicitly on arrival | The previous caching was part of the platform rather than something installed in the site, so nothing in the export contains it and the migrated site is slower than the original until it is rebuilt. |
| Scaling assumptions | Resource ceilings set deliberately instead of inherited from autoscaling | A site that has been silently scaled for years has never been told how much it actually uses, so the first honest measurement happens during the migration rather than before it. |
| Cutover sequencing | TTL lowered in advance and certificates issued before traffic moves | Moving records at full TTL means some visitors continue reaching the old platform for hours after it stopped being authoritative, which produces orders written to a site nobody is watching. |
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.
Why can't I just download a backup from Convesio and restore it?
Will I lose the autoscaling?
What happens to Convesio's built-in caching?
How much downtime is there?
Is the migration free?
Move off Convesio without guessing which copy is live.
Free migration, a consistent database export, and caching rebuilt on arrival.