Changing or removing MX records during an email migration

Create destination mailboxes and preserve access to the old provider. Record every existing MX destination and priority, and prepare the new provider’s exact instructions. Lower TTL in advance when you control the zone and the migration schedule permits it.

1. Open Zone Editor > Manage for the authoritative domain and filter by MX.
2. Edit or add the complete destination MX set supplied by the new provider. Check both hostnames and priorities.
3. Remove obsolete entries when the cutover plan calls for it. An old MX with a higher numeric priority can still receive mail if preferred servers fail, so do not retain it casually.
4. Update cPanel Email Routing and outgoing authentication records as required by the new mail design.
5. Query public MX answers and send tests from independent external senders. Continue checking the old provider during the cache-transition period and complete any final message synchronisation.

New mail should arrive at the new service, and website-generated messages should use the intended route. Verify both sending and receiving with real mailbox tests.

If delivery fails, read the bounce details and compare the published set with the provider’s exact requirements. Restore the recorded old MX set only if the old service remains ready to receive mail. Deleting every MX record is not a safe way to disable email because fallback behaviour can still occur.

• Adding MX records for an email provider in cPanel
• Editing or deleting a DNS record in cPanel Zone Editor
• Creating a mailbox in SiteWorx
• Changing or removing a cPanel CNAME alias

• cPanel: Zone Editor
• cPanel: Email Routing