Migrating your website to another hosting provider sounds like a risky operation. But with the right approach it is surprisingly easy, and you can do it without downtime. Read more about an affordable website.

Why do people switch hosting?

• Better price: You are paying too much for what you get
• Slow website: Your current hosting is not fast enough
• Poor support: You do not get help when you need it
• Downtime: Your site is offline too often
• More features: Your new host offers what your current one does not
• Consolidation: Bringing everything together with one provider

Preparation: what do you need?

• Access to your current hosting: FTP or control panel login
• Database details: If you use a CMS such as WordPress
• Access to your domain management: To change DNS
• Your new hosting account: Already created and ready

Step-by-step plan to migrate a website

Step 1: Make a backup

This is the most important step. Make a complete backup of:

• All files: Via FTP or File Manager
• The database: Via phpMyAdmin (export as .sql)
• Emails: If you want to keep them

Keep this backup locally on your computer. That way you can always go back if something goes wrong. Read more about a .website domain name.

Step 2: Prepare your new hosting

At your new provider:

1. Add your domain (without changing DNS yet)
2. Create a new database
3. Note the database details (name, user, password)

Step 3: Upload your files

Transfer all files to your new hosting via FTP or the File Manager. This can take a while for large sites.

Tip: Upload as a .zip and unpack it on the server, that is much faster.

Step 4: Import the database

Go to phpMyAdmin on your new hosting and import your .sql backup. Then adjust the configuration (for example wp-config.php for WordPress) with the new database details.

Step 5: Test via the hosts file

You can test your site before you change DNS by adjusting your local hosts file:

1. Find the IP address of your new hosting
2. Add to hosts: 123.456.789.0 yourdomain.nl
3. View your site, only you see the new version
4. Remove the line again when you are done testing

Step 6: Change the DNS

Once everything works on the new hosting:

1. Log in to your domain manager
2. Change the nameservers or the A record to your new hosting
3. Wait for DNS to propagate (up to 24 hours, usually faster)

Step 7: Check everything

After the DNS change:

• Test all pages
• Check forms
• Check whether email works
• Check whether SSL/HTTPS is active

Migrating a WordPress website

• Plugins: All-in-One WP Migration, Duplicator or UpdraftPlus
• Managed migration: Many hosts do it for you for free

With a plugin you create a complete package that you install on the new host, database, files and settings all at once.

Frequently asked questions

How long does a website migration take?

The migration itself can be done in an hour. DNS propagation takes up to 24 hours, but it is often sorted within a few hours.

Will my site go offline during the migration?

Not if you do it right. Your old site stays active until DNS points to the new one. At most there is a short overlap where some visitors see the old and others see the new.

Can my new host do the migration?

Many providers offer free migration. Just ask, it saves a lot of work.

Do I need to move my domain too?

Not necessarily. You can keep your domain with your current registrar and only move the hosting. It is handy to have everything with one party though. Check out our domain transfer page if you also want to move your domain.

Need help?

Migrating a website step by step

Step 1: make a complete backup

Download all files from your current hosting via FTP. Also export your database via phpMyAdmin as an SQL file. Keep this backup safe, it is your safety net if something goes wrong.

Step 2: prepare the new hosting

Activate your new hosting plan. Create a database and note the details (database name, user, password, host). Upload your files to the new server.

Step 3: import the database

Import your SQL file into the new database via phpMyAdmin. Then adjust the database settings in your configuration file (wp-config.php for WordPress).

Step 4: test via a temporary URL

Most providers offer a temporary URL to test your site before you move the domain. Check whether everything works: pages, forms, images.

Step 5: move the domain

Change the nameservers at your registrar to those of your new hosting. Or adjust the A records to the new IP address. DNS propagation takes up to 24-48 hours.

Step 6: check everything

After the DNS change: test your whole website. Check links, forms, email, and any SSL certificates.

WordPress-specific migration

Use WP-CLI or an SQL query:

UPDATE wp_options SET option_value = 'https://newdomain.nl'
WHERE option_name IN ('siteurl', 'home');

Or use a plugin like Better Search Replace to replace all old URLs.

Common problems

White page after migration

Often a database connection error. Check the database settings in wp-config.php. Watch out for the correct hostname, with some hosts this is not 'localhost'.

Images do not work

The URLs in the database still point to the old location. Use Search Replace to adjust them.

Email does not work

Do not forget to check your MX records. If your email was with the old host, you need to move that too or set the MX records correctly.

Professional migration

Checklist for your migration

• Backup made of all files and the database
• Database details of the new hosting noted
• Files uploaded to the new server
• Database imported
• Configuration file adjusted (wp-config.php)
• URLs replaced in the database
• Site tested on the temporary URL
• DNS/nameservers changed
• SSL certificate activated
• Email checked
• All pages and functions tested

A successful migration starts with good preparation. Take your time, follow the steps, and your website will soon run flawlessly on your new hosting.

Migrating a website to other hosting seems complicated, but with good preparation it is very doable. Take the time to test everything before you make the switch. Test on the new server whether all pages load properly, whether forms work and whether the database has been transferred correctly. Once everything works, you can switch the DNS with confidence.

Plan your migration carefully and do not take unnecessary risks. Better to spend a day longer preparing than a week solving problems after a rushed migration.

A successful website migration starts with a good plan and ends with thorough testing.

Moving to Theory7? We are happy to help. With many plans we offer free migration assistance. Check out our web hosting plans or get in touch, we are happy to think along with you.

Migrating a website: the complete checklist

Step	Action	When	Priority
1	Make a full backup (files + database)	1 week before	Critical
2	Activate and test new hosting	3-5 days before	High
3	Upload files via FTP/SFTP	1-2 days before	High
4	Import the database	1-2 days before	High
5	Adjust configuration (wp-config, .env)	After upload	High
6	Change DNS/nameservers	After a successful test	Critical
7	Activate SSL certificate	After DNS propagation	High
8	Cancel old hosting	2 weeks after migration	Low

Migrating a website without downtime

• Adjust the hosts file: test your website on the new server before you change DNS by adjusting your local hosts file
• Set a low TTL: lower the TTL of your DNS records to 300 seconds, at least 48 hours before the migration
• Keep the old hosting: keep your old hosting active until at least 2 weeks after the migration
• Migrate email separately: do not forget that email accounts also need to be moved if they are on the same hosting

With Theory7 web hosting we help you migrate your website for free. Our team makes sure everything goes smoothly.

Frequently asked questions about migrating a website

Will I lose my SEO positions if I migrate my website?

Not if you do it right. Make sure all URLs stay identical, 301 redirects are set up correctly, and resubmit your sitemap to Google Search Console after the migration. Temporary fluctuations are normal and recover within a few weeks.

How long does migrating a website take on average?

For an average website (WordPress, up to 5 GB) the technical process takes 1-2 hours. The total lead time including DNS propagation is 24-48 hours. Larger websites with complex databases can take longer.

Can I migrate my website without technical knowledge?

Yes, many hosting providers offer free migration help. There are also WordPress plugins such as Duplicator and All-in-One WP Migration that automate the process. When in doubt, professional help is always recommended.

Do I need to move my domain name too?

That is not necessary. You can leave your domain name with your current registrar and only change the nameservers to your new hosting provider. A domain transfer is a separate process.

Migrating a website and email migration

• IMAP vs POP3: with IMAP, emails are stored on the server. Export these before you cancel the old hosting.
• MX records: make sure the MX records point to the correct mail server after the DNS change.
• Passwords: create new email accounts on the new hosting with the same addresses.
• Outlook/Thunderbird: adjust the server settings in your email client after the migration.

Plan the email migration carefully so you do not miss any messages during the transition. At Theory7 we also help you with the email migration.

Migrating a website: technical checklist

Preparation (1-2 weeks before the migration)

• Make a full backup of all files and databases
• Document your current server settings (PHP version, modules, cron jobs)
• Note all email addresses and their settings
• Lower the TTL of your DNS records to 300 seconds (5 minutes) so the switch goes faster
• Inform your team about the planned migration and possible downtime

During the migration

1. Upload all website files to the new server via FTP or SSH
2. Import the database on the new server
3. Adjust the database connection details in the configuration files
4. Test the website on the new server via the IP address or a temporary domain
5. Check all functionality: forms, shopping cart, login, search function
6. Point the DNS to the new server once everything works

Migrating a website without downtime

Method	Downtime	Complexity	Suitable for
DNS switch after a full copy	Minimal (DNS propagation)	Low	Static websites
Synchronization with rsync	Almost none	Medium	File-based sites
Database replication	None	High	Dynamic websites
Load balancer migration	None	High	Large applications

Understanding DNS propagation

After changing your DNS records it takes some time before all internet providers have the new data. This is called DNS propagation and can take 1 to 48 hours, although with a low TTL it is usually completed within a few hours. During this period some visitors still see the old server. That is why you should keep both servers active until propagation is fully complete.

Common mistakes when migrating a website

• Not making a backup - Always make a full backup before you start. Also test whether the backup actually works by restoring it in a test environment.
• Forgetting email - If your domain is also used for email, do not forget to move the email accounts and messages along.
• Hardcoded URLs in the database - WordPress and other CMSes store full URLs in the database. Use a search-and-replace tool to update these after the migration.
• Not renewing the SSL certificate - Your current SSL certificate may not work on the new server. Arrange a new certificate before you change the DNS.
• Cancelling the old server too soon - Keep the old server active for at least two weeks after the DNS change as a fallback.

With good preparation and this checklist you can migrate your website safely and with minimal downtime to a new hosting environment.

Migrating a website: special considerations per CMS

For WordPress websites it is crucial to update all URLs in the database. WordPress stores full URLs in serialized data, which means a simple search-and-replace in the database is not enough. Use tools such as WP-CLI or the Search Replace DB script that handle serialized data correctly. Also do not forget to update the wp-config.php with the new database details and siteurl.

Joomla websites store configuration in the configuration.php file. After the migration you need to update the path to the tmp and log folders, as well as the database settings. Joomla also has a built-in migration assistant that guides you through the process when upgrading to a new version.

For Magento web shops the migration is more complex because of the larger database and the number of dependencies. Always test the migration first on a staging environment and plan the switch outside peak hours. Magento requires that after the migration you clear all caches, run the indexer again and regenerate the static content.

Regardless of which CMS you use, always test all functionality thoroughly after the migration: forms, search function, checkout processes and user registrations. Draw up a checklist specific to your CMS and go through it systematically. Keep your old hosting active for at least two weeks as a safety net in case unexpected problems arise.

Migrating a website: summary and timeline

Two weeks before the migration: make a full backup, document your current settings, lower the DNS TTL and inform your team. One week before the migration: transfer files and database to the new server, test extensively on the new environment and prepare your DNS change. On the day of the migration: point DNS to the new server, check website and email, and monitor for problems. The first week after the migration: keep both servers active, check all functionality daily and solve any problems right away. After two weeks: verify that DNS propagation is fully complete, make a final backup of the old server and cancel the old hosting. With this structured approach you minimize risks and ensure a flawless transition to your new hosting environment.

Migrating a website: the benefits of good preparation

After the migration: monitoring and optimization

The work does not stop once your website migration is complete. The first 48 hours after the switch are crucial for monitoring problems. Check all pages for correct functioning, test forms, ordering processes and login functions. Verify that all images and downloads load correctly and that internal links point to the right pages. Monitor your web server log files for 404 errors that may indicate missing files or incorrect redirects. Keep an eye on the loading times with tools such as Google PageSpeed Insights and compare these with the measurements you took before the migration. If you detect performance problems, adjust the server configuration: increase the PHP memory limit, activate OPcache or optimize the database configuration.