Buying a website
Can I Change Website Providers and Keep My Domain and Email?
Planning an Orlando business website redesign? Separate domain, hosting, DNS and email decisions, then agree on the checks before ending old services.
Orlando Advertising · Published October 24, 2026 · Sources checked October 24, 2026
Separate four jobs that may share one bill
Domain registration keeps your website name registered. Website hosting runs the site. Email hosting provides the mailboxes. DNS holds the records that direct website visits and mail to the right services. One company may supply several of these, but they are different responsibilities.
Ask the current provider to identify each service and its account holder. Record the renewal contact and who is authorized to make changes. An invoice saying “website package” does not tell you whether canceling it also ends email or DNS.
Ask what the redesign actually needs to change
A new design on the existing platform, a move to a new website host and a transfer of domain registration are different changes. Ask the incoming provider to mark each service as staying, changing or not yet confirmed. AI-assisted design does not remove this planning step.
Changing where the website points can be a narrower task than changing nameservers, which changes the authoritative DNS service. If DNS is moving, ask for a review of all required records. Cloudflare warns that an automatic scan may not find every record. Preserving only the email’s MX records is not a complete continuity plan; authentication and other service records also matter.
Keeping an email address is not the same as moving a mailbox
If the existing email service can remain active, the website may be able to move independently. Confirm that arrangement with the providers rather than assuming an old package can be canceled.
If email hosting must change, agree separately on existing messages, folders, aliases and any calendars or contacts that need attention. Microsoft explains that changing MX records directs new incoming mail but does not move messages already stored. A familiar address can therefore hide an incomplete migration.
Do not retire the old service just because the new homepage is visible. Confirm what the cancellation ends, what data must be retained and any remaining commitment. Google’s Workspace cancellation guidance illustrates why this matters: ending the subscription removes access to core services and can lead to irreversible data deletion. Other providers have their own terms.
Check three routes before closing the handover
Ask for separate evidence that the agreed business addresses can receive mail, send mail and receive website inquiries. Use authorized test messages without real customer details, and record who checked each result.
A working staff mailbox does not establish that the new form’s notifications will arrive. Google’s SPF guidance includes web servers and contact forms among possible senders to account for. The website may use a different sending service from your staff email.
Illustrative example: an Orlando contractor keeps its existing email provider while replacing its estimate-request website. The acceptance check follows one dummy request from the new page to the actual receiving system, rather than stopping at a thank-you screen. It also checks the business mailbox separately.
Copy this handover request into your brief
“Please identify our domain registrar, DNS provider, website host and email provider. For each, state what stays, what changes, who approves it and any ongoing charge.”
“Please separate a website move from any email migration. List the mailboxes, existing data, aliases and connected services included, plus anything excluded or still unknown.”
“Please define the test results, unresolved issues, recovery plan and person responsible for confirming when old services can be retired. Do not cancel a bundled service until its dependencies are understood.”
Keep this plan alongside the website proposal. It is a scope and responsibility checklist, not a promise of uninterrupted service or instructions to change live account settings yourself.
A practical starting checklist
- Identify the domain, DNS, website and email providers.
- Mark each service as staying, changing or unconfirmed.
- Separate new-mail routing from existing-mail migration.
- Test incoming mail, outgoing mail and website inquiries separately.
- Confirm dependencies and retention before ending old services.
Sources and context
- Microsoft 365: Connect a domain with DNS records
- Cloudflare: Primary DNS setup and existing-record checks
- Google Workspace: Set up SPF
- Google Workspace: Cancellation and data-retention warnings
This guide is a planning checklist, not instructions to change live account settings or a promise of uninterrupted service. Confirm the scope, dependencies and current provider terms before making changes.