WordPress hosting for sites leaving Hostinger.
Hostinger runs hPanel rather than cPanel and LiteSpeed rather than Apache, so the two things most migration guides assume are both absent.
What a Hostinger site brings with it.
Two assumptions break on this move: that there is a cPanel backup, and that the caching plugin will keep working.
A cache plugin with nothing to talk to
LiteSpeed Cache issues instructions to a LiteSpeed server. On any other stack it is a plugin talking to something that is not there, and the site quietly stops caching.
hPanel, not cPanel
The standard cPanel backup route does not exist, so the export is done differently. Worth knowing before you go looking for a button that is not there.
CDN URLs saved into content
Rewritten asset URLs persist in the database after the account closes, so each one is repointed at your own domain.
Panel-written .htaccess
hPanel writes its own cache and redirect directives into .htaccess. Those are read and reimplemented rather than carried into a stack that reads them differently.
Mail on the same plan
Hostinger plans commonly bundle email on the domain, so the MX position is settled before the DNS change rather than after.
Exported the way the panel allows.
The first hour of a Hostinger migration is usually spent discovering the export route is not the one the guide assumed. We start from the right one.
- Export route confirmed for hPanel before starting
- Staged copy on a temporary domain for review
- Cutover at a time you choose
- Old host left running until you confirm
Caching that engages again.
A site whose cache plugin lost its server looks like a hosting downgrade. It is a leftover plugin, and removing it is the difference.
What we change when a site arrives from Hostinger
These are the specific things this move needs, and they follow from a different panel and a different web server.
| Setting | What we do | Why |
|---|---|---|
| LiteSpeed Cache plugin | Removed, with caching rebuilt at our edge | The plugin issues instructions to a LiteSpeed server; without one it is overhead that also stops anything else caching properly. |
| Export route | Planned for hPanel rather than cPanel | The cPanel backup path most guides assume simply does not exist here, and discovering that mid-migration costs a day. |
| CDN asset URLs | Rewritten to your own domain across the database | Rewritten URLs are saved into content over time and outlive the account that served them. |
| Panel-written .htaccess | Read and reimplemented rather than copied | hPanel adds cache and redirect directives you did not write, and they behave differently on a stack that is not LiteSpeed. |
| MX position agreed before the DNS change | Email is commonly bundled on the same plan, so moving the domain takes the mailboxes unless that is decided first. |
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.
Will my LiteSpeed Cache plugin keep working?
Hostinger uses hPanel. Does that change the export?
What happens to images served through their CDN?
I have email on my Hostinger plan. Will it break?
Is there any downtime during the switch?
Leave Hostinger with caching that still works.
Free migration planned for hPanel, the orphaned cache plugin removed, and CDN URLs brought home.