Yes. You can move your website to a new host while keeping the domain registered with its current registrar and leaving email with Microsoft 365, Google Workspace, or another mail provider. The safe approach is to change only the DNS records that direct web traffic.
Your domain, DNS, website, and email are separate
The registrar records who controls the domain. Authoritative nameservers hold its DNS records. Web hosting serves the website, while a mail provider handles messages. One company may supply all four, but they remain separate functions.
This matters because a website move does not require a domain transfer. It also does not require a nameserver change if you can edit the existing DNS zone.
The lowest-risk migration method
- Record the current nameservers and export or copy every DNS record.
- Identify the MX records and the TXT or CNAME records used for SPF, DKIM, and DMARC.
- Copy the website and database to the new hosting account.
- Test the new copy without changing public DNS.
- Reduce the relevant web-record TTL in advance where possible.
- Change only the root-domain A or ALIAS record and the
wwwrecord required by the new host. - Recheck the website, forms, SSL, and email in both directions.
Why changing nameservers can break email
When you replace nameservers, the new DNS provider becomes responsible for the entire zone. If the new zone contains the website records but not the existing mail records, incoming email may be directed incorrectly and sent messages may lose authentication.
A nameserver move can still be safe, but the complete zone must be recreated first. Do not rely on the website migration plugin to copy DNS; it normally copies files and the database only.
How to test before switching
Use a temporary URL supplied by the host, a local hosts-file entry, or a controlled preview method. Check the home page, important landing pages, WordPress administration, forms, search, login, basket, checkout, images, and downloadable files.
For a database-driven site, decide whether orders, form entries, comments, or account changes can occur during the final copy. A busy site may need a short content freeze and a final database synchronisation.
What should stay unchanged
If email is not moving, leave the MX records and mail authentication records intact. Preserve service records used for Microsoft 365, Google Workspace, verification tools, accounting systems, and other third parties. Keep the domain at the existing registrar unless you separately want to consolidate it.
After the web DNS change
Both old and new web servers may receive visits while cached DNS answers expire. Keep the old hosting active for at least several days and do not cancel it until logs and public checks show the move is complete. Issue SSL on the new account and verify both the bare domain and www version.
Test forms using an address outside your domain as the recipient and reply to the message. That checks more of the mail path than simply loading the contact page.
Moving to TekLan
TekLan offers website migration and can work around an existing registrar or external email provider. Before the move, tell us who controls your DNS and where email is hosted. We can then agree exactly which records will change and what you should test. Send us your current setup for a migration plan.
