Moving a website to a new hosting provider means copying the website to a new server, testing it there, and then pointing the domain to the new location. The risky part is not only the copy. It is keeping files, databases, DNS, email, SSL, forms, and redirects lined up.
For a small business website, a migration should be treated like a controlled handoff rather than a last-minute switch.
WordPress sites usually include files and a database. The files include WordPress core files, themes, plugins, uploads, and configuration files. The database includes pages, posts, users, menus, settings, form data, and many plugin settings.
If you copy only the files, a typical WordPress site will not be complete.
Make a Full Backup First
Before you move anything, create a backup of the current site.
For WordPress, make sure the backup includes:
Website files
Database
Uploads
Themes
Plugins
Configuration files such as wp-config.php
Any custom files or folders
Store the backup somewhere separate from the hosting account if possible. If something goes wrong during the move, you need a way back.
Record the Current Setup
Write down the current site details before changing anything.
Capture:
Current hosting provider
Domain registrar
Active nameservers
DNS records
PHP version
Database name and user
WordPress version
Active theme
Active plugins
Permalink settings
SSL status
Email provider
Priority redirects
Cron jobs or scheduled tasks
This list helps you rebuild or troubleshoot the site if the new hosting environment behaves differently.
Set Up the New Hosting
Prepare the new hosting before pointing the domain.
Depending on the website, this may include:
Creating the hosting account
Adding the domain
Creating a database
Uploading website files
Importing the database
Updating configuration files
Matching the PHP version or choosing a newer supported version
Installing SSL
Setting up any required redirects
For WordPress, the database details in wp-config.php must match the database on the new host. If the database name, username, password, or host value is wrong, WordPress may show a database connection error.
Test Before Changing DNS
Do not point the live domain until the new copy has been tested.
Use a temporary URL, staging URL, hosts file, or preview method if available.
Test:
Homepage
Main pages
Menus
Forms
Login page
Checkout or booking flow
Search
Images
Downloads
Mobile layout
HTTPS
Redirects
Admin dashboard
If the site has ecommerce, bookings, memberships, or customer submissions, plan the final copy carefully so new orders or entries do not get left behind on the old host.
Plan the DNS Switch
The DNS switch sends visitors to the new hosting location.
Before switching, confirm:
The new site works
The new hosting IP or nameservers are correct
Email DNS records are copied if nameservers are changing
SSL is ready or can be issued after DNS points correctly
The old host will stay active during the transition
Someone is available to test after the switch
If you change nameservers, all DNS records may need to move, including email records. Website migrations often break email when MX, SPF, DKIM, or DMARC records are forgotten.
Watch for URL and Path Changes
If the domain stays the same, the migration may be simpler. If the domain, subdomain, folder path, or protocol changes, links inside the site may need updating.
WordPress stores URLs in the database. A careless database search and replace can break serialized data used by themes, widgets, and plugins.
Use tools that understand WordPress data structures, or ask someone experienced to handle it.
Keep the Old Hosting Temporarily
Do not cancel the old hosting as soon as the domain points to the new one.
Keep it active long enough to:
Confirm DNS has settled
Check forms and emails
Compare missing files
Retrieve logs or backups
Capture anything that changed during the move
Roll back if needed
How long you keep it depends on the site and risk level, but shutting it down immediately is rarely wise.
Test After the Move
After the DNS switch, test again from outside your normal browser.
Check:
www and non-www
HTTP and HTTPS
Contact forms
Email notifications
Checkout or bookings
Login pages
Search results that lead to old URLs
Sitemap
Analytics and tracking
Page speed
Ask someone on a different network to test too.
After the Migration
Update records and notes:
New hosting login location
New DNS provider
New server IP, if relevant
New backup routine
PHP version
SSL renewal status
Any changed redirects
Any unresolved issues
For a WordPress site, Tech Help Canada’s WordPress maintenance page is a useful related resource because migration work should lead into an ongoing update, backup, and monitoring routine.
We empower people to succeed through practical business information and essential services. If you’re looking for help with SEO, copywriting, or getting your online presence set up properly, you’re in the right place. If this piece helped, feel free to share it with someone who’d get value from it. Do you need help with something? Contact Us
Want a heads-up once a week whenever a new article drops?
