You can move WordPress hosting without moving your business email—but only after checking where both services actually live. The website, domain registration, DNS and mailboxes are separate responsibilities, even when one supplier bundles them into a single bill.
Choosing the destination? Compare Krystal’s managed WordPress hosting if you want a WordPress-focused platform. Its Onyx plans list email as an add-on, not an included mailbox service. Decide whether to retain your current email provider or budget for a separate mailbox move before ordering.
Map four services before changing anything
Start with a one-page ownership record. Put the provider, account owner, renewal date and recovery route beside each service below. A domain registered in your name does not mean you already have access to its DNS settings.
| Service | Its job | Question to answer |
|---|---|---|
| Domain registrar | Maintains the registration and renewal | Who controls the account and renewal? |
| DNS provider | Publishes records directing services | Where is the authoritative DNS zone? |
| Website host | Runs WordPress, files and database | What will move, and what stays behind? |
| Email provider | Stores mailboxes and handles email | Is it independent or part of the old hosting? |
A website-only move does not inherently require a registrar transfer or new nameservers. Keeping working services in place can reduce the number of dependencies in the change. However, check whether cancelling the old hosting would also remove its DNS service or mailboxes: services can be technically separate but commercially bundled.
One domain, separate routes
Website DNS records → WordPress host → pages and checkout
MX records → mail server → business mailbox
The DNS trap: unchanged MX does not always mean unchanged email
MX records identify the server for incoming email. That server name must itself resolve to an address. If the MX destination uses the same hostname whose address you change for the website, email can be redirected too—even though nobody edited the MX record.
For example, imagine an MX record pointing to example.com, with that name resolving to the old combined web-and-mail server. Pointing example.com at a new web-only host changes the destination behind that mail route. An apparently small website edit has affected two services.
Ask the person handling migration to record the MX destination and its address dependencies, not simply tick “MX copied”. Also inspect any mail hostname used by staff’s email applications. This is a dependency check, not a universal set of DNS values to copy into every domain.
Incoming mail is only half the picture. Website forms may send through authenticated SMTP, an email API or the old server. Email-related DNS records include SPF, DKIM and DMARC. Preserve the correct provider configuration and review it if the sending service changes; do not add an arbitrary second SPF policy as a quick fix.
Decide whether this is a website move or two migrations
If mail is already with a separate provider: confirm that its subscription and DNS remain active. The website migration can often leave those mailboxes untouched. You still need to prove that forms and order notifications send correctly from the new site.
If mail is bundled with the old hosting: either retain that service deliberately or arrange a mailbox migration. Make a list of real mailboxes, aliases, forwarding rules, shared addresses and storage usage. An alias that forwards to a person is not the same thing as a mailbox requiring its own login and storage.
Krystal’s KARMA email-migration guidance says destination mailboxes must already exist. Moving a DNS record does not create accounts or copy historic messages. Check separately what happens to contacts, calendars, signatures and mail saved only on an individual computer; an IMAP message transfer should not be assumed to cover those items.
Consider a hypothetical Formby consultancy whose WordPress site is on shared hosting but whose staff use Microsoft 365. A sensible scope could be “move WordPress, retain Microsoft 365 and the current DNS provider, verify form sending”. If its email instead lives inside the old hosting account, that same scope is incomplete. The difference is the dependency map, not the size of the business.
Choose a hosting plan against the migration scope
Before comparing headline prices, read our shared versus managed WordPress hosting guide. For this decision, the important additional question is who owns each migration step.
Review the current Krystal Onyx plans alongside your mailbox requirements. Keep an existing email service if it meets your needs; buying new website hosting is not, by itself, a reason to replace it. If you need new mailboxes, include their cost in the comparison.
Krystal’s migration service scope differs by hosting platform and source setup. Do not read “free migration” as an unlimited promise to transfer every mailbox, repair old faults and reconfigure every outside service. Send the provider a list and obtain a clear included/excluded answer.
- Website: files, database, media, redirects, scheduled tasks and any staging site.
- Email: mailbox creation, message transfer, aliases, device setup and final synchronisation.
- Connections: payment callbacks, booking tools, SMTP/API credentials and third-party DNS verification.
- Commercial terms: renewal cost, VAT treatment, mailbox charges, migration extras and an overlap period with the old provider.
- Ownership: who changes DNS, checks the results and makes the rollback decision?
Prepare a cutover that protects new enquiries and orders
Make a recoverable copy of the site and database before the move. Our WordPress backup restore checklist explains why the existence of a backup file is not enough.
Agree how changes made after the first copy will reach the new site. For a brochure site, that might mean a short content-edit freeze. For an online shop, orders, stock and customer changes need a deliberate final synchronisation or controlled maintenance window. Otherwise two valid-looking copies can contain different trading records.
Test the new installation before directing ordinary visitors to it. Use the host’s supported preview or staging method; check certificates, links, login and integrations. Keep test orders and notifications controlled so you do not charge customers or send unintended messages.
Krystal’s pre-migration guidance highlights DNS caching and keeping the old service available during transition. Lowering a record’s TTL ahead of a planned change may help, but does not remove copies already cached under the previous TTL. If nameservers must change, account for every required record and any DNSSEC transition with the providers.
Use an acceptance record, not “the homepage loads”
| Check | Evidence to keep |
|---|---|
| Website routes | Main domain and www behave as intended; HTTPS and representative old URLs work |
| Incoming and outgoing mail | Messages sent and received with an external account; replies reach the intended mailbox |
| Website enquiries | A real form submission reaches its destination, with a usable reply address |
| Shop or bookings | Controlled transaction, confirmation, stock/calendar update and relevant callback complete |
| Historic and recent data | Required mailbox folders and the final website changes are present |
| Recovery | Named decision-maker, retained old service and a plan to reconcile new data if reverting |
For enquiry testing, follow the full route in our contact-form delivery guide. A success message in the browser does not prove inbox delivery. Keep checks free of unnecessary customer data.
Do not cancel the old package simply because the new homepage is visible. Confirm the agreed checks, final data transfer, retention needs and which services would disappear with cancellation. A rollback is also more than pointing DNS back: new orders or messages may need reconciliation.
The buying decision in one sentence
Choose the host that fits your WordPress requirements, then buy only the email and migration work your dependency map shows you need. Check Krystal’s managed WordPress options with that scope beside you, rather than treating a hosting checkout as a complete migration plan.
Planning a new site or a move for a Formby or Freshfield business? Tell Formby Web Design where your website and email currently live. That gives us a useful starting point for discussing your website project without assuming everything needs replacing.
