{"id":572,"date":"2026-11-17T01:12:26","date_gmt":"2026-11-17T06:42:26","guid":{"rendered":"https:\/\/photonconsole.com\/blog\/?p=572"},"modified":"2026-11-17T09:12:55","modified_gmt":"2026-11-17T14:42:55","slug":"email-provider-migration-checklist-40-items-before-you-switch","status":"publish","type":"post","link":"https:\/\/photonconsole.com\/blog\/email-provider-migration-checklist-40-items-before-you-switch\/","title":{"rendered":"Email Provider Migration Checklist: 40 Items Before You Switch"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Migrations rarely fail on a missing step. They fail on a step nobody owned.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Someone assumed the DNS change was handled because someone else mentioned DNS in a meeting. The suppression list was exported, but only for the primary domain. The rollback plan existed, in the sense that somebody said, &#8220;We can always switch back,&#8221; out loud.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is the list of 40 checks, grouped into the seven phases they belong to, with the reason each one matters. Work through it with a name against every line.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Quick Answer: The Seven Phases<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Phase<\/th><th>Items<\/th><th>When<\/th><\/tr><\/thead><tbody><tr><td>Authentication and DNS<\/td><td>1\u20138<\/td><td>Before any traffic moves<\/td><\/tr><tr><td>Data and suppression<\/td><td>9\u201314<\/td><td>Before the first production send<\/td><\/tr><tr><td>Integrations and code<\/td><td>15\u201322<\/td><td>Before the first production send<\/td><\/tr><tr><td>Content and templates<\/td><td>23\u201327<\/td><td>Before the first production send<\/td><\/tr><tr><td>Monitoring and measurement<\/td><td>28\u201333<\/td><td>Before you ramp past 5%<\/td><\/tr><tr><td>Rollback readiness<\/td><td>34\u201337<\/td><td>Before you ramp past 5%<\/td><\/tr><tr><td>Sign-off<\/td><td>38\u201340<\/td><td>Before stage 1<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Three items cause most incidents: <strong>item 2<\/strong> (SPF lookup count), <strong>item 12<\/strong> (suppressions imported before the first send) and <strong>item 18<\/strong> (no duplicate send path). If you only verify three things, verify those.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Use This<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large is-resized\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Pre-Flight-Send-Gates-1024x576.png\" alt=\"Timeline diagram showing which email migration checklist phases must be clear before the first production send and which are re-verified at each rollout stage.\" class=\"wp-image-574\" style=\"aspect-ratio:1.7777777777777777;width:1200px;height:auto\" srcset=\"https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Pre-Flight-Send-Gates-1024x576.png 1024w, https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Pre-Flight-Send-Gates-300x169.png 300w, https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Pre-Flight-Send-Gates-768x432.png 768w, https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Pre-Flight-Send-Gates-1536x864.png 1536w, https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Pre-Flight-Send-Gates.png 1672w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\">Four phases gate the first send. Two gate the ramp. Sign-off comes before any of it.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Two rules make the difference between a checklist that works and one that gets pasted into a document and forgotten.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Every item needs a named owner, not a team.<\/strong> &#8220;Platform team&#8221; is not an owner. An item assigned to a group is an item assigned to nobody, and those are the ones that turn up unfinished at 50% rollout.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>This is a gate, not a one-time pass.<\/strong> Items 28\u201337 get re-checked at every ramp stage, because what was true at 5% can stop being true at 50% \u2014 alerts that never fired, a rollback path that quietly broke when someone cleaned up an unused environment variable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Common Mistake<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Treating the checklist as pre-flight only. Teams work through all 40 items carefully, start the ramp, and never look at the list again \u2014 which is exactly when the monitoring and rollback items start to decay. The rollback was verified in week one; by week three somebody has rotated the old provider&#8217;s credentials during a routine security sweep, and the rollback that everyone believes in no longer exists. Re-run phases 5 and 6 at the start of every ramp stage. It takes ten minutes and it is the difference between having a rollback and believing you have one.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This checklist covers <em>what<\/em> to verify. It deliberately does not cover the order in which to move traffic \u2014 that is in our guide to <a href=\"https:\/\/photonconsole.com\/blog\/migrate-email-provider-without-downtime\/\">migrating email providers without downtime<\/a>, and the measurement method is in <a href=\"https:\/\/photonconsole.com\/blog\/dual-email-provider-setup\/\">running two email providers during a migration<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Phase 1: Authentication and DNS (Items 1\u20138)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Authentication failures are one of the most common causes of email delivery problems, and during a migration they are the most likely thing to break both providers at once rather than just the new one.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>#<\/th><th>Check<\/th><th>Why it matters<\/th><\/tr><\/thead><tbody><tr><td>1<\/td><td>New provider&#8217;s include added to SPF, with the old one still present<\/td><td>Both must be authorised during the parallel run<\/td><\/tr><tr><td>2<\/td><td><strong>Total SPF DNS lookups counted and confirmed under ten<\/strong><\/td><td>Exceeding it returns <code>permerror<\/code> and fails authentication for <em>both<\/em> providers simultaneously<\/td><\/tr><tr><td>3<\/td><td>DKIM published on a new selector, independent of the old provider&#8217;s<\/td><td>Independent selectors let both sign in parallel with no conflict<\/td><\/tr><tr><td>4<\/td><td>The DKIM signature was verified on a real send, not just a published record<\/td><td>A record that resolves is not proof the signature validates<\/td><\/tr><tr><td>5<\/td><td>DMARC record present with a policy of at least <code>p=none<\/code><\/td><td>Google requires a DMARC record from bulk senders<\/td><\/tr><tr><td>6<\/td><td>From-domain alignment confirmed on SPF or DKIM<\/td><td>Only one needs to align, but one must<\/td><\/tr><tr><td>7<\/td><td>TTLs lowered at least one full old-TTL period before cutover<\/td><td>Lowering a TTL only takes effect after the old one expires everywhere<\/td><\/tr><tr><td>8<\/td><td>Any sending subdomain has an A or MX record in public DNS<\/td><td>Some receivers treat a subdomain with neither with more suspicion<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Item 2 is the one that bites hardest. The ten-term limit is specified in <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc7208.html\" target=\"_blank\" rel=\"noopener\">RFC 7208<\/a>, and it counts <code>include<\/code>, <code>a<\/code>, <code>mx<\/code>, <code>ptr<\/code>, <code>exists<\/code> and <code>redirect<\/code> \u2014 but not <code>ip4<\/code>, <code>ip6<\/code> or <code>all<\/code>. Adding one more provider&#8217;s include is often what tips a long-standing record over the edge. Verify with <a href=\"https:\/\/mxtoolbox.com\/\" target=\"_blank\" rel=\"noopener\">MXToolbox<\/a> and the free <a href=\"https:\/\/www.photonconsole.com\/email-deliverability-checker.php\">email deliverability checker<\/a>, and see our guide to <a href=\"https:\/\/photonconsole.com\/blog\/spf-dkim-dmarc-explained-simply\/\">SPF, DKIM and DMARC<\/a> for the mechanics.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Phase 2: Data and Suppression (Items 9\u201314)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>#<\/th><th>Check<\/th><th>Why it matters<\/th><\/tr><\/thead><tbody><tr><td>9<\/td><td>Suppressions exported from <em>every<\/em> list type the old provider keeps<\/td><td>Some providers split them into several separate lists<\/td><\/tr><tr><td>10<\/td><td>Exported per sending domain, and per stream where the provider has them<\/td><td>Suppression data is often scoped below the account level<\/td><\/tr><tr><td>11<\/td><td>Export stored in your own system, not only uploaded to the new provider<\/td><td>This is your data; the next migration should not need an export at all<\/td><\/tr><tr><td>12<\/td><td><strong>Hard bounces and complaints are imported before the first production send<\/strong><\/td><td>A new sending identity with no bounce history gets judged hardest on its first sends<\/td><\/tr><tr><td>13<\/td><td>Explicit decision on which categories <em>not<\/em> to import<\/td><td>Provider-side blocks reflect that provider&#8217;s infrastructure, not your recipients<\/td><\/tr><tr><td>14<\/td><td>Final re-export scheduled for the last day of the parallel run<\/td><td>Addresses that bounced during the ramp exist only on the old provider<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Item 13 catches people out. Not every suppression is about the recipient \u2014 some record the old provider&#8217;s own delivery decisions, and importing those carries another company&#8217;s infrastructure history into your new setup. Our guide to <a href=\"https:\/\/photonconsole.com\/blog\/how-to-reduce-email-bounce-rate-for-saas-applications-a-production-infrastructure-guide\/\">reducing bounce rate<\/a> covers why the first sends from a new identity matter disproportionately.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Phase 3: Integrations and Code (Items 15\u201322)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>#<\/th><th>Check<\/th><th>Why it matters<\/th><\/tr><\/thead><tbody><tr><td>15<\/td><td>Every send site found by grepping for the old provider&#8217;s hostname and SDK<\/td><td>A forgotten cron job or admin tool keeps sending after cutover<\/td><\/tr><tr><td>16<\/td><td>All old credentials inventoried, including any in CI and in staging<\/td><td>Credentials in a pipeline are the ones nobody remembers<\/td><\/tr><tr><td>17<\/td><td>Routing by recipient hash implemented, percentage in configuration<\/td><td>A rollback that needs a deploy is not a rollback<\/td><\/tr><tr><td>18<\/td><td><strong>One send site, one decision, one provider \u2014 no duplicate path<\/strong><\/td><td>Adding a second call rather than routing causes duplicate delivery<\/td><\/tr><tr><td>19<\/td><td>New provider&#8217;s webhook endpoint deployed and publicly reachable<\/td><td>Events you cannot receive are events you cannot compare<\/td><\/tr><tr><td>20<\/td><td>Webhook signature verification implemented and tested against a real event<\/td><td>Signing schemes differ entirely between providers<\/td><\/tr><tr><td>21<\/td><td>Every payload shape the new provider sends is handled<\/td><td>Some providers post more than one shape depending on the event source<\/td><\/tr><tr><td>22<\/td><td>Inbound mail checked \u2014 MX records and any routing rules<\/td><td>If the old provider also receives mail, that is a second migration<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Item 22 is the one most likely to be missed entirely, because inbound routing is configured once and then never touched. Its failure is silent in both directions: senders get a bounce you never see, and your application simply stops receiving the posts it used to. See <a href=\"https:\/\/photonconsole.com\/blog\/migrate-from-mailgun\/\">migrating from Mailgun<\/a> for the reimplementation pattern, and the <a href=\"https:\/\/www.photonconsole.com\/smtp-relay-api.php\">SMTP relay API<\/a> reference for the sending side. PhotonConsole issues SMTP credentials on signup, so items 17 to 21 can be built and tested against a live endpoint before any production traffic moves.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Quick Fix<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Five Items That Cause Most Incidents<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Item 2<\/strong> \u2014 SPF lookups over ten returns <code>permerror<\/code> and breaks both providers at once<\/li>\n\n\n\n<li><strong>Item 12<\/strong> \u2014 suppressions imported after the first send instead of before<\/li>\n\n\n\n<li><strong>Item 18<\/strong> \u2014 a second provider call added rather than traffic routed, causing duplicate delivery<\/li>\n\n\n\n<li><strong>Item 22<\/strong> \u2014 inbound mail forgotten, failing silently for days<\/li>\n\n\n\n<li><strong>Item 36<\/strong> \u2014 old credentials rotated mid-migration, destroying the rollback nobody re-tested<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Phase 4: Content and Templates (Items 23\u201327)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>#<\/th><th>Check<\/th><th>Why it matters<\/th><\/tr><\/thead><tbody><tr><td>23<\/td><td>Templates exported into version control, not into another provider&#8217;s store<\/td><td>Version-controlled templates make the next change a config edit<\/td><\/tr><tr><td>24<\/td><td>Layouts or shared wrappers flattened or reproduced<\/td><td>A template exported without its wrapper looks almost right<\/td><\/tr><tr><td>25<\/td><td>Every template rendered against missing and null variables<\/td><td>Renderers differ on undefined values: blank, literal placeholder, or error<\/td><\/tr><tr><td>26<\/td><td>Marketing mail carries a one-click unsubscribe with an HTTPS URL<\/td><td>Required by Google for bulk marketing mail, per RFC 8058<\/td><\/tr><tr><td>27<\/td><td>Tracking and link domains updated where the provider rewrites URLs<\/td><td>Links pointing at a decommissioned tracking domain break after teardown<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">On item 26, <a href=\"https:\/\/support.google.com\/a\/answer\/14229414\" target=\"_blank\" rel=\"noopener\">Google&#8217;s bulk sender requirements<\/a> ask for one-click unsubscribe on marketing and promotional messages, implemented with <code>List-Unsubscribe<\/code> headers under <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc8058.html\" target=\"_blank\" rel=\"noopener\">RFC 8058<\/a>, including one HTTPS URL in the header. Transactional mail is exempt. A mailto link or a link in the body does not satisfy it, and Google recommends fulfilling requests within 48 hours.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Phase 5: Monitoring and Measurement (Items 28\u201333)<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large is-resized\"><img decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Signed-Off-Ownership-Infographic-1024x576.png\" alt=\"A migration checklist ledger with team placeholders and vague criteria compared with one carrying a single named owner and a numeric criterion for each item\" class=\"wp-image-575\" style=\"aspect-ratio:1.7777777777777777;width:1200px;height:auto\" srcset=\"https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Signed-Off-Ownership-Infographic-1024x576.png 1024w, https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Signed-Off-Ownership-Infographic-300x169.png 300w, https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Signed-Off-Ownership-Infographic-768x432.png 768w, https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Signed-Off-Ownership-Infographic-1536x864.png 1536w, https:\/\/photonconsole.com\/blog\/wp-content\/uploads\/2026\/11\/Photon-Console_-Signed-Off-Ownership-Infographic.png 1672w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\">An item owned by a team is an item owned by nobody. Names, numbers and a date.<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>#<\/th><th>Check<\/th><th>Why it matters<\/th><\/tr><\/thead><tbody><tr><td>28<\/td><td>Both providers&#8217; events normalised into one vocabulary of your own<\/td><td>Two dashboards both reading 99.2% are not measuring the same thing<\/td><\/tr><tr><td>29<\/td><td>Unmapped event types logged and counted, never silently discarded<\/td><td>A dropped bounce category makes a provider look better than it is<\/td><\/tr><tr><td>30<\/td><td>Rates reported segmented by receiving domain, not only as an average<\/td><td>A problem at Gmail and none at Outlook is a finding an average hides<\/td><\/tr><tr><td>31<\/td><td>Google Postmaster Tools access confirmed for every sending domain<\/td><td>Provider-reported delivery is acceptance, not inbox placement<\/td><\/tr><tr><td>32<\/td><td>Seed inbox tests scheduled on both paths<\/td><td>Shows where mail lands rather than whether it was accepted<\/td><\/tr><tr><td>33<\/td><td>Alerts configured on bounce rate and complaint rate thresholds<\/td><td>Nobody watches a dashboard at 3am on the third day of a ramp<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">For item 31, <a href=\"https:\/\/postmaster.google.com\/\" target=\"_blank\" rel=\"noopener\">Postmaster Tools<\/a> reports spam rate and domain reputation from Google&#8217;s side. Google asks senders to stay below 0.1% user-reported spam and to prevent the rate from ever reaching 0.3%; a sender above 0.3% is ineligible for mitigation until it has stayed below that for seven consecutive days. Those are the numbers to put in item 39. <a href=\"https:\/\/www.mail-tester.com\/\" target=\"_blank\" rel=\"noopener\">Mail Tester<\/a> covers item 32 for individual messages.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Phase 6: Rollback Readiness (Items 34\u201337)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>#<\/th><th>Check<\/th><th>Why it matters<\/th><\/tr><\/thead><tbody><tr><td>34<\/td><td>Rollback to 0% achievable without a deploy<\/td><td>If reverting needs a release, you cannot abort quickly<\/td><\/tr><tr><td>35<\/td><td>Old provider still fully functional \u2014 not downgraded, paused or cancelled<\/td><td>A downgraded plan may not handle 100% of your volume any more<\/td><\/tr><tr><td>36<\/td><td><strong>Old provider&#8217;s credentials still valid and excluded from rotation<\/strong><\/td><td>A routine security sweep silently destroys the rollback<\/td><\/tr><tr><td>37<\/td><td>Rollback executed once, in production, at a low percentage<\/td><td>An untested rollback is a plan, not a capability<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Item 37 is the one people resist and the one worth insisting on. Take the rollout from 5% to 0%, confirm mail still flows entirely through the old provider, then put it back. Ten minutes, during business hours, while the stakes are low. The alternative is discovering at 50% that the revert path has a bug.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Phase 7: Sign-Off (Items 38\u201340)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>#<\/th><th>Check<\/th><th>Why it matters<\/th><\/tr><\/thead><tbody><tr><td>38<\/td><td>A named individual against every item above<\/td><td>An item owned by a team is owned by nobody<\/td><\/tr><tr><td>39<\/td><td>Numeric exit criteria agreed in writing before stage 1<\/td><td>A ramp without criteria ends when somebody gets bored<\/td><\/tr><tr><td>40<\/td><td>A decommissioning date set, with the teardown order written down<\/td><td>Migrations that are never finished leave credentials live indefinitely<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Quick Fix<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Day Before Cutover<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Re-verify SPF resolves and the lookup count is still under ten<\/li>\n\n\n\n<li>Confirm the old provider&#8217;s credentials are still valid \u2014 test an actual send<\/li>\n\n\n\n<li>Re-export suppressions from the old provider and import them<\/li>\n\n\n\n<li>Check that alerts from item 33 have fired at least once in testing<\/li>\n\n\n\n<li>Confirm nothing else ships today: no template release, no DNS edit, no campaign<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Note<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Items 39 and 40 look like paperwork and are the two that most often decide whether the migration ends. Without agreed numbers, a single hard bounce in a small cohort becomes an argument rather than a data point, and the ramp stalls at 5% indefinitely. Without a decommissioning date, the old provider stays live for months with valid credentials and an open invoice, which is both a cost and a security exposure. Set both before stage 1, when nobody is under pressure and the discussion is cheap.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pro Tips<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Put a name, not a team, against every line.<\/strong> This single change catches more than any individual item.<\/li>\n\n\n\n<li><strong>Count your SPF lookups before adding anything.<\/strong> It is the one mistake that breaks both providers at once.<\/li>\n\n\n\n<li><strong>Import suppressions before the first send, never after.<\/strong> First impressions on a new sending identity are expensive.<\/li>\n\n\n\n<li><strong>Grep for the provider&#8217;s hostname, not its SDK name.<\/strong> The hostname appears in config files the SDK search misses.<\/li>\n\n\n\n<li><strong>Test the rollback for real, at 5%.<\/strong> Ten minutes to turn a plan into a capability.<\/li>\n\n\n\n<li><strong>Exclude the old provider&#8217;s credentials from rotation<\/strong> until teardown, and tell whoever runs the sweep.<\/li>\n\n\n\n<li><strong>Re-run phases 5 and 6 at every ramp stage.<\/strong> Monitoring and rollback decay quietly.<\/li>\n\n\n\n<li><strong>Change one thing at a time.<\/strong> A template release during a ramp invalidates the week&#8217;s data.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Related Reading<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This checklist is the hub for our migration cluster. Each article below covers one part in depth:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/photonconsole.com\/blog\/migrate-email-provider-without-downtime\/\">Migrating email providers without downtime<\/a> \u2014 the sequence and timing, ordered by reversibility<\/li>\n\n\n\n<li><a href=\"https:\/\/photonconsole.com\/blog\/dual-email-provider-setup\/\">Running two email providers during a migration<\/a> \u2014 recipient hashing, event normalisation and exit criteria<\/li>\n\n\n\n<li><a href=\"https:\/\/photonconsole.com\/blog\/migrate-from-sendgrid\/\">Migrating away from SendGrid<\/a> \u2014 where templates and multiple suppression lists are the lock-in<\/li>\n\n\n\n<li><a href=\"https:\/\/photonconsole.com\/blog\/migrate-from-amazon-ses\/\">Migrating from Amazon SES<\/a> \u2014 where an AWS dependency graph is the lock-in<\/li>\n\n\n\n<li><a href=\"https:\/\/photonconsole.com\/blog\/migrate-from-mailgun\/\">Migrating from Mailgun<\/a> \u2014 where inbound routing is the forgotten half<\/li>\n\n\n\n<li><a href=\"https:\/\/photonconsole.com\/blog\/migrate-from-postmark\/\">Migrating from Postmark<\/a> \u2014 where an enforced architecture is the lock-in<\/li>\n\n\n\n<li><a href=\"https:\/\/photonconsole.com\/blog\/spf-dkim-dmarc-explained-simply\/\">SPF, DKIM and DMARC explained simply<\/a> \u2014 the authentication records in phase 1<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What is the most commonly missed item in an email provider migration?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Inbound mail. If the old provider also receives mail through an MX record, that is a second migration with its own cutover, and its failure is silent in both directions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Which item breaks migrations most often?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The SPF lookup count. Adding a second provider&#8217;s include can push the record past the ten-term limit, which returns <code>permerror<\/code> and fails authentication for both providers at the same time.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should I import every suppression list from my old provider?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Import hard bounces and complaints, which are facts about recipients. Decide deliberately about provider-side blocks, which reflect that provider&#8217;s infrastructure rather than your recipients.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When should suppression data be imported?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Before the first production send. A new sending identity has no bounce history, so mailing previously-bounced addresses from it teaches receivers that this identity sends to addresses that do not exist.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I avoid sending duplicate emails during a migration?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Route rather than add. One send site makes one decision and calls one provider. Adding a second provider call alongside the existing one causes duplicate delivery and corrupts your comparison data.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What spam rate should trigger a rollback?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Google asks senders to stay below 0.1% and to prevent the rate from ever reaching 0.3%. At or above 0.3% a sender is ineligible for mitigation until seven consecutive days below it, which makes 0.3% a sensible hard stop.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I really need to test the rollback?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. Take the rollout from 5% to 0% in production, confirm mail flows through the old provider, then restore it. An untested rollback is a plan rather than a capability.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How long should I keep the old provider after reaching 100%?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Around two weeks, fully functional and with valid credentials. Set the decommissioning date in advance so the account does not stay live for months.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does every item need an individual owner?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Because an item assigned to a team is assigned to nobody. Items owned by groups are the ones that turn up unfinished halfway through a ramp.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Forty items sounds like a lot until you consider that most of them take under five minutes and three of them prevent the incidents that make migrations memorable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you do nothing else from this list, do these: count your SPF lookups before adding a provider, import suppressions before the first send rather than after, and confirm you have one send site making one decision rather than two calls running side by side. Those three cover the failures that produce duplicate invoices, authentication outages affecting both providers, and a burst of bounces on a brand-new sending identity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then do the two that feel like administration. Put a person&#8217;s name against every line, and agree the numbers that mean proceed, hold and roll back before the first percent of traffic moves. Checklists do not fail because items are missing. They fail because nobody owned the one that mattered, and because without agreed criteria a single bounce becomes an argument instead of a data point.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Done properly, what you keep is worth more than the switch itself: templates in version control, a suppression list you own, and an event vocabulary that is not shaped around one vendor&#8217;s API. At that point the next migration is a configuration change. If you are still choosing a destination, our <a href=\"https:\/\/www.photonconsole.com\/compare.php\">comparison page<\/a> sets the options side by side, and <a href=\"https:\/\/www.photonconsole.com\/\">PhotonConsole<\/a> issues credentials on signup so the new path can be live and testable while you work through phase 1.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Read More<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.photonconsole.com\/email-deliverability-checker.php\">Free Email Deliverability Checker<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.photonconsole.com\/quickstart.php\">PhotonConsole Quickstart<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.photonconsole.com\/smtp-relay-api.php\">SMTP Relay API Documentation<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.photonconsole.com\/compare.php\">Compare Email Delivery Providers<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/photonconsole.com\/blog\/migrate-email-provider-without-downtime\/\">Migrating Email Providers Without Downtime<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/photonconsole.com\/blog\/dual-email-provider-setup\/\">Running Two Email Providers During a Migration<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.photonconsole.com\/relay.php\">PhotonRelay: SMTP Relay Service<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.photonconsole.com\/pricing.php\">PhotonConsole Pricing<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Migrations rarely fail on a missing step. They fail on a step nobody owned. Someone assumed the DNS change was handled because someone else mentioned DNS in a meeting. The suppression list was exported, but only for the primary domain. The rollback plan existed, in the sense that somebody said, &#8220;We can always switch back,&#8221; [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":573,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[597,598],"class_list":["post-572","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-email-deliverability","tag-forty-checks-across-seven-phases","tag-from-spf-lookups-to-sign-off-migrations-rarely-fail-on-a-missing-step-they-fail-on-the-step-nobody-owned"],"_links":{"self":[{"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/posts\/572","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/comments?post=572"}],"version-history":[{"count":1,"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/posts\/572\/revisions"}],"predecessor-version":[{"id":576,"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/posts\/572\/revisions\/576"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/media\/573"}],"wp:attachment":[{"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/media?parent=572"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/categories?post=572"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/photonconsole.com\/blog\/wp-json\/wp\/v2\/tags?post=572"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}