The Short Answer
Move The Website, Keep The Email Service You Already Use
Yes—your website can normally move to a new host while your Microsoft 365 or Google Workspace email stays where it is. The important step is to separate website hosting, domain registration, DNS management and email before changing anything. Plan which website records will change, preserve the records and services your email uses, and test both the website and mail afterwards.
Ultra IT can help you move an eligible website to Sydney-based hosting, with a local, developer-led Sunshine Coast team to coordinate the technical details. You can keep your existing business email and domain ownership. A website move does not need to become a mailbox migration or an unrequested redesign.
If you are wondering, “Will changing hosts break our email?”, start with the checklist below. You do not need to know every DNS setting to make a useful enquiry: your website address, email provider and current host are a good starting point. Discuss your hosting move with Ultra IT.
What Matters Most
- Identify domain registration, DNS, website hosting and email separately.
- Preserve email records and test website enquiries as well as mailboxes.
- Use the twelve-question brief to agree access, timing and dependencies.
- Cancel the old service only after retained services and checks are accounted for.
Sunshine Coast Web Hosting · Your Next Step
Moving Hosting? Start With What Must Keep Working
Share your website address, current platform and the hosting issue. We can check website, domain and email dependencies and discuss a suitable migration path.
Hosting starts from $32/month. Storage, backups, migration, email and maintenance inclusions are confirmed in the written scope.
Enquire first. Scope and costs are agreed before work begins.
Explore The Service And Inclusions01
1. Separate The Four Services Before Comparing Hosts
Your domain is the name customers recognise. Registration keeps that name assigned to you; website hosting runs the site; email hosting runs mailboxes; DNS directs requests to the right services. One supplier might handle all four, or each might have a different provider.
This distinction helps you ask for the change you actually want. “Move our WordPress site and keep Microsoft 365” is a clearer brief than “move everything”. It also helps uncover an old bundle whose website, DNS and email would all disappear if the account were cancelled.
Use account or billing information to confirm these facts; a familiar logo on an invoice is not enough to establish who controls the active DNS. Record the responsible person, not their password.
| Service | What To Identify | What A Website-Only Move Means |
|---|---|---|
| Domain registration | Registrar, business ownership and renewal contact | Keep registration unless a separate transfer is agreed |
| DNS management | Where the active DNS records are managed | Keep it, or plan a separate controlled DNS move |
| Website hosting | Current host, site platform and required features | Copy and test the website on the new host |
| Business email | Microsoft 365, Google Workspace, cPanel or another service | Retain the chosen mail platform and its required settings |
02
2. Decide Whether DNS Needs To Move At All
Changing the website's destination and changing its nameservers are different jobs. If the current DNS service can remain active, a website-only move may only need the relevant website records updated. The exact records depend on the new host, any CDN and the site's existing setup.
Changing nameservers means changing where the domain's DNS is managed. That broader change needs a complete review of the records the business still uses, not just a new website address. Check the replacement zone before the switch and retain a record of the former configuration and a practical rollback route.
Google explicitly explains that when a website connection changes nameservers, the relevant Workspace records must also exist at the new DNS host to keep services working. This supports a simple planning rule: website and email can stay separate, but their DNS dependencies still need attention. Google Workspace: connecting a website and preserving Workspace records.
Do not replace records with values copied from somebody else's setup. Your administrator should verify the settings required by your actual accounts, including any domain verification, subdomains or third-party services.
03
3. Keep Email Delivery And Website Form Delivery In The Plan
Keeping Microsoft 365 or Google Workspace usually means leaving those mailboxes, accounts and subscriptions in place. Their required DNS settings must remain correct. Microsoft's documentation distinguishes mail routing from moving existing messages: changing an MX record changes the destination for new mail; it does not copy old mailboxes. Microsoft: domain and email DNS records.
An email review should also identify authorised sending services. Your website, invoicing system and newsletter tool may send mail differently. Check the existing authentication configuration and the actual sending arrangement rather than blindly adding a second SPF record or assuming every sender follows the mailbox provider.
Website enquiry notifications deserve their own test. An inbox can send and receive normally while the website's form fails because its sending configuration changed during the move. Agree who will check the visitor's confirmation, delivery to the intended inbox and a reply to the submitted address. A form success message alone is not evidence that the business received an enquiry.
On cPanel hosting, local email routing can matter even when the public email records look correct. cPanel warns that incorrect routing can interrupt mail; its automatic detection uses the local zone configuration, not a live public DNS lookup. Ask the hosting technician to verify the appropriate routing for the chosen mail service. cPanel: Email Routing.
04
4. Use This Website-Only Migration Brief
Copy this worksheet into your planning notes or send the non-sensitive answers with your hosting enquiry. Leave unknowns marked “please check”—you do not need to guess technical settings.
Keep passwords, recovery codes, API keys and payment details out of this worksheet and ordinary enquiry messages. Agree on a secure access-handover method with the team handling the migration. Where the provider supports it, delegated or temporary access can be preferable to sharing the business owner's full account.
| Briefing Question | Your Answer |
|---|---|
| Website address and platform | URL; WordPress, HTML or another system |
| What should move? | Website only, or a separately agreed broader scope |
| What must stay unchanged? | Domain ownership, email platform and important integrations |
| Current hosting and renewal date | Provider; renewal date if known |
| Current email platform | Microsoft 365, Google Workspace, cPanel or unknown |
| Domain registrar and DNS manager | Provider names; say if different or unknown |
| Who can approve access and DNS changes? | Responsible business contact |
| What does the site do? | Enquiries, sales, bookings, member logins or custom functions |
| Where do website notifications go? | Destination inboxes and sending service, if known |
| Are content, orders or bookings changing during the move? | What must be synchronised and an appropriate change window |
| Who will verify the result? | Website reviewer and email reviewer |
| What remains in the old account? | Mailboxes, DNS, files, backups or other dependencies to check |
05
5. Test The New Site Before Changing The Public Destination
A copy that opens is a starting point, not the whole migration check. Review the main customer journey on the new hosting: navigation, images, enquiry forms and any booking, checkout or login features the business uses. Confirm the correct site, database and configuration are being tested.
If the site takes orders or bookings, plan how changes made during migration will be handled. Avoid running an uncoordinated duplicate that accepts real transactions or sends duplicate messages. The move needs a clear approach to current data and a rollback decision, not just a convenient copying time.
After the approved switch, check the public website address, HTTPS, important existing page URLs and the email flows you agreed to preserve. An unchanged URL structure helps avoid unnecessary broken links; any deliberate URL changes need their own redirect plan. Retain the old service for the agreed validation period rather than cancelling as soon as the homepage appears.
06
6. Check The Old Account Before Cancelling It
Ask a specific question: “What would stop working if this account were cancelled today?” The answer might include old cPanel mailboxes, DNS hosting, stored files or services outside the new website scope.
If email lives in Microsoft 365 or Google Workspace, that does not automatically prove the old website account has no remaining role. Verify the DNS dependency, forwarding arrangements and website sender. If email is hosted inside the old cPanel account, retaining it may require keeping that service or planning a separate mailbox move.
Only cancel when the agreed website and email checks pass, the retained services are accounted for, and the business has the access and recovery information it needs. Record the decision and the responsible person. This is a controlled handover, not a promise that every migration can be completed without interruption.
07
How Ultra IT Can Help
Ultra IT combines Sydney-based website hosting with local Sunshine Coast support and development capability. We can review the existing site, identify its dependencies, coordinate an eligible migration and help resolve website issues that need more than a scripted hosting response.
The standard website hosting signup is AU$32 per month including GST, with one eligible website migration included following technical fit review. Domain registration and Microsoft 365 or Google Workspace subscriptions are not included. cPanel email addresses are included, but a separate cloud-email migration or additional development work is a separately agreed scope. Keeping your current cloud email is a valid option.
If the plan fits your needs, begin your hosting signup. Payment starts the plan; website access, migration timing and setup still need to be coordinated. If you want those dependencies checked first, ask about moving your website. Include the website address, current email platform and the functions you need to preserve—not account passwords.
Common Questions
Clear Answers Before You Decide
Can I Keep Microsoft 365 Or Google Workspace With A New Website Host?
Yes, normally. Website hosting and those email platforms can remain separate. Preserve the account's required DNS settings, verify website mail sending and test the agreed mail flows after the move. If you also want to change email platforms, treat that as a separate migration.
Do I Have To Transfer My Domain To Ultra IT?
No. Changing website hosting does not require transferring domain ownership to Ultra IT. Identify the registrar and DNS manager so the authorised person can make the agreed website change. A registrar transfer, if wanted, is a separate decision.
Will A Website Migration Copy My Old Email Messages?
Not automatically. A website-only move is not a mailbox migration. If mailboxes are on the old hosting account and you want to move them, agree the accounts, historical messages and device setup as a separate part of the work before cancelling anything.
Do We Need To Change Nameservers?
Not always. It depends on where DNS is managed and whether that service can remain. Updating the relevant website records may be enough. If nameservers change, review the full DNS setup and preserve the records needed by email and other retained services.
What If I Do Not Know Who Manages Our Domain Or Email?
Start with the website address, provider invoices and the business contact who can approve access. Ultra IT can help identify the services and the next access step. Keep passwords and recovery codes out of the initial enquiry; arrange a secure handover once the scope and authorised people are clear.
Sources And Review Notes
This guide combines Ultra IT's practical service experience with the current primary sources below. Product availability, pricing and platform guidance can change; check the linked source or ask us to review the current environment before acting.
