Capture the current site
Export files, database, DNS records, email setup, certificates, scheduled jobs and integration secrets. Store at least one independent backup.
Ormaven Guides · Migration checklist · 2026-10-08
A hosting migration is a process, not a change of logo. Protect the working version first, then test the new environment before switching traffic.
A decision checklist based on provider documentation and public guidance. We did not personally test or purchase the listed services.
Export files, database, DNS records, email setup, certificates, scheduled jobs and integration secrets. Store at least one independent backup.
Use the new host’s staging or preview option. Test all routes, forms, logins and checkout in a non-production environment.
Provider migration help may not include mailbox contents, DNS entries, cron jobs or custom settings. Assign each task explicitly.
Schedule a change window, validate SSL, redirects and uptime, then keep the previous environment available until confirmation.
Hypothetical inputs to demonstrate a formula; they are not actual Hostinger or SiteGround prices. Add domain, mailboxes and migration labor where applicable.
Verify the current price, exact features and exclusions with the provider before purchasing.
Verify terms Official siteVerify the current price, exact features and exclusions with the provider before purchasing.
Verify terms Official siteLinks marked Partner link may earn Ormaven a commission. Inactive partnerships lead to the provider's ordinary official site. How partner links work.
No universal guarantee. Good preparation reduces risk, but DNS caching and complex applications can still cause disruption.
Not necessarily; check scope. Some migration services explicitly exclude email.
After the new site, emails, redirects and backups have all been verified.
No firsthand testing is claimed. Example prices are illustrative rather than live quotes.