For most small sites, a host migration service or a migration plugin works best. Large or complex sites often need manual transfer of files plus database for full control. Migration means copying WordPress files and the database to a new host or new address.
Hostinger lists these three as the standard approaches, with choice depending on size and control, in its migration guide. Plan the move before touching DNS so visitors keep seeing the live site. Test the new copy first, then switch traffic once pages, forms, and links work.
Table of Contents
- Should you let your host move the site?
- What do migration plugins do well?
- When is manual migration worth the effort?
- How do you avoid downtime and broken links?
Should you let your host move the site?
Hostinger calls host-handled migration the easiest path for owners. The provider team moves the site while the original stays live. That setup lowers downtime risk during the switch.
Choose this route when you lack time or server access. A freelancer handing off a brochure site is a good fit. Marketing teams also gain because ads and search traffic keep landing on a live site.
What do migration plugins do well?
Plugins suit do-it-yourself moves without server work. They bundle posts, settings, themes, plugins, and uploads into one import file. Serialized data means settings stored in a coded format that breaks if edited by hand.
SiteOrigin explains that All-in-One WP Migration also replaces the old address, even in coded serialized data, in its site-moving basics. Upload caps are the main limit. SiteOrigin notes imports often fail near 512MB on shared hosts. Ask the host to raise the cap, or switch to a Duplicator-style installer or manual transfer for large media libraries.
When is manual migration worth the effort?
Manual moves fit developers who want full control. Learn WordPress describes the core flow as copy files, move database, then reconnect. Copy files by FTP or file manager.
Export the old database in phpMyAdmin, create a new database, import the file, then update wp-config.php and match the table prefix. Use manual transfer for very large sites or strict server setups. Plugin archives that exceed the upload cap are a clear signal. The extra steps pay off when you must control prefixes, credentials, and file placement.
How do you avoid downtime and broken links?
Address changes need database cleanup. Changing domains or moving from HTTP to HTTPS leaves old links in posts and settings. Developer.WordPress.org recommends wp search-replace because it handles serialized data safely and offers –dry-run previews, in its search-replace command reference.
FastCow advises backup first, testing on the new host before switching DNS, and lowering DNS TTL in advance, in its migration walkthrough. FastCow notes re-saving permalinks plus clearing cache fixes the common homepage-ok with inner-page-404 error. Test three inner pages and one form after the switch.
- Back up files and database and keep a copy off the new host.
- Build on a temporary address and click through pages, forms, and checkout.
- Lower DNS TTL, switch DNS, then re-save permalinks and clear cache.
