Moving a WordPress site to a new hosting provider in Europe is usually straightforward if you plan the cutover carefully and keep DNS, database, and file changes under control. The main goal is to move the site with minimal downtime, preserve email and SSL settings where needed, and avoid broken links, missing media, or database connection issues after the switch.
In a typical managed hosting environment, the process involves exporting the WordPress files and database from the old host, importing them to the new account, updating configuration details, and then changing DNS so visitors start reaching the new server. If you use a control panel such as Plesk, many of these tasks can be handled from a single interface, which makes the migration safer and easier to verify.
What you need before starting the migration
Before moving a WordPress site, collect the access details and confirm the scope of the migration. This helps you avoid surprises during the final switch.
- WordPress admin access
- Hosting control panel access on both old and new providers, such as Plesk
- SFTP or FTP access for file transfer
- Database credentials for the current WordPress database
- Access to DNS management for the domain
- Information about email services if the domain also uses hosted mailboxes
- A current backup of both files and database
It is also useful to check whether the site uses caching plugins, a CDN, security plugins, custom cron jobs, or integrations with external services. These can continue to work after migration, but only if their settings are reviewed during the move.
Choose the migration method that fits your setup
There are several ways to move a WordPress site to a new hosting provider in Europe. The best option depends on site size, technical experience, and whether the hosting platform offers migration tools.
Manual migration
Manual migration is the most flexible method. You copy the WordPress files, export the database, create a new database on the target server, and update the wp-config.php file. This approach is often preferred when you need full control over the process or when automated tools are not available.
Plugin-based migration
Migration plugins can package your site into a single archive or copy the entire installation to the new host. This is convenient for smaller sites, but large sites may hit upload limits or timeouts. Some plugins also need temporary higher PHP limits on the destination server.
Hosting provider migration service
Many managed hosting providers offer a migration service or assisted onboarding. This is the easiest option if you want the provider to handle file transfers, database import, and basic checks. It is especially useful when moving a production site where downtime must stay low.
Step 1: Prepare the WordPress site on the old host
Start by reducing the risk of losing recent content during the transfer. If the site has frequent orders, comments, or form submissions, schedule the migration during a quieter period.
- Update WordPress core, themes, and plugins if possible
- Remove unused plugins and themes
- Clear cache and temporary files
- Check for known database or plugin errors
- Record custom settings, cron jobs, and redirects
If the website is active, consider placing it in maintenance mode only at the final cutover stage, not during the whole migration. That way, the content remains available while you prepare the new environment.
Step 2: Back up files and database
A complete backup is essential, even if you use a migration tool. The backup protects you if the transfer fails or if you need to roll back after DNS propagation.
Back up WordPress files
Download the full WordPress directory, including:
- wp-content folder
- wp-config.php
- .htaccess file on Apache-based hosting, if present
- Any custom files outside the standard WordPress folders
The wp-content folder is especially important because it contains themes, plugins, uploads, and often custom code.
Export the database
Export the database using phpMyAdmin, the hosting control panel, or a database tool. Use a format compatible with MySQL or MariaDB import on the new host. If the database is large, make sure the export completes successfully and is not truncated.
For larger sites, a compressed export can save time and reduce the chance of transfer issues.
Step 3: Set up the new hosting account in Europe
On the new hosting platform, create the target environment before moving the site. This usually includes the domain, database, and PHP configuration.
- Add the domain or subdomain in the control panel
- Create a new database and database user
- Assign the user to the database with full privileges
- Check PHP version compatibility with the site
- Confirm file permissions and document root location
In managed hosting or Plesk-based environments, it is often possible to set the PHP version per site. This is useful if the old host used an older PHP release and the site needs a matching version before you update plugins or themes.
Step 4: Upload the WordPress files
Transfer the files to the new hosting account using SFTP, FTP, or the control panel file manager. If the site is large, SFTP is usually more reliable than browser-based uploads.
Make sure the files are placed in the correct document root. A common mistake is uploading WordPress into an extra nested folder, which leads to the site loading from the wrong path or not loading at all.
After upload, confirm that the following are present:
- wp-admin
- wp-includes
- wp-content
- wp-config.php
Step 5: Import the database on the new server
Import the database dump into the new database you created earlier. This step can be done through phpMyAdmin, the hosting panel, or command-line tools if available.
After import, verify that the tables were created correctly and that the table prefix matches the one used in wp-config.php. If the site uses a custom prefix instead of the default wp_, keep it exactly as it is unless you have a specific reason to change it.
Common database import issues
- File size limits in the control panel
- Timeouts during upload or import
- Wrong character encoding, especially for multilingual sites
- Missing tables because the export was incomplete
If the import fails, split the dump into smaller parts or use a command-line import method when supported by the hosting platform.
Step 6: Update wp-config.php
Once the files and database are in place, update wp-config.php with the new database details. Make sure the database name, user, password, and host are correct.
In some European hosting environments, the database host is not always localhost. It may be a hostname provided by the hosting platform, so check the control panel documentation or account details carefully.
Review additional configuration values as well:
- Table prefix
- Custom authentication keys and salts
- Any hardcoded file paths
- Debug settings, if enabled
If the old site used a temporary URL or local development domain, be ready to update site URLs after the database import.
Step 7: Update the site URL if the domain or path changes
If the domain stays the same, you may not need to change the WordPress address or site address. If the domain changes, or if the site is moved from a temporary subdomain to the live domain, update the stored URLs in the database.
You can do this safely using a search-and-replace tool that handles serialized data. A manual database edit is not recommended because it can break widgets, page builder settings, and plugin data.
Common places where URL changes may be needed include:
- WordPress general settings
- Media links in posts and pages
- Theme or page builder settings
- Hardcoded links in custom content
Step 8: Test the site before changing DNS
Testing on the new server before the DNS switch is one of the most important steps. It lets you catch issues while the old site is still live.
You can test the site using a temporary URL, hosts file mapping, or the preview feature in the hosting control panel, depending on what your provider supports.
What to test
- Homepage and key internal pages
- Login to /wp-admin
- Contact forms
- Search functionality
- Images and media loading
- Checkout flow, if it is an e-commerce site
- SSL certificate behavior
- Performance and caching
Also verify that permalinks work correctly. If pages return 404 errors, resaving the permalink settings in WordPress often refreshes the rewrite rules.
Step 9: Check SSL, caching, and security settings
After moving a WordPress site to a new hosting provider in Europe, SSL and caching settings may need adjustment. A fresh environment often requires a new certificate, new cache rules, or updated security plugin settings.
SSL certificate
Install or activate SSL for the domain on the new host. Once the certificate is active, ensure that the site uses https:// consistently. If mixed content appears, update hardcoded links or run a database search-and-replace.
Caching
If the site uses server-side cache, a plugin cache, or a CDN, clear all cache layers after migration. Old cached assets can make the site appear broken even when the new server is configured correctly.
Security and firewall rules
Some security plugins, IP restrictions, or firewall rules may need to be updated to reflect the new hosting platform or new server IP address. If the site sends email notifications through the server, check whether SMTP settings need adjustment as well.
Step 10: Change DNS and complete the cutover
When the test version looks correct, update the DNS records for the domain so traffic points to the new hosting provider. Usually, this means changing the A record, AAAA record, or nameservers, depending on how DNS is managed.
To reduce downtime, lower the DNS TTL in advance if possible. That can help changes propagate faster when the cutover happens.
Keep the old hosting account active for a short overlap period. This gives you time to catch any straggling requests and prevents email or cache-related issues during propagation.
After DNS propagation
- Verify the site opens from different networks
- Check WordPress admin login
- Confirm forms and email notifications work
- Review server logs for 404 or 500 errors
- Make sure cron tasks and scheduled posts run normally
Common problems after a WordPress migration
Even a well-planned migration can reveal issues after launch. Most problems are easy to fix once you know where to look.
Broken links or missing images
This usually means the site URLs were not updated completely, or media files were not copied to the correct wp-content/uploads path. Recheck file transfer and run a safe database search-and-replace if needed.
Database connection error
Confirm the database name, username, password, and host in wp-config.php. Also check that the database user has the correct permissions.
403 or 404 errors
These are often caused by permission problems, missing rewrite rules, or a mismatch between the web server configuration and the WordPress permalink structure.
White screen or fatal error
This may come from a plugin conflict, incompatible PHP version, or missing extension. If needed, disable plugins by renaming the plugins folder temporarily and review the PHP error logs in the control panel.
Emails are not sending
If the site previously relied on server mail settings, check SMTP configuration, sender addresses, and any DNS records such as SPF and DKIM. Managed hosting providers may require specific outgoing mail settings.
Best practices for a low-disruption migration
To move a WordPress site with minimal disruption, follow a few practical rules that reduce risk and make troubleshooting easier.
- Clone and test before switching DNS
- Do not make content changes during the final copy unless you plan for a second sync
- Keep the old host active until the new site is stable
- Document all settings, credentials, and customizations
- Use the hosting control panel to review logs, PHP settings, and database status
- Check compatibility before upgrading PHP, plugins, or themes
For larger or business-critical sites, it can be useful to schedule a final content freeze shortly before the DNS change. That way, orders, comments, and form entries do not get split between two environments.
When to use a managed hosting migration service
A managed hosting migration service is worth considering when the site has a complex setup, such as multiple domains, a large database, e-commerce, multilingual content, or custom integrations. It is also helpful if you do not want to troubleshoot database imports, rewrite rules, or SSL installation on your own.
In a Plesk-based or managed environment, support teams can often validate the migration more quickly because they can inspect the domain configuration, database mapping, PHP version, and web server logs from the same panel.
FAQ
How long does it take to move a WordPress site to a new host?
A small site can often be migrated in under an hour, but testing, DNS propagation, and fixing configuration issues can take longer. Larger or more complex sites may need several hours or a full day, especially if you are moving email, SSL, and custom integrations too.
Will my WordPress site go offline during migration?
Not necessarily. If you copy the site first, test it on the new host, and then switch DNS, downtime can be very short. The main risk comes from content changes made after the initial copy but before the cutover.
Can I migrate WordPress without a plugin?
Yes. Manual migration is fully possible and often preferred for control and reliability. You only need access to the files, database, and new hosting account.
Do I need to change my domain name to move hosting?
No. In most cases, the domain stays the same and only the DNS records change so the domain points to the new hosting provider.
What if my site uses WooCommerce or another e-commerce plugin?
Plan the migration carefully and avoid moving during peak sales hours. After the move, test checkout, payment gateways, order emails, and tax settings. For active stores, a short content freeze before DNS change is usually recommended.
Should I keep the old hosting account after the move?
Yes, at least for a short period. Keeping it active helps during DNS propagation and gives you a fallback if something was missed during the migration.
How do I know the migration is complete?
The migration is complete when the site loads correctly on the new host, the database works, forms and logins function, SSL is active, and DNS points consistently to the new provider from the locations you check.
Conclusion
Moving a WordPress site to a new hosting provider in Europe is mostly about preparation, verification, and timing. If you back up everything, copy files and database carefully, test the site before DNS changes, and review SSL, caching, and email settings, you can complete the migration with minimal disruption.
For most sites, a controlled move through a hosting control panel such as Plesk makes the process easier to manage. For more complex websites, using a managed migration service can save time and reduce the chance of errors. In both cases, the key is to test thoroughly before cutover and keep the old environment available until the new one is stable.