Moving hosts feels risky until you treat it like a project with a checklist. Thousands of Nigerian sites switch providers every year because of pricing, support quality, payment friction, or downtime. HostPawa is built for that journey: local-friendly billing, hosting and domains in one client area, and migration help when you need it. Start with Switch to HostPawa and the detailed Website Migration page; this article expands the practical steps.
Step 0 — Decide what is moving
Inventory before you touch DNS:
- Websites and apps (including staging copies)
- Databases and which apps use which schemas
- Email (move mailboxes now, later, or keep MX elsewhere temporarily)
- Domains: stay at the current registrar first, or plan a domain transfer
- Third-party DNS (Cloudflare, etc.) versus registrar DNS
- SSL, cron jobs, and special server configs
Write down current nameservers and a rollback plan. Migrations fail less often when rollback is boring and documented.
Step 1 — Choose a HostPawa plan
Match resources to reality, not marketing fantasy. A busy WooCommerce store needs more than a five-page brochure site. Browse web hosting plans, then open an account and create the empty hosting service that will receive your files.
Step 2 — Copy files and databases
- On the old host, compress the site files or sync via SFTP/rsync.
- Export MySQL/MariaDB dumps (
mysqldumpor phpMyAdmin). - Upload files into the correct HostPawa document root.
- Create databases/users on HostPawa and import dumps.
- Update configuration with the new DB credentials and any changed paths.
If you prefer not to DIY, request help via Website Migration. Provide panel access or SFTP details only through secure channels you trust.
Step 3 — Test before DNS cutover
Use a temporary URL, hosts-file override, or staging subdomain to verify:
- Pages render and assets load
- Logins and forms work
- Checkout/payment callbacks still make sense (may need final DNS for some gateways)
- Uploads write to disk
- Cron equivalents are scheduled on the new plan
Fix issues here—not after the whole country is hitting the new IP.
Step 4 — Lower TTL and plan the cutover window
A day or two before go-live, lower DNS TTL if your DNS host allows it (e.g. 300 seconds). Pick a low-traffic window for your audience. Have both old and new hosts available during cutover.
Step 5 — Point DNS to HostPawa
- Update A/AAAA records or switch nameservers as instructed in your HostPawa panel.
- Watch propagation with multiple resolvers.
- Issue/verify SSL on the live hostnames.
- Re-test critical flows on the public domain.
Keep the old host running for a short overlap. If something catastrophic appears, you can point DNS back while you fix it.
Step 6 — Email strategy
Email is the usual surprise. Options:
- Move web first; keep MX on the old provider temporarily
- Move mailboxes to HostPawa as a second project
- Use a specialised email provider and only host the website with us
Changing MX and website DNS in the same hour without a plan is how messages get lost. Sequence them deliberately.
Step 7 — Optional domain transfer
You do not have to transfer the domain to change hosting. Hosting follows DNS; registration can stay put. When you want one invoice and one client area for everything, start a domain transfer after the site is stable. Unlock the domain, get the auth/EPP code, disable clientTransferProhibited if needed, and follow HostPawa’s transfer wizard. For .ng and other ccTLDs, allow extra time for registry processes.
Step 8 — Post-migration hygiene
- Update monitoring and uptime checks to the new IP
- Rotate passwords that were shared during migration
- Confirm backups are running on HostPawa
- Cancel the old host only after a quiet soak period (often 7 days)
- Update Google Search Console / analytics if property verification relied on old files
Agency and multi-site notes
Migrate one site end-to-end as a template, then batch the rest. Standardise a checklist in Notion/Sheets. For white-label or reseller movements, talk to HostPawa about volume via Switch to HostPawa.
Bottom line
A clean move to HostPawa is inventory → copy → test → DNS → optional domain transfer → cancel old host. Use migration assistance when you want experts on the copy/cutover, keep DNS control clear, and use domain transfer only when you are ready to consolidate. When you want the high-level pitch and next action, open Switch to HostPawa and pick a web hosting plan that fits.