MX records tell the world which server receives email for your domain. Change them when you move your email to Microsoft 365, Google Workspace or another provider while keeping your website with us. You need to do two things in cPanel: update the MX records, and tell the server that mail for the domain is now handled elsewhere.
These steps apply if your domain uses our nameservers. If your DNS is hosted elsewhere, change the MX records there, but still complete step 2 below.
1. Replace the MX records
- Get the exact MX record values from your new provider's admin console. Each provider gives you a hostname and a priority.
- In cPanel, go to Domains › Zone Editor and click Manage next to your domain.
- Click Filter › MX to show only MX records.
- Click Edit on the existing record and replace the Destination with your provider's hostname and its Priority. Then click Save Record. If the provider gives you more than one MX record, add the others with Add Record › Add "MX" Record.
- Delete any old MX records that still point to our server (usually
example.co.ukormail.example.co.uk). If you leave them in place, some mail will keep arriving here.
The lowest priority number is tried first.
2. Set Email Routing to Remote
- Go to Email › Email Routing and choose your domain.
- Select Remote Mail Exchanger and click Change.
This step matters. If routing stays on Local Mail Exchanger, our server still thinks it owns your mail. Messages sent from your website (contact forms, WordPress notifications) or from other accounts on the same server will then be delivered to the old local mailboxes instead of your new provider. Automatically Detect Configuration usually picks the right option once the new MX records are in place, but setting Remote explicitly is safer.
If you later move your email back to us, set the MX record back to your own domain and choose Local Mail Exchanger.
3. Update your SPF record
Your SPF record must authorise the new provider to send mail for your domain, or your messages may land in spam. In the Zone Editor, edit the TXT record that starts v=spf1 and add the include: value your provider gives you. Microsoft 365, for example, uses include:spf.protection.outlook.com. Keep a single SPF record. If your website still sends mail from our server, keep the existing entries as well. See how to set up SPF, DKIM and DMARC for the full picture, including DKIM for your new provider.
Check it worked
Run your domain through our email checker to confirm the new MX and SPF records are visible. Allow time for propagation (see checking DNS propagation). Before you cancel or delete the old mailboxes, copy any mail you want to keep across to the new provider.