Moving a WordPress site feels risky when the site takes payments, leads, or church/school updates every day. The fear is real: broken permalinks, missing uploads, email that stops, or a DNS change that leaves half the country on the old server. HostPawa offers free WordPress migration so switching hosts is an operations task—not a rebuild.
This article explains how our free migration works, what you prepare, how cutover happens, and how to start via website migration or switch to HostPawa.
What “free migration” includes
For eligible hosting orders, we move your existing WordPress site onto HostPawa: files, database, and the usual rewrites so the site runs on the new account. The goal is a working WordPress site on your new plan—theme, plugins, and media included—ready for you to verify before DNS points the world at us.
Migration is not a redesign, SEO overhaul, or custom plugin development project. If the old site was already broken, we may need WordPress hosting plus repair work rather than a blind copy of a failing stack. Tell us upfront if the site currently shows critical errors.
What we need from you
- Your domain name and whether DNS is at the registrar, Cloudflare, or another host
- Temporary login to the current host (or SFTP + database access) and wp-admin when available
- Confirmation of what must move: primary site only, or addon domains / subsites
- Any non-WordPress apps on the same account you also need moved
- A preferred maintenance window if you run flash sales or Sunday live streams
- Whether email is hosted with the current provider (email cutover is planned separately from the website)
If you cannot get old-host access, say so early—we will outline alternatives (backup upload, All-in-One style exports, or vendor assistance).
Our migration workflow
1. Provision the HostPawa account
You order a suitable WordPress hosting plan. We prepare the account, PHP version appropriate for modern WordPress, and SSL readiness for the domain.
2. Copy files and database
We pull a consistent copy of wp-content, core files as needed, and the MySQL/MariaDB database from the source. For large media libraries, we allow extra time so uploads are not half-synced.
3. Search-replace and configuration
Serialized WordPress data is updated carefully for the new environment. We align wp-config.php database credentials, adjust for the staging hostname used for testing, and check that critical paths (uploads, caches) resolve.
4. Test on a temporary URL
Before DNS changes, you review the site on a test hostname: home page, inner pages, forms, login, checkout if applicable, and a sample of blog or product URLs. This is the moment to catch plugin license re-activations or absolute links that still point at the old host.
5. DNS cutover
When you approve, we help you point the domain to HostPawa (A/CNAME or nameservers, depending on your setup). Propagation is not instant worldwide; we plan for TTL and ask you not to make conflicting DNS edits mid-cutover.
6. Post-move checks
After cutover we recheck SSL, permalinks, wp-admin, and caching. You should place a test order or form submission on the live domain. We remain available if something odd appears only after real traffic returns.
Downtime: what to expect
Done properly, website downtime is minimal—often just the DNS overlap window where some users still hit the old server. That is why we finish testing on a temporary URL first. Avoid editing content on the old site after the final copy unless you coordinate a re-sync; otherwise new blog posts can be left behind.
Email is the usual surprise. If MX records still point at the old host, web migration alone will not move mailboxes. We clarify email hosting before nameserver changes so messages do not bounce during a brand relaunch.
Nigeria-aware tips for a smooth switch
- Paystack/Flutterwave webhooks: Update callback URLs if they were hard-coded to a temporary domain during testing.
- WhatsApp and pixel plugins: Confirm tracking still fires on the live domain after SSL is active.
- Mobile QA: Test on Android Chrome over mobile data; many issues only show outside office Wi-Fi.
- Agency clients: Keep the client’s registrar login handy; DNS delays are often access delays, not technical mystery.
When migration needs extra care
Multisite, very large media libraries, heavily customised checkouts, or sites with multiple connected subdomains need a clearer inventory. WooCommerce stores should schedule cutover outside peak sales. If the old host is already unstable, we may recommend a backup-first approach and a freeze on plugin updates until the move completes.
How to start
- Pick a WordPress-capable plan on WordPress hosting.
- Open a migration request via website migration or the broader switch to HostPawa path.
- Send credentials through a secure channel—never paste passwords in public tickets if a safer vault option is offered.
- Approve the test site, then authorise DNS cutover.
- If anything looks wrong after go-live, contact us with screenshots, URLs, and the time you noticed the issue.
What you still own after the move
You keep full ownership of content, themes, and plugins. HostPawa runs the hosting platform; you (or your developer) continue content edits in wp-admin as usual. We recommend enabling ongoing backups and a sensible update routine so the first month on a new host is calm, not a plugin free-for-all on day two.
Bottom line
Free WordPress migration at HostPawa is a structured copy, test, and DNS cutover—not a DIY FTP weekend. You bring access and approval windows; we bring the move onto WordPress-ready hosting. Start with website migration, explore switching to HostPawa, choose a plan on WordPress hosting, and contact us if your site has special constraints we should plan for before the first file copy.