How to Change Web Hosting Provider Without Losing Data

How to change web hosting provider without losing your website, email or search visibility? Build the new account first, copy every part of your service, test it, and only then change DNS and close the old account. This checklist is for a normal move where your domain name and website address stay the same.

Before you start: renewal date, backups and logins

Why this matters: most migration problems come from cancelling too early, forgetting a mailbox, or copying only the visible website files.

Write down these details before buying the new plan:

• Your domain registrar login and the account email used for renewal.
• The old hosting username, panel login, FTP/SFTP details, database details and current server IP.
• The old hosting renewal date, invoice number and cancellation policy. Set a calendar reminder several days before renewal, but do not cancel yet.
• Every domain, subdomain, addon site, database, cron task, FTP account, mailbox, forwarder, autoresponder and DNS record in use.
• The current DNS zone: A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC and any verification records.
• A recent local backup of website files, the database and important email.

For WordPress, the backup must include wp-content, the WordPress core files, wp-config.php, .htaccess if present, and a database export. WordPress’s migration guidance also separates the files from the database, so do not assume that downloading public_html alone is a complete backup. Read HostKarle’s WordPress migration guide if your site runs on WordPress.

Keep a simple migration sheet:

Item	Old host	New host	Tested
Website files			☐
Database and credentials			☐
Mailboxes and old messages			☐
DNS records			☐
SSL and redirects			☐
Forms, cron jobs and integrations			☐

Step 1: buy the new plan or request free migration

Why this matters: you need a working destination while the old website and mail service are still live.

1. Choose a plan that has enough storage, sites, databases and mailboxes for your current account. For example, HostKarle Professional supports up to 10 websites, 150 GB SSD storage, 20 business email accounts and 20 MySQL databases. It is billed at ₹1,788 yearly or ₹249 monthly; the card displays the yearly option as ₹149/mo.
2. Create the hosting account, but do not point your domain to it yet. Keep the old DNS and old hosting active.
3. If you are moving to HostKarle, request the included free migration and provide the old panel or backup details through the proper account channel. Ask what they need before sharing any password, and change temporary passwords after the move.
4. Add the domain and each required subdomain at the new host. If the panel offers a temporary URL, preview URL or hosts-file test, use it for testing before public DNS changes.

HostKarle plans use DirectAdmin, with Softaculous, PHP version selection, self-service backup and restore tools, free auto-renewing SSL and free migration. See the shared hosting plans for the current plan details before ordering.

Success looks like: the new account exists, the destination domain is ready, and the old website still opens normally for visitors.

Step 2: copy website files and databases

Why this matters: the files contain your themes, plugins, uploads and configuration, while the database contains posts, pages, settings, users and orders.

Use the method that matches your old and new panels:

1. Full account backup: if both providers support DirectAdmin backups, create a complete user backup and ask the new host to restore it. DirectAdmin’s backup documentation says a user backup can contain databases, email accounts, email data, domains, websites and subdomains. This is usually the most complete route.
2. Panel migration: use the new host’s migration form if it supports your old panel. Confirm that it covers databases, mailboxes, DNS records and cron jobs, not only WordPress files.
3. Manual WordPress move: download all site files, export the database, upload the files to the new document root, create a new database and user, then import the SQL file. Update the new wp-config.php with the new database name, username, password and host if those values changed.

For a manual copy, the actions are:

1. Put the site in maintenance mode or choose a quiet period. Note the time so you know which last-minute orders, form entries or comments need checking.
2. Export the database from the old panel’s database tool. Keep the .sql file in two safe places.
3. Download the complete document root, including hidden files. Do not omit .htaccess, uploads, plugin folders or custom configuration files.
4. Create the matching database and database user on the new account, then import the export.
5. Upload the files and set the new database credentials in wp-config.php.
6. Compare the PHP version and required extensions. If the old site uses a particular PHP version, select a compatible version on the new account before testing.

Do not run a broad find-and-replace just because the hosting company changed. If the domain and URLs remain identical, the database URLs normally remain identical too. If you are changing the domain as well, use a migration tool that understands serialised WordPress data and take another backup first.

Success looks like: the new copy loads through its temporary test method, WordPress admin accepts your login, media opens, forms submit, and no recent content is missing.

Step 3: recreate mailboxes and move old mail

Why this matters: website migration tools often do not include email, and DNS can send new messages to either system while records are changing.

Make a list of every address before you create anything: hello@, sales@, personal addresses, aliases, forwarders, catch-all rules and autoresponders.

1. Create the same mailbox addresses on the new host. If the old passwords cannot be exported safely, set new passwords and update each phone, computer and mail app.
2. Recreate forwarders, filters, signatures and autoresponder messages. Check the destination address for every forwarder.
3. Copy old messages over IMAP using a mail client or an approved mailbox-migration tool. Keep the old mailbox available while the copy is running. For a large mailbox, ask both providers about their supported transfer method.
4. Record the new incoming and outgoing mail server names, ports and encryption settings. Do not guess them from another provider’s instructions.
5. Check the DNS records that protect delivery: MX, SPF, DKIM and DMARC. Copy the existing records into the new DNS zone when the new provider supplies replacement values.
6. Send a test from an outside account to the new mailbox and reply from it. Test both a personal Gmail/Outlook address and one address on your own domain if available.

If you use a third-party email service, do not replace its MX records with the web host’s records. Changing the website host does not automatically require changing the email host.

Success looks like: all planned addresses exist, old messages are visible, new mail arrives, replies leave successfully, and SPF/DKIM/DMARC records are present in the DNS zone that will become authoritative.

Step 4: lower TTL and change DNS carefully

Why this matters: DNS resolvers cache answers for the record’s TTL, so a lower TTL makes a planned record change easier to complete. It cannot instantly remove answers that were already cached under a longer TTL.

At least one day before the cutover, if your DNS provider allows it, lower the TTL for the website records to 300 seconds (5 minutes). Cloudflare’s TTL documentation explains that TTL controls how long DNS answers are cached and that longer TTLs make later updates take longer to take effect.

First decide which change you actually need:

• Keep your current nameservers: change only the website A/AAAA record, or the CNAME used by the website. Leave third-party MX, SPF, DKIM, DMARC and verification records alone.
• Move DNS to the new host: copy the complete zone first, including mail and TXT records. Then change the nameservers at your registrar. For HostKarle, the nameservers are ns1.fastnsdns.com and ns2.fastnsdns.com; confirm the current values in your account before submitting the change.

Before saving the change, compare the old and new zones line by line. Do not remove an unfamiliar TXT record until you know which service uses it.

After the change, check the public answers from your computer:

nslookup example.com
nslookup -type=MX example.com
nslookup -type=TXT example.com

Replace example.com with your domain. Run the checks again from a mobile connection or a different network, because your home or office resolver may still have cached the old answer.

For a step-by-step nameserver walkthrough, see how to find and update HostKarle nameservers.

Success looks like: different networks begin resolving the website to the new host, mail records still point to the intended mail service, and the old host remains available for visitors whose DNS is not updated yet.

Step 5: issue SSL and test the live site

Why this matters: a site can appear to have moved while HTTPS, redirects, scheduled tasks or forms still use the old account.

When the new domain resolves to the new host:

1. Run the new host’s Let’s Encrypt or SSL setup for the root domain, www version and every HTTPS subdomain you use. The certificate authority must validate control of each name before issuing a certificate.
2. Open both http://example.com and http://www.example.com. Confirm that each redirects to the intended HTTPS URL.
3. Test the home page, important landing pages, images, CSS, JavaScript, WordPress login, search, contact form, checkout or enquiry flow, downloads and 404 page.
4. Log in to WordPress and check media, plugins, themes, scheduled posts, cron-dependent features and any external API connection.
5. Confirm that the database is receiving new data. Submit a harmless test form and verify it arrives in the expected mailbox or dashboard.
6. Check the source and destination server separately if possible. A hosts-file test can help, but remember to remove the temporary line after testing.

If you see mixed-content warnings, update hard-coded http:// asset URLs only after taking a backup. If WordPress reports a database connection error, recheck the database name, user, password and host in wp-config.php.

Success looks like: HTTPS works without a certificate warning, the complete user journey works, new data is saved, and the new copy matches the old site.

Step 6: keep the old host, then cancel it

Why this matters: DNS changes roll out at different speeds, and the old server may still receive visitors or mail during the overlap.

Keep the old hosting account active until all of these checks pass:

• The longest old DNS TTL has elapsed, or you have allowed the provider’s stated propagation window.
• The website resolves to the new host from more than one network.
• You have tested the website, HTTPS, forms, logins, database writes and important integrations.
• New mail arrives at the new mailboxes and old mail has been copied or archived.
• The registrar, hosting, email and domain renewal dates are recorded in your calendar.
• You have one final backup of the old account and one verified backup of the new account.

During the overlap, avoid making separate content or order changes on both copies. If the old site must receive a last-minute order or form submission, record it and reproduce it on the new copy before cancellation.

When the checks pass, cancel auto-renewal or submit the old provider’s cancellation request. Download final invoices and backups, confirm the cancellation date in writing, and retain the domain registrar account. Changing hosting does not transfer ownership of your domain.

For future moves, track hosting renewal prices and dates separately from domain renewals; they are different services and can renew on different days. HostKarle’s hosting renewal price guide explains why checking the renewal amount before the next billing date matters.

A quick migration checklist

Use this short version on the day of the move:

1. Old plan paid and renewal date recorded.
2. Local backup of files, database and email made.
3. New account created and domain added without changing public DNS.
4. Files, database, mailboxes, old messages and DNS records copied.
5. New copy tested through a temporary URL, hosts file or preview method.
6. TTL lowered where possible and the cutover time recorded.
7. Website records or nameservers changed.
8. SSL issued and website, forms, database and mail tested.
9. Old host kept active during the overlap.
10. Old plan cancelled only after the new copy and mail flow are confirmed.

Troubleshooting after changing hosts

The old website still appears

Your device or DNS resolver may have a cached answer. Check the A/AAAA record with nslookup, try mobile data, and confirm that you changed the correct record or nameservers. Do not delete the old account while some networks still reach it.

The website loads but WordPress shows a database error

Check the database name, database user, password and database host in wp-config.php. Confirm that the database user has access to the imported database, then check the new host’s PHP and database compatibility.

The website works but email stops

Inspect MX first, then SPF, DKIM and DMARC. If you kept an external email provider, restore its MX records; if you moved mailboxes, confirm that the same addresses were created on the new host and that mail apps use the new server settings.

HTTPS shows a warning

Make sure the domain resolves to the new host before issuing SSL. Include both the root and www names if you use both, then test in a private browser window after the certificate is issued.

A form or scheduled task stopped working

Check the form recipient, SMTP settings, cron schedule, PHP version and file permissions. Compare the old and new environment settings instead of reinstalling plugins immediately.

FAQ

Can I change web hosting provider without changing my domain?

Yes. Keep the domain at its current registrar and move only the website hosting. Copy the site first, test the new account, and then update the website record or nameservers so the same domain points to the new provider.

Will changing hosting delete my website?

Changing the host does not delete the original site by itself. The risk comes from an incomplete backup, a failed import or cancelling the old account before the new copy and DNS are verified, so keep independent backups and an overlap period.

Do I need to move email when I move my website?

Not always. Website hosting and email hosting can be separate: preserve the existing MX records if mail stays where it is. If mail is moving too, recreate mailboxes, copy old messages and test delivery before changing DNS.

How long should I keep the old hosting account?

Keep it active until the longest recorded DNS TTL has passed and you have tested the site and mail from multiple networks. If you do not know the old TTL, allow a conservative overlap of at least 48 hours and wait longer when your provider or DNS records indicate a longer cache period.

Is it easier to ask the new host to migrate my website?

Usually, yes, especially when the new provider includes migration. Give the migration team a complete inventory and backup, and still test files, database, mailboxes, DNS, SSL and forms yourself before cancelling the old plan.

DONE how-to-change-web-hosting-provider words=2562

{“@context”: “https://schema.org”, “@type”: “FAQPage”, “mainEntity”: [{“@type”: “Question”, “name”: “Can I change web hosting provider without changing my domain?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Yes. Keep the domain at its current registrar and move only the website hosting. Copy the site first, test the new account, and then update the website record or nameservers so the same domain points to the new provider.”}}, {“@type”: “Question”, “name”: “Will changing hosting delete my website?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Changing the host does not delete the original site by itself. The risk comes from an incomplete backup, a failed import or cancelling the old account before the new copy and DNS are verified, so keep independent backups and an overlap period.”}}, {“@type”: “Question”, “name”: “Do I need to move email when I move my website?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Not always. Website hosting and email hosting can be separate: preserve the existing MX records if mail stays where it is. If mail is moving too, recreate mailboxes, copy old messages and test delivery before changing DNS.”}}, {“@type”: “Question”, “name”: “How long should I keep the old hosting account?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Keep it active until the longest recorded DNS TTL has passed and you have tested the site and mail from multiple networks. If you do not know the old TTL, allow a conservative overlap of at least 48 hours and wait longer when your provider or DNS records indicate a longer cache period.”}}, {“@type”: “Question”, “name”: “Is it easier to ask the new host to migrate my website?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Usually, yes, especially when the new provider includes migration. Give the migration team a complete inventory and backup, and still test files, database, mailboxes, DNS, SSL and forms yourself before cancelling the old plan. DONE how-to-change-web-hosting-provider words=2562”}}]}