Before you change MX records and move business email, verify that the domain is under your control, DNS is ready for the new provider, and inbound test messages can reach the destination. This checklist prevents the most common cutover failures: missing Cloudflare zones, premature MX changes, and untested receiving.
Why Pre-Move Verification Prevents Downtime
Changing MX records is irreversible in the short term. If the new provider cannot receive mail or DNS propagation is incomplete, messages bounce or disappear. Verifying ownership, zone control, and basic DNS readiness first lets you test inbound delivery while the old MX is still active, then cut over with confidence. Rollback becomes straightforward when you have a documented pre-state.
How We Structured This Verification Process
The sequence follows Arawa Mail’s documented domain onboarding flow and general email migration best practices. We prioritize checks that must succeed before any MX change (Cloudflare zone control for non-registered domains, receiving activation) and place optional authentication records (SPF/DKIM) in the correct order relative to sending activation. All Arawa-specific steps are drawn from the official domain-onboarding and Cloudflare-requirements pages.
Pre-Migration Domain Verification Checklist
- Confirm domain ownership and DNS control. You must be able to edit DNS. For domains not registered through Arawa, the domain must already be an active zone in Cloudflare whose name matches exactly. See Cloudflare requirements.
- Add the domain in Arawa Mail and review status. Open Domains, add the domain if needed, and note the three statuses (Domain, Receiving, Sending). Follow domain onboarding.
- Activate receiving first. Click Activate receiving and complete the Cloudflare OAuth flow if required. Confirm receiving shows as active before proceeding. This publishes the MX records under Arawa’s control.
- Test inbound delivery while the old MX may still be partially active. Send a test message from an external account to a mailbox you create after receiving is active. Verify it arrives in the Arawa inbox.
- Prepare authentication records but do not cut MX yet. Activate sending when ready; this adds DKIM and MAIL FROM records. Publish or update SPF to include the new provider. Do not lower TTL or change MX until tests pass.
- Document current MX, SPF, and DKIM. Record the existing records and TTLs so you can roll back quickly if needed. Our migration checklist covers the cutover itself.
- Create user accounts only after receiving is confirmed. Accounts become usable once receiving is active.
Cloudflare and DNS Specific Checks
For domains not registered with Arawa:
- The Cloudflare zone name must match the domain exactly (example.com, not www.example.com or a subdomain unless that is the email domain).
- The connected Cloudflare account must have permission to edit DNS.
- Existing MX records will be warned about; confirm you are ready to replace them only after receiving activation succeeds.
Domains registered through Arawa skip the Cloudflare step; records are published directly.
Internal Links and Next Steps
- How to Connect a Cloudflare Domain to ArawaMail
- Custom-Domain Email Migration Checklist
- How to Move Business Email Off Google Workspace
- SPF, DKIM, and DMARC explained
- Official docs: domain onboarding and sending
FAQ
Do I need Cloudflare for every domain?
Only for domains not registered through Arawa. Registered domains use Arawa’s nameservers and skip Cloudflare.
Should I change MX before activating receiving?
No. Activate receiving in Arawa first so the correct MX can be published under controlled conditions, then test, then finalize any remaining cutover.
How do I test inbound before the full cutover?
After receiving is active, create a mailbox and send a test message from an external address. Confirm arrival before lowering old MX TTLs or removing old records.
What if activation fails?
Return to the domain details page and retry. Check that the Cloudflare zone is active and the account has DNS write access. Reset only if you need to start over completely.