The short version
Move the complete email configuration, not just the website records. Capture the working BIMI names and values before switching nameservers, then verify the new authoritative answers and actual mail.
Capture a baseline before touching the zone
A DNS move can look successful because the website loads while an email-related record has been missed. Export the current zone and make a separate inventory of your BIMI selectors, their complete hostnames and their values. Include any CNAME targets that another service controls.
Keep the export in the normal change record. Also record the asset URLs and a recent working message from each important sending stream. These are your comparison points if a logo disappears after the move.
Translate names carefully between DNS editors
Google’s DNS instructions note that some editors append the domain automatically. A full name copied into a relative-name field can therefore create the wrong hostname.
For a fictional example.com zone, the desired default name is default._bimi.example.com. Check the resulting name, not just the text visible in the form. Preserve one intended configuration at each selector and inspect delegated targets separately.
Use a small cutover worksheet
| Item | Evidence to retain |
|---|---|
| BIMI names and values | Old and new authoritative answers |
| Authentication records | MX, SPF, DKIM and DMARC inventory comparison |
| Hosted assets | Exact public URLs and retrieval results |
| Mail behaviour | Post-change message authentication and receiver observation |
Coordinate any TTL changes in advance with your DNS administrator. Previously cached answers do not disappear just because the new zone is ready. Avoid combining the DNS move with a logo change or certificate replacement unless the dependencies are explicitly planned.
Close the move with evidence from the new service
Check the new authoritative service and a public lookup after the delegation change. If those disagree, investigate delegation and caching before editing the BIMI value repeatedly. If both are correct but the logo is missing, compare a new message with your saved baseline.
Keep the old service available for the agreed transition period and document who can revert the change if necessary. A successful website check should close the website task; email configuration needs its own sign-off.
Sources & further reading
Sources checked on . Requirements can change; check the original guidance when implementing. Planning checklists and examples are BIMI World’s editorial suggestions.