WordPress Host Migration Checklist for Business Websites

WordPress Hosting Migration Checklist for Business Websites

A WordPress hosting migration checklist helps you move a business website to a new server without losing content, email, SEO settings or customer enquiries. The safest process is to audit the current website, create tested backups, prepare the new hosting environment, migrate privately, test everything, and change DNS only after the site is ready.

Host migration is not simply copying WordPress files from one cPanel account to another. A business website usually includes a database, uploaded media, plugins, themes, contact forms, email accounts, SSL certificates, DNS records, analytics scripts, payment integrations and search-engine settings. Missing any one of these can cause downtime or lost leads.

This checklist is written for Indian small businesses, D2C brands, NGOs, schools, clinics and agencies moving a WordPress website between hosting providers or servers.

1. Decide Whether Migration Is Necessary

Before starting, identify the reason for the move. The reason affects the type of hosting you need and the risks you should plan for.

Common reasons include:

• Frequent downtime or slow page loading
• Limited storage or bandwidth
• Poor support from the current host
• A website outgrowing shared hosting
• Need for a staging environment
• Difficulty managing backups
• Rising renewal costs
• Security concerns
• Moving from an overseas provider to an Indian data centre, or the reverse
• Separating website hosting from domain and email services

A new host will not automatically solve every performance problem. Slow WordPress websites can also be caused by oversized images, poor plugin choices, unoptimised themes, third-party scripts, weak database structure or an unsuitable website design.

Before purchasing a plan, record what the present website requires:

• WordPress and PHP versions
• Database type and size
• Total website file size
• Monthly visitors and traffic patterns
• Number of domains and subdomains
• Number of email mailboxes
• Existing cron jobs
• WooCommerce or other transactional functions
• Required PHP extensions
• Current backup method
• CDN, firewall or caching services
• Whether the website uses a dedicated IP or special server settings

For a brochure website with a few pages, ordinary managed WordPress or quality shared hosting may be sufficient. A busy WooCommerce store, membership website, learning platform or appointment website may require stronger CPU, memory, database performance and support.

Check the contract before cancelling

Do not cancel the old hosting account immediately after buying the new one. Keep it active until:

1. The website is working on the new server.
2. DNS has updated across important networks.
3. Email delivery has been checked.
4. Forms, payments and administrative functions have been tested.
5. You have retained the final backup.

Also review the old provider’s billing cycle, refund policy and backup retention period. Some hosts delete files soon after cancellation. Download your own backups instead of relying on the provider to retain them.

2. Audit the Existing Website

A proper audit is the first practical part of a website migration. It creates a record of what must be moved and gives you a reference for testing the new version.

Record the website structure

Prepare a list of:

• Main domain
• www and non-www version
• Subdomains such as shop.example.in or members.example.in
• Important landing pages
• Blog categories and tags
• Product, service or course pages
• Downloadable files
• Media library
• Forms and form recipients
• Login and registration pages
• Search functionality
• Any private or password-protected areas
• Staging or development websites

If you use WordPress multisite, note every mapped domain and subsite. Multisite migration requires additional database and configuration checks.

Record integrations

Make a list of all external services connected to the website. These may include:

• Google Analytics or Google Tag Manager
• Google Search Console
• Meta Pixel
• WhatsApp chat tools
• Razorpay, Cashfree, PayU or other payment gateways
• Shipping platforms
• CRM systems
• Email marketing services
• SMTP providers
• Appointment or booking software
• CAPTCHA services
• Cloudflare
• CDN services
• Accounting or invoicing tools
• School management or clinic systems

Some integrations depend on the server IP address, domain verification, API keys or allowed callback URLs. A migration can leave the website looking normal while payment confirmation, enquiry delivery or analytics tracking silently fails.

Take baseline measurements

Before moving the site, note the current condition:

• Homepage loading behaviour
• Key page loading behaviour
• Contact form submission
• Checkout or booking flow
• Login and password reset
• Search results
• Mobile layout
• Current redirects
• Indexability settings
• Sitemap URL
• Robots.txt contents
• Broken links or known errors

You do not need to chase a particular score in a speed-testing tool. The purpose is comparison. If the new website is slower or behaves differently, your baseline helps identify the change.

3. Complete the Backup Checklist

A backup is useful only if it can be restored. Downloading a single WordPress export file is not a complete backup because it may not include plugins, themes, configurations or uploaded files.

Your WordPress backup checklist should include the following.

Website files

Create a complete copy of the WordPress files, including:

• wp-content/uploads
• Active and inactive themes
• Installed plugins
• Custom code
• Child themes
• Must-use plugins
• Configuration files
• Verification files
• .htaccess, where applicable
• Any files stored outside the normal WordPress directory

The wp-content/uploads folder is particularly important because it contains images, PDFs and other media uploaded through WordPress. Large media libraries may take time to download and upload.

Database

Export the complete WordPress database. It contains:

• Pages and posts
• Product information
• User accounts
• WordPress settings
• Plugin settings
• Theme customisation
• Orders and customer records
• Form entries, if stored in WordPress
• Menus and widgets
• SEO metadata

For a small website, a database export through a hosting panel or migration plugin may be adequate. For a large WooCommerce site or a database with active orders, the migration should be planned carefully so new orders and customer records are not lost during the final move.

Configuration and access details

Record:

• WordPress administrator usernames, without sharing passwords in a document unnecessarily
• Database name and user
• FTP or SFTP details
• Hosting control panel access
• DNS provider access
• Domain registrar access
• SSL provider details
• SMTP credentials
• CDN and firewall access
• Payment gateway dashboard access
• Scheduled task or cron configuration

Do not store sensitive credentials in a public spreadsheet or send them through an unsecured group chat. Use a password manager or another controlled sharing method.

Test the backup

At least one backup should be tested before migration. The most reliable test is restoring it to a temporary location, staging server or local development environment.

Check whether:

• The homepage opens
• Admin login works
• Images display
• Plugins load
• Forms work
• The database is complete
• Custom functionality is present
• The site can be updated or configured

Keep the old host active until the new site has been checked. Ideally, retain more than one copy of the backup in separate locations.

4. Prepare the New WordPress Hosting

Purchase or configure the new hosting before making changes to the live website. The new environment should match the technical requirements of the WordPress installation and its plugins.

Confirm technical compatibility

Check:

• Supported PHP version
• MySQL or MariaDB version
• Available memory
• Maximum upload size
• Maximum post size
• Execution time
• Number of PHP workers, where relevant
• Required PHP extensions
• SSL availability
• SFTP or SSH access
• Automatic backup options
• Staging support
• Server-level caching
• Malware scanning
• Support availability in Indian business hours, if that matters to your team

Do not upgrade PHP or WordPress casually during the same migration unless there is a clear reason and a tested compatibility plan. Keeping the first move technically similar makes troubleshooting easier. Upgrades can be planned after the website is stable.

Prepare the domain privately

You should be able to view the migrated website before changing the public DNS. Hosts commonly provide one of these options:

• Temporary hosting URL
• Temporary domain
• Staging subdomain
• Hosts-file preview
• Password-protected development URL
• Direct server IP with a configured host header

A temporary URL can create problems if WordPress saves that address throughout the database. Confirm how the host handles URLs before using it. Some migration tools allow a search-and-replace operation after the final domain is connected.

Do not make a staging website publicly indexable. Use a password, noindex setting and access restrictions. Remove those restrictions carefully after the final site is live.

Lower DNS TTL in advance

DNS records have a time-to-live, or TTL, which tells networks how long to cache an address. Before migration, reduce the TTL for the website’s A record or relevant CNAME record if your DNS provider permits it.

This does not guarantee instant DNS changes. Internet service providers, browsers, operating systems and resolver services can cache records differently. It simply reduces the planned waiting period in many cases.

Do not change mail-related records without understanding them. An incorrect MX, SPF, DKIM or DMARC record can affect business email even when the website is working.

5. Migrate the Website

There are three common ways to move WordPress.

Migration plugin

A migration plugin can package and transfer many ordinary WordPress websites. It is convenient for smaller websites and teams that do not want to work directly with databases.

Check the plugin’s limits before using it. Large media libraries, hosting upload limits, timeouts and database size can interrupt the process. Confirm whether the migration includes the entire database, uploads, themes, plugins and configuration.

Manual file and database transfer

A manual migration generally involves:

1. Put the website into maintenance mode only if necessary.
2. Copy the WordPress files from the old server.
3. Export the database.
4. Create a database and database user on the new host.
5. Upload the files.
6. Import the database.
7. Update wp-config.php with the new database details.
8. Correct file permissions.
9. Check the site using a private preview method.
10. Replace old URLs only when appropriate.
11. Re-save permalinks after the site loads.

A manual method offers more control, but errors in database credentials, file permissions, URL replacement or server configuration can produce errors. It is better suited to someone comfortable with WordPress hosting and database administration.

Host-assisted migration

Some managed WordPress providers offer migration assistance. Ask what is included before assuming that the service covers email, DNS, third-party services or custom applications.

Clarify:

• Whether they will move files and database
• Whether they will test forms and checkout
• Whether they will configure SSL
• Whether they will handle DNS
• Whether they will migrate email
• Whether there is any limit on site size
• What happens if the migration fails
• Whether the old site remains available during testing

A host-assisted move can reduce technical work, but the website owner still needs to verify business functions.

Handle live data carefully

A simple company website may receive only occasional form submissions. A WooCommerce store, clinic booking site or membership portal may receive new records continuously.

For websites with live transactions:

• Plan a low-activity migration window
• Put the site into maintenance mode briefly if required
• Take a final database backup
• Record new orders or enquiries before the switch
• Consider temporarily disabling new transactions
• Confirm payment gateway callbacks after the move
• Import or reconcile any records created during the transition

Never assume that copying the database early and changing DNS later will include activity that occurred in between.

6. Test the New Website Before DNS Changes

Testing should cover the public website, the WordPress dashboard and business operations. A homepage check is not enough.

Use the following pre-launch checklist.

Check URLs and redirects

Migration sometimes changes the domain format, directory structure or permalink behaviour. Compare important old URLs with the new URLs.

Test:

• HTTP to HTTPS redirect
• www to non-www, or the reverse
• Old page URLs
• Changed service or product URLs
• Blog category links
• Image URLs
• Attachment links
• XML sitemap
• Canonical tags
• Pagination
• 404 page

If URLs have changed, prepare permanent redirects from old URLs to the most relevant new pages. Do not redirect every old URL to the homepage. That creates a poor user experience and may weaken the relationship between old and new content.

Check email separately

Website hosting and email hosting can be with the same provider or different providers. A website migration does not necessarily move mailboxes, and changing name servers can unintentionally remove existing email records.

Confirm whether email uses:

• Google Workspace
• Microsoft 365
• Zoho Mail
• A hosting-provider mailbox
• Another business email service

Before changing DNS, copy the existing DNS records, including MX, SPF, DKIM and DMARC. After the move, send and receive test messages from personal and business accounts. Check whether website forms reach the intended inbox and whether replies go out correctly.

7. Change DNS and Complete the Cutover

Once the new site has passed testing, schedule the DNS change. Choose a time when the business can respond if a problem appears. Avoid making the switch immediately before a major campaign, sale, admissions deadline or public event.

Confirm the correct DNS record

Depending on the setup, you may change:

• An A record to the new server IP
• A CNAME for a subdomain
• Nameservers at the domain registrar
• A record behind Cloudflare or another DNS service

Changing nameservers is broader than changing a single website record. It can affect email, verification records, subdomains and other services. If possible, update only the required website record rather than moving all DNS management without a reason.

Take a screenshot or export of the current DNS zone before making changes.

Do not forget SSL

After DNS begins pointing to the new server:

1. Install or activate the SSL certificate.
2. Confirm the certificate covers the correct domain variants.
3. Force HTTPS only after the certificate is valid.
4. Check for mixed-content warnings.
5. Test forms and payment pages over HTTPS.
6. Confirm that HTTP redirects to HTTPS.

Many hosts provide free automated certificates, but renewal still depends on correct DNS and server configuration. Note who is responsible for certificate renewal.

Monitor propagation

DNS updates do not reach every user simultaneously. During propagation, some visitors may see the old server while others see the new one.

Monitor:

• Website access from different networks
• Mobile data and office broadband
• Main Indian cities relevant to your customers
• DNS resolution
• SSL status
• Server logs
• Form delivery
• Orders or bookings
• Email flow

Do not delete the old site as soon as your own laptop shows the new server. Keep it available until the transition is stable and the agreed retention period has passed.

8. Post-Migration SEO, Security and Operations

A host migration can be technically successful while creating SEO or operational problems. Complete these checks after the domain is live.

SEO checks

Open Google Search Console and confirm:

• The correct property is verified
• The preferred domain setup is consistent
• The XML sitemap is accessible
• Important pages are not blocked
• No temporary staging noindex setting remains
• Canonical URLs use the correct domain
• Redirects work
• Search Console does not show a sudden pattern of server errors

If the domain and URLs remain unchanged, a hosting move alone should not require a new website redesign or mass URL change. Still, monitor indexing and crawl errors after launch.

Keep analytics and conversion tracking active. Check actual enquiry forms, calls, WhatsApp clicks, purchases or bookings rather than only checking that a tracking script appears in the page source.

Security checks

Change or review credentials if they were shared during the migration. Remove:

• Temporary administrator accounts
• Old SFTP users
• Test databases
• Temporary preview domains
• Migration archives left in public folders
• Unused plugins and themes
• Debug settings enabled for troubleshooting
• Public backup files

Configure automatic updates according to your risk tolerance and testing process. Enable regular off-site backups. A backup kept only on the same server is not adequate protection against a server failure or account compromise.

Review file permissions, login protection, two-factor authentication and hosting firewall settings. For a school, clinic or NGO handling personal information, access to user records and form entries should be limited to people who need it.

Confirm business continuity

The website is part of a larger operating process. Confirm that:

• Enquiries reach the right staff
• WhatsApp links open the correct number
• Phone numbers are clickable on mobile
• Booking notifications reach the relevant team
• Payment settlements continue normally
• Customer receipts are sent
• Product inventory is accurate
• Staff can log in
• The agency or developer has the right access
• Renewal and backup responsibilities are documented

For Indian businesses, also verify payment gateway settings, GST-related invoice fields, COD options, shipping zones and delivery charges if the website sells products. A migration should not change tax or payment behaviour without the owner knowing.

Keep a migration record

Document:

• Old host and new host
• Migration date
• DNS changes
• Nameserver or record details
• SSL setup
• Backup location
• WordPress and PHP versions
• Plugin changes
• Redirect changes
• New administrator accounts
• Support contacts
• Renewal dates
• Recovery steps

This record is useful when the next developer or agency needs to troubleshoot the website. It also prevents dependency on one person’s memory.

Common Host Migration Mistakes

The same errors appear repeatedly in WordPress website migration projects.

Cancelling the old host too early

This removes your easiest rollback option. Retain the old hosting until DNS, email, forms and business workflows have been tested.

Moving files but not the database

The site may show an old page, missing products or a fresh WordPress installation. Both files and database are required.

Forgetting the uploads folder

The website loads, but images and downloadable files return errors. Check the complete wp-content directory.

Testing only the homepage

A homepage can work while the contact form, checkout, login, redirects or mobile menu is broken. Test critical user journeys.

Changing nameservers without copying DNS records

This can interrupt email and subdomains. Export or record the full DNS zone first.

Leaving staging restrictions active

A noindex tag, password protection or maintenance mode can prevent customers and search engines from accessing the live website.

Updating everything during the move

Changing the host, PHP version, WordPress core, theme and multiple plugins at once makes fault-finding difficult. Migrate first, stabilise the website, then schedule upgrades.

Ignoring email delivery

The website can appear fine while enquiry notifications go to spam or stop altogether. Test both website-generated mail and normal mailbox communication.

Frequently Asked Questions

How long does a WordPress hosting migration take?

The time depends on website size, database complexity, email setup, DNS access, traffic and the chosen migration method. A small informational website is generally simpler than a WooCommerce store, school portal or booking system. Plan a testing window rather than relying on a fixed promise.

Will my website go offline during migration?

A carefully planned move can keep visible downtime low, but temporary issues are possible during DNS changes or final database synchronisation. Keeping the old host active, testing through a private preview and scheduling the cutover during a quieter period reduces risk.

Do I need to migrate my business email with the website?

Not necessarily. Website hosting and email hosting can remain with different providers. You must preserve the correct MX, SPF, DKIM and DMARC records, and you should test email before and after changing DNS.

Will a hosting migration affect Google rankings?

A host-only move with the same domain and URL structure does not inherently require a ranking change. Problems can occur if the new site is blocked, slow, inaccessible, missing metadata or using incorrect redirects. Check robots.txt, canonical URLs, sitemap access and server errors after launch.

Should I change the WordPress version during migration?

Usually, it is easier to migrate using a compatible environment first and upgrade after the site is stable. If a security or hosting requirement makes an upgrade necessary, test the theme and plugins on staging before the final switch.

What should I do with the old hosting account?

Keep it active until the new website, email, forms, payments and DNS are confirmed. Download final backups and document the new setup before cancelling the old account. Check whether the domain, SSL, DNS and email services are billed separately.

Where to Start

Begin by listing the domain, hosting account, email provider, DNS provider, WordPress administrator, important integrations and business-critical website functions. Take a complete files-and-database backup, test that backup, and purchase the new hosting only after confirming its technical compatibility.

Then create a private copy on the new server, test pages, forms, email, payments, redirects, analytics and mobile behaviour, and only then change DNS. Keep the old host available during propagation and complete the post-migration security and SEO checks before closing the project.

For help reviewing your WordPress hosting migration checklist or planning the move, talk to the Govindani Infotech team on WhatsApp; project requirements and pricing are confirmed there.