Managed WordPress hosting for sites leaving 20i and StackCP.
20i organises hosting into packages rather than accounts, and a single package often holds several unrelated sites. Working out what belongs to whom comes before anything is copied.
One login can hold a lot more than one site.
This is the part that makes a 20i migration different: the unit you are leaving is rarely a single website.
StackCP packages hold several sites
A package can carry multiple domains and WordPress installs side by side. Which of them are moving, and which stay, is decided before the first export.
Reseller accounts hold clients
If the account is a reseller one, some sites belong to customers who have their own logins and their own expectations about downtime. Those get their own cutover conversation.
StackCache does not come with you
20i's bundled caching is applied at their edge, not by a plugin you can carry. Anything it was doing has to be reproduced here rather than assumed to continue.
Their CDN and DNS in front
Packages frequently use 20i's own nameservers and CDN, so DNS is managed inside StackCP rather than at the registrar — which changes where the cutover actually happens.
Databases shared across a package
Several sites in one package can share a database server and naming scheme, so exports have to be separated carefully to avoid carrying a neighbour's tables.
Separate the sites before you move any of them.
The failure here is not a lost file. It is discovering mid-migration that the package you exported contained three sites, two of which belong to somebody else.
- Every site in the package listed
- Reseller clients identified and scheduled separately
- DNS location established — StackCP or registrar
- Databases separated per site
Resources per site, not per package.
Sites sharing a package share its limits, so a busy neighbour is your problem too. Here each site has its own container and its own ceiling.
What we change when a site arrives from 20i
The package model drives most of this, and their edge features drive the rest.
| Setting | What we do | Why |
|---|---|---|
| Package contents | Every domain and install inside the package listed before an export is scoped | 20i's unit of hosting is a package rather than a site, so exporting one without an inventory routinely picks up a neighbouring site's files as well. |
| Reseller clients | Client-owned sites identified and given their own cutover slot | A reseller package holds sites whose owners have their own logins and their own tolerance for downtime, and scheduling them as one batch decides that for them. |
| StackCache | Edge caching reproduced in-stack rather than carried | 20i applies it at their own edge with no plugin to bring along, so a site that felt fast there arrives with none of that unless it is rebuilt here. |
| DNS ownership | Established as StackCP or registrar before the cutover is planned | Packages often use 20i's nameservers, which means the records to change live inside the panel you are leaving rather than at the registrar. |
| Database separation | Per-site exports taken from a shared database server | Sites in one package share a database host and naming convention, so an unfiltered dump carries tables belonging to a site that is not moving. |
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 20i package has several sites. Can I move just one?
I am a reseller. What about my clients' sites?
Does StackCache come with me?
Where do I change DNS — 20i or my registrar?
Will my other sites be affected while one moves?
Move one site without disturbing the rest.
Free migration, the package inventoried first, and a cutover slot per site.