2 Geeks Web Design
How to Migrate Your Website to a New Host Safely
Moving a website from one hosting provider to another can improve speed, reliability, storage, support, or monthly cost. It can also create avoidable problems if files, databases, email accounts, domain settings, or security certificates are handled out of order. A safe migration depends less on rushing and more on following a clear sequence.
The goal is to move a complete working copy of the site, test it privately, and change public traffic only after the new server is ready. This approach reduces downtime and gives you a fallback if an unexpected issue appears.
A hosting migration may be simple for a small static site, but WordPress installations, online stores, membership websites, and custom applications require additional care. Before touching the current server, document what exists and identify the parts that need to be transferred.
Audit the current website first
Start by creating an inventory of your website. Record the domain name, hosting account, content management system, database type, PHP or server version, SSL setup, email accounts, scheduled tasks, subdomains, redirects, and third-party services. This information helps you compare the old environment with the new one before the transfer begins.
Look through the hosting control panel for files that may not be obvious from the public website. Backup folders, staging installations, cron jobs, log files, and custom configuration files can all affect how the site operates. Check whether forms send messages through the server, whether payment services use API credentials, and whether analytics or marketing tools depend on a particular domain configuration.
Crawl the existing website and save a list of important URLs, including pages, posts, product listings, downloads, and image files. A simple site structure makes this process easier, and a clear sitemap can help you verify that key content is still present after the move. Take screenshots of important pages and note current loading times so you have a practical comparison after migration.
Create reliable backups before moving anything
Make at least one complete backup before beginning the transfer. For a typical content-managed website, this means downloading all site files and exporting the entire database. Store the backup in more than one location, such as a local computer and a separate cloud drive. Do not rely solely on a backup stored inside the hosting account you are about to leave.
Test the backup rather than assuming it works. Open the archive, confirm that the expected directories are included, and inspect the database export for readable SQL content. If possible, restore the backup to a temporary environment. A backup that cannot be opened or restored does not provide meaningful protection.
Save copies of configuration details separately. These may include environment variables, database credentials, SMTP settings, API keys, DNS records, robots.txt rules, and custom rewrite directives. Protect sensitive information carefully, and rotate credentials later if they were shared during the migration process.
Before making changes, lower the DNS time-to-live value if your provider allows it. Reducing the TTL a day or two ahead of the move can help DNS updates reach visitors faster, though it cannot guarantee that every network will refresh immediately.
Prepare the new hosting environment
Purchase or activate the new hosting account before canceling the old one. Select a plan that meets the website’s storage, memory, database, traffic, and technical requirements. Confirm that the server supports the software your site uses, including the required PHP version, database engine, extensions, SSL certificates, and server rules.
Create the destination database and user, then record the database name, username, password, hostname, and port. Upload the website files to the correct document root, which is often named public_html, www, httpdocs, or something similar. If the site uses WordPress or another CMS, preserve the original directory structure unless the new host requires a documented adjustment.
Import the database and update the configuration file with the new connection details. Some websites store absolute paths or old domain references in the database, so search carefully before replacing values. A broad search-and-replace can damage serialized data or structured content; use a migration tool designed for the specific CMS when appropriate.
Install an SSL certificate on the new server before public traffic is redirected. Verify that the certificate covers the main domain and relevant subdomains. Configure redirects, caching, compression, backups, file permissions, and firewall rules while the old website is still online.
| Migration area | What to verify on the new host | Common risk |
|---|---|---|
| Website files | All directories, media, themes, plugins, and downloads are present | Missing images or broken features |
| Database | Import completes and the site connects successfully | Error pages or missing content |
| Domain settings | DNS records, subdomains, and redirects are documented | Visitors reach the wrong server |
| Mailboxes, forwarding, MX records, and SMTP settings are recreated | Lost or delayed messages | |
| Security | SSL, permissions, malware scanning, and administrator access work | Warnings or unauthorized access |
| Performance | Caching, server resources, and image delivery are configured | Slower loading after launch |
| Scheduled tasks | Cron jobs and automated processes run correctly | Forms, backups, or updates fail |
Test the transferred site privately
Do not change the domain’s DNS records immediately after uploading the site. First, test the new installation through a temporary URL, preview address, hosts-file entry, or staging domain. This allows you to inspect the destination server without sending regular visitors there.
Check the homepage and several internal pages, then test contact forms, searches, login areas, shopping carts, checkout steps, downloads, videos, and interactive features. Confirm that images load, navigation works, and links do not point back to an outdated temporary address. Review browser developer tools for mixed-content warnings, JavaScript errors, and failed network requests.
Test the administrative side as well. Log in to the CMS, publish a draft, upload an image, update a menu, and confirm that user permissions remain correct. If the site uses scheduled publishing, automated backups, newsletters, or external integrations, verify each process individually.
Use a redirect checker and compare the new site with the old URL inventory. Look for missing pages, incorrect canonical tags, unexpected noindex directives, and altered metadata. Run a performance test from more than one location, but treat the results as guidance rather than an absolute measurement.
Plan the DNS switch carefully
Choose a low-traffic period for the final cutover. Tell staff when editing must stop on the old site, especially if the website receives orders, registrations, bookings, comments, or form submissions. For an active website, put it into maintenance mode briefly or create a final content freeze so changes are not lost between the last backup and the DNS update.
Take a final database backup immediately before switching hosts. If visitors can submit information during the transfer, consider putting the old site into read-only mode. Online stores and membership systems may need a more specialized migration strategy because transactions or account updates can occur continuously.
Update the necessary DNS records, usually the A record for the root domain and the CNAME or A record for www. Leave email-related records unchanged unless email is moving too. If mailboxes are part of the hosting migration, document the MX, SPF, DKIM, and DMARC records before making adjustments.
DNS propagation is gradual. Some visitors may reach the old host while others reach the new one for several hours. Keep both hosting accounts active during this period, and do not make different content changes on each server. Monitor traffic, error logs, uptime, form delivery, and order activity as the new records spread.
Protect search visibility and customer trust
A host change should not require a change to your public URLs. Preserve page addresses whenever possible, because unnecessary URL changes can create broken links and ranking fluctuations. If URLs must change, create a carefully mapped set of permanent 301 redirects from every old address to its corresponding new destination.
Review the robots.txt file, XML sitemap, canonical URLs, metadata, structured data, and analytics tracking code. Submit the sitemap again through the relevant search engine tools if the site’s structure or domain configuration has changed. Watch for accidental staging settings, especially noindex tags that may have been used while testing.
Email deserves separate attention because it is frequently overlooked during a website move. Confirm that contact forms deliver to the intended inbox, outgoing messages use the correct sender address, and authentication records are valid. Send test messages to several providers and check both delivery and reply behavior.
Your About page, team information, service descriptions, and contact details also deserve a visual and factual review after migration. An authentic About page can reinforce trust, but only if its images, links, staff details, and calls to action still display correctly on the new server.
Complete post-migration checks
Monitor the website closely for at least several days after DNS changes. Review server error logs, uptime alerts, analytics, search console reports, and customer messages. Pay special attention to 404 errors, 500 errors, failed form submissions, slow database queries, and unusual login attempts.
Check that automated backups are now running on the new host and that you know where those backups are stored. Confirm that renewal dates for the domain, SSL certificate, hosting plan, and premium software are documented. Remove unused temporary accounts, old staging copies, and exposed archive files after the new site is stable.
Use this practical checklist during the final review:
- Confirm that the homepage, key landing pages, media, downloads, and navigation work.
- Test forms, email delivery, user logins, payments, search, and scheduled tasks.
- Verify SSL coverage, HTTPS redirects, security headers, and administrator permissions.
- Compare analytics, search visibility, redirects, sitemap settings, and robots.txt.
- Keep the old hosting account active until traffic and functionality are consistently normal.
Only cancel the old hosting plan after the DNS transition is complete, the final backup is secure, and no important service still depends on the previous server. Retaining the old account for a short buffer period is usually less expensive than rebuilding a site after an overlooked migration problem.
A careful host transfer is a technical project, but it also affects customers, search engines, staff workflows, and future maintenance. If your website has custom code, an online store, a large database, or complex email requirements, professional oversight can reduce risk. 2 Geeks Web Design provides hands-on development and straightforward communication for small businesses that need a reliable, custom-built web presence. Contact the studio to plan a safe migration, test the new environment, and keep your website working while the infrastructure changes.