Provision the new provider’s mailboxes, migrate required messages and obtain its exact MX priorities and authentication records. Save the current routing information and choose a controlled migration window.

1. Confirm which service hosts authoritative DNS. Publish the new provider’s required MX records there, retaining only records that belong to the intended routing design.
2. Open Administration > Mail Options > Remote Setup in SiteWorx.
3. Disable local delivery for the intended domain and confirm the action. This is separate from editing public MX records.
4. If SiteWorx DNS is authoritative, use its remote MX controls to add or edit the supplied mail-server hostnames and preference values. Lower preference numbers have higher priority.
5. Test incoming mail from an external sender and messages generated by the hosted website. Verify replies, authentication and all required aliases before retiring the old service.

Both external senders and local applications should deliver to the new provider. DNS caches may temporarily retain previous records, so monitor both sides during the planned transition.

If local email management disappears after disabling delivery, that is expected for the affected domain. Re-enabling local delivery is not a general fix for an external mailbox issue; it can split mail between systems.

No. MX controls future routing. Existing mail, contacts and calendars need an appropriate migration or export process before the old mailbox service is closed.

• Publishing SiteWorx SPF without creating multiple SPF records
• Enabling and publishing SiteWorx domain signing records
• Adding and editing DNS records in SiteWorx
• Creating a SiteWorx email group for several recipients

• InterWorx: Remote Guide