Bringing an existing domain to Inboxlee: the migration playbook
Move a working domain into Inboxlee without dropping mail. DNS-first migration, mailbox-first migration, and the gotchas.
Rejwan Nirob·Jan 26, 2026·6 min readInboxlee can manage existing domains, not just newly provisioned ones. The migration takes more care than a fresh setup because there is live mail to protect during the transition.
Pre-migration audit
Before doing anything, audit the existing setup. Run dig MX, dig TXT, dig _dmarc on the domain. Note current SPF includes, DKIM selectors, and DMARC policy. Inboxlee's wizard does this automatically and surfaces conflicts.
DNS-first migration
Recommended path. Move DNS to Cloudflare (or accept Inboxlee's default nameservers). Inboxlee re-applies SPF, DKIM, DMARC, MX with safe values, merging existing includes where conflict-free. Mail continues flowing through the existing mailbox while DNS is verified. Then add new mailboxes under Inboxlee management.
Mailbox-first migration
Faster but riskier. Provision new Inboxlee mailboxes directly under the existing domain without touching DNS first. Works if the existing setup is clean. Fails silently if SPF or DKIM conflicts exist.
The gotchas
- Existing TXT records over the 255-char limit can corrupt during transfer - verify post-migration
- CNAME flattening at apex sometimes breaks DKIM if the registrar handles CNAMEs differently
- DMARC reports may temporarily route to two destinations - that is normal during a 7-day overlap window
- Auto-renew settings do not transfer between registrars - verify and re-enable
Inboxlee's migration wizard scans your existing DNS, flags conflicts before any change, and walks the migration step by step. No downtime, no surprise drops.
Migrate a domainFrequently asked
Can I bring an existing domain to Inboxlee or do I have to buy a new one?
You can bring an existing domain. The MagicLee wizard has a "Bring your own domain" path that audits current DNS (SPF, DKIM, DMARC, MX), flags any conflicts before any change is made, and walks the migration step by step. No downtime, no surprise drops if the audit comes back clean.
What is the safest way to migrate a working cold-email domain to Inboxlee?
DNS-first migration. Move DNS to Cloudflare (or accept Inboxlee's default nameservers), let Inboxlee re-apply SPF/DKIM/DMARC/MX with safe values (merging existing includes where conflict-free), and verify before adding new mailboxes. Mail continues flowing through the existing mailbox during the transition. Mailbox-first migration is faster but breaks silently if existing SPF or DKIM conflicts.
Will mail drop during a domain migration to Inboxlee?
Not if you follow the DNS-first migration path. Existing MX records keep delivering inbound mail until Inboxlee's new mailboxes are verified live. The risk windows are: (1) registrar nameserver propagation (5-30 min), (2) DKIM key rotation if the migration changes selectors. Inboxlee's wizard schedules around both to avoid drops.
What gotchas should I watch for when migrating a cold-email domain?
Four things: TXT records over 255 chars can corrupt during transfer (verify post-migration), CNAME flattening at apex sometimes breaks DKIM depending on registrar, DMARC reports may temporarily route to two destinations during the 7-day overlap (normal), and auto-renew settings do not transfer between registrars (verify and re-enable on the new registrar).