Steps to Migrate a Website from One Hosting to Another – Complete Guide

Moving a website from one hosting provider to another can improve performance, reliability, security, and scalability. However, a hosting migration involves more than copying website files. You may also need to transfer databases, email accounts, DNS records, SSL certificates, scheduled tasks, and server configurations.

This guide explains how to migrate a website safely while minimizing downtime, data loss, broken functionality, and SEO disruption. The general process applies to WordPress, PHP websites, content-management systems, e-commerce stores, forums, and many other web platforms.

What Is Website Hosting Migration?

Website hosting migration is the process of moving a website from one server or hosting provider to another while keeping the same domain name and, in most cases, the same URLs and content.

A complete migration may include:

• Website files
• Databases
• Uploaded images and documents
• Email accounts and messages
• DNS records
• SSL/TLS certificates
• Cron jobs and scheduled tasks
• Server configuration
• Application environment variables
• Backups and security settings

The objective is to reproduce the website correctly on the new server, test it thoroughly, direct the domain to the new environment, and keep the old server available until the migration is confirmed successful.

Why Consider Moving Your Website to a New Host?

Businesses usually change hosting providers when the existing environment no longer meets their technical, financial, or operational requirements.

1. Slow Website Performance

If pages load slowly despite proper website optimization, the hosting environment may lack sufficient processing power, memory, disk performance, or network capacity.

A faster server can improve user experience, but hosting is only one performance factor. Themes, plugins, database queries, images, third-party scripts, caching, and application code should also be reviewed.

2. Insufficient Server Resources

A growing website may need more:

• CPU capacity
• RAM
• Storage
• Bandwidth
• Database connections
• Concurrent processes
• Email storage

Frequent resource-limit errors, slow administration pages, failed backups, or interrupted imports may indicate that the current hosting plan is no longer suitable.

3. Frequent Downtime or Server Errors

Repeated outages and errors can damage user trust, interrupt sales, and prevent search engines from accessing the website.

Common warning signs include:

• Frequent 500, 502, 503, or 504 errors
• Database connection failures
• Unexplained server restarts
• Long periods of unavailability
• Recurring disk-space or resource-limit warnings

4. Poor Technical Support

Reliable support is important when a website experiences security incidents, server errors, email problems, or unexpected downtime.

A hosting provider should offer clear communication, suitable response times, and support appropriate for the platform being used.

5. Security or Backup Concerns

Migration may be necessary when the current provider does not offer suitable:

• Malware protection
• Automatic backups
• Backup retention
• Firewall protection
• Account isolation
• Software updates
• Access controls
• Disaster-recovery options

6. High Costs or Poor Value

A lower price does not always mean better value. Compare the full service, including performance, backups, support, security, email, management tools, renewal pricing, and migration assistance.

7. Need for More Control

A business may move from shared hosting to a VPS, cloud server, dedicated server, or managed platform when it needs custom software, specific PHP versions, advanced caching, increased security controls, or root-level server management.

Before You Start: Create a Migration Plan

A successful migration begins before any files are transferred. Document the current website environment and decide how each component will be reproduced on the new server.

Create a Website Inventory

Record the following information:

• Domain name and registrar
• Current hosting provider
• Website platform and version
• PHP, database, and web-server versions
• Website files and storage size
• Database names and sizes
• Email accounts and storage usage
• DNS records
• SSL certificate configuration
• Cron jobs
• Third-party integrations
• Firewall and security rules
• Backup locations
• Application-specific server requirements

Check the New Server for Compatibility

Confirm that the new hosting environment supports the website’s requirements.

Review:

• PHP or application runtime version
• Required PHP extensions
• Database type and version
• Web server configuration
• File permissions
• Maximum upload size
• Execution and memory limits
• Rewrite rules
• Scheduled tasks
• Email sending requirements
• Server location
• Backup capabilities

Choose a Low-Traffic Migration Window

Schedule the final migration during a period when the website receives fewer visitors, orders, registrations, or content updates.

For a business website, this may be outside normal working hours. For an e-commerce store or international website, traffic data should be reviewed rather than assuming that weekends or late nights are always quiet.

Reduce DNS TTL in Advance

The DNS time to live, or TTL, controls how long DNS resolvers may cache a record.

When possible, reduce the TTL of the website’s main DNS records before migration. This can help new DNS values take effect more quickly after the switch.

Do not wait until the final cutover to reduce TTL, because existing cached records may continue using the previous value until they expire.

Prepare a Rollback Plan

A rollback plan explains how to restore service if the new server fails after the DNS switch.

It should include:

• A verified backup of the original website
• The previous DNS values
• Access to the old hosting account
• A record of configuration changes
• The person responsible for approving rollback
• Steps for handling data created during the migration window

Step-by-Step Guide to Migrating a Website to a New Host

Step 1: Prepare the New Hosting Account

Choose a hosting plan that can support the website’s current requirements and expected growth.

Consider:

• CPU and RAM allocations
• Storage type and capacity
• Bandwidth and traffic limits
• Server location
• Automatic backup frequency and retention
• Control panel availability
• Technical support
• Security features
• Scaling options
• Email hosting
• Staging environments
• Migration assistance

Activate the account, add the domain if required, and prepare the document root before transferring data.

Step 2: Create and Verify a Complete Backup

Do not begin the migration without a recent, restorable backup.

A full backup may include:

• Website files
• Databases
• Email messages and accounts
• DNS records
• SSL certificate files when applicable
• Configuration files
• Cron jobs
• Server rules
• Environment variables

For many PHP websites, files are located inside a directory such as public_html, htdocs, httpdocs, or another document root. Confirm the actual directory instead of assuming every host uses public_html.

How to Back Up Website Files

You can use:

• The hosting control panel’s backup tool
• File Manager
• FTP or SFTP
• SSH and command-line archive tools
• A platform-specific migration plugin

Include hidden files such as .htaccess, because they may contain rewrite rules, redirects, access restrictions, or PHP settings.

How to Back Up the Database

Common database backup methods include:

• phpMyAdmin export
• The hosting panel’s database backup tool
• mysqldump through SSH
• A platform-specific backup plugin

For a MySQL or MariaDB website, export the complete database structure and data. Large databases may be more reliable to export through command-line tools than through a browser-based interface.

Verify the Backup

A backup is useful only if it can be restored.

Check that:

• The archive opens successfully.
• Expected directories and hidden files are present.
• The database export is not empty or incomplete.
• Backup file sizes are reasonable.
• The files are stored outside the server being migrated.

Use clear filenames that include the website and backup date, for example:

example-com-files-2026-07-29.tar.gz
example-com-database-2026-07-29.sql

Step 3: Create the Database and Application Environment

On the new server:

1. Create a new database.
2. Create a database user.
3. Use a strong, unique password.
4. Grant the required privileges to the user.
5. Record the database hostname and port.

Import the database backup using phpMyAdmin, a hosting control panel, or a command-line utility.

For large databases, confirm that the import did not stop because of upload, execution-time, packet-size, or memory limits.

Step 4: Upload and Restore the Website Files

Upload the website files to the correct document root on the new server.

Depending on the environment, you may use:

• SFTP
• FTP
• File Manager
• SSH
• rsync
• A migration or backup tool

After extraction or upload, review file ownership and permissions. Incorrect permissions can produce access errors, failed uploads, broken caches, or security vulnerabilities.

Step 5: Update the Website Configuration

The application must be updated to connect to the new database and server environment.

For WordPress, review the database settings in wp-config.php:

define('DB_NAME', 'new_database_name');
define('DB_USER', 'new_database_user');
define('DB_PASSWORD', 'use_a_strong_unique_password');
define('DB_HOST', 'localhost');

The database hostname is not always localhost. Use the value provided by the new hosting provider.

Other platforms may store configuration in files such as:

• .env
• config.php
• configuration.php
• settings.php
• Application-specific configuration files

Review:

• Database credentials
• Base URLs
• Storage paths
• Cache directories
• SMTP settings
• API credentials
• Environment variables
• Session configuration

Step 6: Recreate Server Settings and Scheduled Tasks

Website files and databases do not always contain the complete server configuration.

Recreate or review:

• Cron jobs
• Queue workers
• Scheduled backups
• Rewrite rules
• PHP settings
• Firewall rules
• Password-protected directories
• Redirects
• Image-processing libraries
• Background services

A missing cron job may cause scheduled emails, recurring payments, inventory synchronization, backups, or automated tasks to stop working without an obvious frontend error.

Step 7: Install or Issue the SSL Certificate

The new server must serve the website correctly over HTTPS before the domain is fully switched.

Depending on the provider, you may:

• Issue a new Let’s Encrypt certificate
• Use an automatically managed certificate
• Install an existing commercial certificate
• Configure SSL through a proxy or content delivery network

Check:

• The main domain
• The www hostname
• Relevant subdomains
• Certificate expiration and renewal
• HTTP-to-HTTPS redirects
• Mixed-content warnings

Step 8: Test the Website Before Changing DNS

Whenever possible, test the website on the new server before directing public traffic to it.

Testing methods may include:

• A temporary URL supplied by the host
• A staging subdomain
• A local hosts-file entry
• A private preview domain

When using a hosts-file entry, your computer can resolve the domain directly to the new server while most visitors continue using the old server.

Website Functionality Checklist

• Homepage and important landing pages
• Navigation menus
• Images and downloadable files
• Internal links
• Login and registration
• Contact and enquiry forms
• Search functionality
• Checkout and payment processing
• Customer accounts
• Admin area
• File uploads
• Email notifications
• API integrations
• Scheduled tasks
• Redirects
• Custom scripts

Technical Checklist

• No unexpected 404 or server errors
• Correct PHP or application version
• Correct database character set and collation
• Correct file ownership and permissions
• Writable cache and upload directories
• Valid SSL certificate
• No mixed-content warnings
• Correct canonical URLs
• No unintended noindex directive
• No staging-domain URLs in page source

Step 9: Migrate Email if It Is Hosted on the Old Server

Changing hosting does not automatically move email accounts or historical messages.

If email is hosted on the old server, you may need to:

• Create the same mailboxes on the new service
• Copy existing messages using IMAP synchronization
• Recreate aliases and forwarding rules
• Recreate autoresponders
• Update email client settings
• Update SMTP settings used by the website

Review the complete email-related DNS configuration, including:

• MX records
• SPF
• DKIM
• DMARC
• Mail-related A or CNAME records

If the website uses a separate email provider such as Google Workspace or Microsoft 365, preserve the existing mail records when changing website DNS.

Step 10: Perform a Final Data Synchronization

Dynamic websites can change while the first backup is being transferred. New orders, accounts, comments, form entries, uploads, or content edits may remain only on the old server.

Before the final switch, choose an appropriate method:

• Temporarily place the website in maintenance mode.
• Pause checkout, account registration, or content editing.
• Export and import only the newly changed data.
• Run a final file and database synchronization.
• Use replication or platform-specific migration features.

This step is particularly important for e-commerce stores, membership websites, forums, booking systems, and frequently updated applications.

Step 11: Update DNS Records

After the new server has been tested and the final data is synchronized, direct the domain to the new environment.

There are two common approaches:

Change the Nameservers

Replacing nameservers transfers DNS management to another provider.

Before doing this, recreate all required records on the new DNS service, not only the website record. Missing mail or verification records can interrupt email and third-party services.

Change Only the Required DNS Records

If you want to keep the current DNS provider, update only the records needed for the website, such as:

• The root-domain A or AAAA record
• The www record
• Relevant application subdomains

Preserve unrelated records for email, verification, APIs, and other services.

DNS changes may be visible to different users at different times because of resolver and local caching. During this transition, some visitors may reach the old server while others reach the new one.

Step 12: Monitor the Website After Cutover

Do not assume the migration is complete immediately after changing DNS.

Monitor:

• Website availability
• Server error logs
• PHP or application logs
• Database errors
• CPU, RAM, and disk usage
• Checkout and payment results
• Form submissions
• Email delivery
• SSL status
• Analytics data
• Search-engine crawling

Step 13: Keep the Old Hosting Active Temporarily

Do not cancel the old hosting account immediately.

Keeping it active temporarily provides:

• A rollback option
• Access to missed files or messages
• A source for final data comparison
• Protection while DNS caches update

The appropriate retention period depends on the website, billing cycle, DNS setup, and migration risk. High-value or complex websites may require a longer observation period.

Step 14: Create a New Backup on the New Server

After the migration is confirmed, create a fresh backup of the working website in its new environment.

Verify that automatic backups, retention periods, remote storage, and restoration procedures are configured correctly.

How to Protect SEO During a Hosting Migration

A hosting-only migration should normally preserve the same domain, URLs, content, and site structure. When these elements remain unchanged and downtime is minimized, the SEO impact is usually limited.

However, technical mistakes can cause visibility problems.

Keep the Same URLs

Do not change page URLs merely because the website is moving to another server.

If URL changes are also required, treat them as a separate site-migration project and create permanent one-to-one redirects from every old URL to its most relevant new destination.

Preserve Content and Metadata

Confirm that the migration retains:

• Page content
• Title tags
• Meta descriptions
• Heading structure
• Canonical tags
• Structured data
• Image ALT attributes
• Internal links
• Robots directives

Check robots.txt and Indexing Directives

A staging environment may block search engines or use noindex. Make sure those restrictions are not unintentionally copied to the live website.

Review:

• robots.txt
• Page-level robots meta tags
• HTTP indexing headers
• CMS search-engine visibility settings

Check Canonical Tags

Canonical tags should point to the correct live URLs, not temporary domains, IP addresses, staging URLs, or the old server.

Preserve the XML Sitemap

Confirm that the sitemap:

• Loads correctly
• Contains canonical, indexable URLs
• Does not reference staging domains
• Remains accessible through the expected URL

Minimize Downtime

Short interruptions do not automatically cause a ranking loss, but extended or repeated unavailability can prevent crawling and affect users.

If maintenance is necessary, use an appropriate temporary status such as 503 Service Unavailable rather than showing a permanent error page with a successful 200 response.

Review Search Console After Migration

After the switch, monitor:

• Indexing status
• Crawl errors
• Canonical selection
• Page experience reports
• Search impressions and clicks
• Server-related errors

A change-of-address submission is generally associated with domain changes, not a normal hosting migration where the domain remains the same.

Common Website Migration Mistakes

• Canceling the old hosting account before verifying the new server
• Backing up files but forgetting the database
• Forgetting hidden files such as .htaccess
• Not verifying whether the backup can be restored
• Using an incompatible PHP or database version
• Forgetting cron jobs and background workers
• Changing nameservers without recreating email DNS records
• Testing only the homepage
• Switching DNS before installing SSL
• Leaving staging noindex settings enabled
• Failing to synchronize new orders or registrations
• Using incorrect file permissions
• Forgetting SMTP and API configurations
• Assuming DNS changes take effect for every visitor simultaneously
• Making hosting, domain, URL, design, and CMS changes at the same time without a detailed plan

Important Tips for a Smooth Hosting Migration

• Create multiple backups: Keep at least one copy outside both the old and new hosting accounts.
• Document the existing setup: Save screenshots or exports of DNS records, cron jobs, PHP settings, and mail configuration.
• Test before switching DNS: Do not use public visitors as the first test of the new server.
• Schedule carefully: Choose a migration window based on actual traffic and transaction data.
• Communicate when necessary: Notify employees or customers if maintenance may affect important services.
• Protect dynamic data: Use maintenance mode or final synchronization for websites that change continuously.
• Monitor after launch: Many migration problems appear only when real users begin using forms, checkout, email, or account features.

Should You Use a Professional Migration Service?

A basic informational website may be migrated by an experienced website owner using control-panel tools or a reliable migration plugin.

Professional assistance is more appropriate when the website includes:

• E-commerce transactions
• Customer accounts
• Large databases
• Custom PHP or application code
• Complex email requirements
• Multiple domains or subdomains
• Scheduled tasks
• Server-level configuration
• High traffic
• Strict uptime requirements
• Security or compliance obligations

Benefits of a Professional Migration Service

• Reduced technical risk: Experienced technicians can identify compatibility, database, DNS, SSL, and server-configuration issues.
• Less disruption: The migration can be planned around traffic and business activity.
• Complete component transfer: Files, databases, email, DNS, cron jobs, redirects, and configurations can be reviewed together.
• Testing and rollback: A professional process should include validation and a recovery plan.
• Post-migration support: Problems that appear after the DNS switch can be investigated quickly.

No responsible provider should guarantee that every migration will have absolutely zero downtime or zero risk. The objective should be to minimize disruption, protect data, test carefully, and provide a clear rollback path.

Some hosting providers include migration assistance with selected plans. Before relying on a free service, confirm exactly what is included. Some providers migrate only website files and databases but do not transfer email, DNS records, custom applications, cron jobs, or third-party integrations.

Website Migration Checklist

Before Migration

• Inventory website files, databases, email, DNS, and scheduled tasks.
• Confirm new-server compatibility.
• Create and verify complete backups.
• Reduce DNS TTL when appropriate.
• Schedule a low-traffic migration window.
• Prepare a rollback plan.
• Record existing DNS values and server settings.

During Migration

• Create the new database and user.
• Restore website files and database.
• Update application configuration.
• Recreate cron jobs and server settings.
• Install or issue SSL.
• Test the website on the new server.
• Migrate email when required.
• Complete a final data synchronization.
• Update DNS records.

After Migration

• Monitor website availability and server logs.
• Test forms, login, search, checkout, and email.
• Confirm HTTPS and certificate renewal.
• Check canonical tags, robots directives, and XML sitemap.
• Review analytics and search performance.
• Keep the old server temporarily.
• Create a new backup on the new host.
• Cancel the old service only after final confirmation.

Frequently Asked Questions About Website Hosting Migration

Will Migrating My Hosting Cause Data Loss?

A properly planned migration should not cause data loss, but the risk cannot be eliminated simply by copying one backup. Dynamic websites may receive new orders, messages, registrations, or uploads during the migration.

Create verified backups and perform a final synchronization or temporary content freeze before switching DNS.

Will Switching Hosts Affect My SEO Rankings?

A hosting change normally has limited SEO impact when the domain, URLs, content, metadata, and internal linking remain the same and the website stays accessible.

SEO problems may occur if the migration causes prolonged downtime, server errors, slower performance, missing pages, incorrect canonical tags, blocked crawling, or accidental noindex directives.

A faster server can improve page performance, but changing hosts does not guarantee higher rankings.

How Long Do DNS Changes Take?

DNS updates do not reach every resolver and user at exactly the same time. The transition depends on previous TTL values, resolver caching, local networks, and the type of record changed.

During this period, some visitors may reach the old server while others reach the new server. Keeping both environments operational helps reduce disruption.

Do I Need a New Domain When Changing Hosts?

No. Domain registration and website hosting are separate services. You can keep the same domain and update its DNS records or nameservers to direct it to the new server.

Can I Migrate a Website Without Downtime?

Many migrations can be completed with little or no noticeable downtime when the new server is prepared and tested before DNS is changed.

However, results depend on the platform, DNS caching, dynamic data, email setup, and technical complexity. It is more accurate to plan for minimal disruption than to assume downtime is impossible.

Should I Change Nameservers or Only the A Record?

Changing only the website’s address record is often simpler when you want to keep the current DNS provider. Changing nameservers moves DNS management and requires all existing records to be recreated correctly.

Choose the method based on who should manage DNS after the migration.

Will My Email Move With My Website?

Not automatically. If email is hosted on the old server, mailboxes, messages, forwarding rules, and DNS records may need to be migrated separately.

If email uses a third-party provider, preserve its MX, SPF, DKIM, DMARC, and verification records.

When Can I Cancel the Old Hosting Account?

Cancel the old service only after the website, email, SSL, integrations, scheduled tasks, analytics, and DNS behavior have been verified on the new environment.

Keep the old server available long enough to support rollback and recover any missed data.

Can a WordPress Migration Plugin Handle Everything?

A migration plugin can simplify the transfer of WordPress files and databases, but it may not migrate email accounts, DNS records, cron jobs outside WordPress, server configuration, firewall rules, or external services.

Review the complete hosting environment even when using an automated plugin.

What Should I Do if the Site Shows a Database Connection Error?

Check the database name, username, password, hostname, port, user privileges, and database-server availability. Also confirm that the imported database is complete and compatible with the new server.

Conclusion

Migrating a website to a new hosting provider is not simply a file-transfer task. A complete migration may involve website files, databases, DNS, SSL, email, scheduled tasks, server configuration, security settings, and dynamic data.

A safe migration process should:

• Document the existing environment
• Confirm compatibility with the new server
• Create and verify complete backups
• Prepare a rollback plan
• Restore and configure the website on the new host
• Test before changing DNS
• Synchronize final data
• Monitor the website after cutover
• Keep the old hosting active temporarily

When these steps are completed carefully, businesses can move to a more suitable hosting environment while minimizing downtime, protecting data, and preserving SEO performance.

Viet SEO supports website owners with hosting migration planning, backup and restoration, database transfer, DNS configuration, SSL installation, email migration, compatibility testing, and post-migration monitoring. Professional assistance is particularly valuable for e-commerce websites, custom applications, large databases, and business-critical systems where errors can interrupt operations or cause data loss.