Post actualizado el día octubre 25, 2026 by DeiviSanzPlay
Moving a WordPress website from one hosting provider to another isn’t witchcraft, but it’s not just pressing a button and crossing your fingers either. If you do it wrong, you can take the site down for hours, lose orders, or destroy the SEO you’ve worked so hard for. I’ll tell you from the trenches, without embellishment and with the steps that really matter in how to migrate WordPress to another hosting in 2026.
Before touching anything: backup and plan B
90% of migration disasters come from skipping this step. Make a complete backup of files and database before moving a single finger. If you use UpdraftPlus, All-in-One WP Migration, or Duplicator, run them and download the package to your computer, don’t leave it only on the old server.
I always make two copies: one on the old hosting and one locally. It sounds paranoid, but when something fails at 2 in the morning, you’re grateful to have that .wpress or .zip file on hand. No backup, no migration, period.
The two real paths: manual or with a plugin
There’s no middle ground here. Either you get your hands dirty or you delegate to a plugin. Each option has its moment and its profile.
Manual migration: total control, total risk
Download via FTP (FileZilla, for example) the entire WordPress folder, including wp-content, plugins, themes, and uploads. Then export the database from phpMyAdmin into a .sql file.
On the new hosting, create a database and a user with all privileges. Upload the files to the public root (usually public_html) and import the .sql. Edit wp-config.php with the new connection details: database name, user, password, and host.
This method gives you absolute control, but any forgotten file or a badly exported table leaves the site blank. If you don’t have experience with SSH or phpMyAdmin, better not start here.
Plugin migration: the fast track (and the one I use 80% of the time)
Install All-in-One WP Migration or Duplicator on the old WordPress, generate the package, and download it. On the new hosting, install a clean WordPress, upload the same plugin, and import the file.
The plugin takes care of rewriting URLs, serializing data, and moving everything without you having to touch the database. Watch out for the upload limit: if your site weighs more than 300 MB, you’ll have to increase upload_max_filesize or use the paid version. It’s the price of convenience.
The database: the soul of your WordPress
If the database isn’t properly configured, WordPress won’t start. It doesn’t matter how beautiful your theme is. Check in wp-config.php that the DB_HOST is correct (sometimes it’s not localhost, but an IP or a name like mysql.yourhosting.com).
A classic mistake is forgetting to change the table prefix if the new hosting uses a different one. Another: not updating the URLs in the wp_options table (siteurl and home). If you don’t, the site redirects to the old domain and appears broken.
URLs, permalinks, and details that kill
After importing, go to Settings > Permalinks and save the changes without touching anything. That regenerates the rewrite rules and prevents the dreaded 404 on posts.
Run a scan with a plugin like Better Search Replace to change any trace of the old domain to the new one. Also check the widgets, menus, and the .htaccess file if you used custom rules.
Click all over the site: home, posts, pages, forms, images. If something fails, better you discover it than a visitor.
DNS: the final leap (and the one that generates the most impatience)
When everything works on the new hosting, change the DNS records at your domain provider. Point the A record to the new server’s IP or change the nameservers if they ask you to.
Propagation can take from minutes to 48 hours. Meanwhile, you can test the new site by adding the IP and domain to your computer’s hosts file. That way you see the result without waiting.
Mistakes I’ve seen (and made) in WordPress migrations
- Not disabling cache plugins before migrating: you carry over absolute paths and the site shows old versions.
- Forgetting the uploads files: images appear broken because you only moved the database.
- Not changing the security keys in wp-config.php: you leave the door open to attacks.
- Migrating with the old hosting expired: if the domain no longer resolves, the export fails.
Another classic: doing the migration at peak time. If you have traffic, schedule the DNS change for the early hours or notify your users. A site down for hours shows up on Google.
Final checklist before saying goodbye to the old hosting
Check that the SSL certificate works on the new server (Let’s Encrypt usually installs itself). Force HTTPS and check that there’s no mixed content.
Send an updated sitemap to Google Search Console and verify there are no crawl errors. If you use corporate email, don’t forget to migrate the MX records too or you’ll lose your emails.
And don’t cancel the old hosting until a week has passed. It’s your safety net if something goes wrong. When everything is stable, then yes, lock the door.
Migrating WordPress to another hosting isn’t difficult, it’s meticulous. With a backup, the right method, and checking the details, your site lands in its new home faster and without drama.
