Managed WordPress hosting for sites leaving Krystal.
Krystal runs two quite different platforms, and UK customers often chose them for where the servers are. Both facts have to be settled before a migration is planned.
Which Krystal product you are on decides the route.
Their traditional hosting and their newer platform export differently, and assuming the wrong one wastes the first attempt.
cPanel plans or the newer platform
One hands over a familiar archive; the other does not. Establishing which you are on is the first step rather than a detail discovered mid-export.
UK residency, if that is why you chose them
Krystal host in the UK and say so loudly. If that was the reason, the replacement origin is chosen deliberately rather than left to a default.
Platform caching that stays behind
Caching applied by their stack is not a plugin you can carry, so anything it was doing is rebuilt here rather than assumed to continue.
Accounts holding more than one site
A single plan often carries several domains, so what is moving and what is staying is settled before an export is scoped.
Their backups, checked not assumed
Confirm what your plan retains and how far back before you rely on it during a move. It is a cheap check and an expensive omission.
Settle the platform and the region first.
Both questions are quick to answer and both change the plan. Neither is pleasant to discover halfway through a cutover.
- Krystal platform identified before the export
- UK origin chosen if residency matters
- Sites in the account enumerated
- Platform caching rebuilt in-stack
Close to your audience, without the guesswork.
A UK site served from a UK origin behind an edge is the arrangement most Krystal customers already wanted. What changes is the tuning around it.
What we change when a site arrives from Krystal
Two decisions up front, then the usual work of replacing platform features with stack features.
| Setting | What we do | Why |
|---|---|---|
| Platform identification | cPanel plan or newer platform established before the export begins | Krystal run both, and only one of them hands over a restorable archive — planning around the wrong assumption means starting the export twice. |
| Origin region | UK origin selected explicitly when residency was the reason | Their UK hosting is a large part of why customers choose them, and accepting a default region silently discards exactly what was being paid for. |
| Platform caching | Rebuilt in-stack ahead of cutover | Caching applied by their stack installs nothing in WordPress, so there is no plugin to carry and the speed does not travel with the files. |
| Account contents | Every domain on the plan listed before the scope is fixed | One plan commonly carries several sites, so an export scoped to the account rather than the site picks up ones that were staying. |
| Backup expectations | Retention confirmed rather than assumed during the move | A migration is exactly when people reach for a backup they have never tested, and the coverage is worth knowing before it matters rather than after. |
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.
Which Krystal platform am I on?
I chose Krystal because they host in the UK. Can I keep that?
Will the site be as fast after moving?
My plan has several websites on it. Can I move one?
Can I rely on Krystal's backups during the migration?
Stay in the UK, change the stack.
Free migration, the right platform route chosen first, and a UK origin if that is why you were there.