Keep the old email provider after migration only as a drain store. Read the old MX TTL, cut to one new owner, leave the old webmail open through that clock plus a day, then export and cancel. Keeping the old MX published is leftover MX with a calendar. MailerZ history cannot show mail that never arrived. The public address does not need two exchangers to stay safe.
Quick answer for keep old email provider after migration
Name what you are keeping. A mailbox login is a drain. An MX hostname is a second owner. Safe keep old email provider after migration setup is exclusive new MX plus a dated drain window. Unsafe setup is “leave Google MX at priority 20 until we are sure.” Product path: migration planner and troubleshooting. MX selection is in IETF RFC 5321 — Simple Mail Transfer Protocol. Names and TTLs are in IETF RFC 1035 — Domain names.
Google’s sitemap docs are about pages, not mail stores; see sitemaps and helpful content. A migration page that recommends keeping both MX for thirty days is leftover MX with a longer calendar.
Confirm MailerZ pricing. Free receives on one domain. Solo is $40 per year for send-as. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. No plan buys a reason to leave the old exchanger published. No inbox SLA.
The user problem and the decision criteria
Founders fear one missed invoice after cutover. The useful fear is stale cache. The useless fear is “what if we need the old hop forever.” The first fear has a clock. The second fear is how leftover MX survives a quarter and how two staffs keep opening two inboxes.
| Question | If yes | If no |
|---|---|---|
| Is the old MX still published? | You are split. Delete it. | You may be in a real drain. |
| Did you write the old TTL on the ticket? | You have a close date. | You will invent a quarter. |
| Is counsel asking for an archive? | Export. Do not keep MX. | Still export if tax needs it. |
| Are new invoices still landing in the old store? | Leftover MX or stale cache past the clock. | Drain is working or done. |
| Are you still paying the old seat next month? | Justify export or cancel. | Good if MX is already gone. |
Technical mail flow
After exclusive cut, new lookups should offer only the MailerZ hosts. Senders that still have the old answer cached will deliver to the old store until that answer expires. That is why you keep the old webmail password. It is not why you leave the old name in the zone. Published names attract new lookups after every cache miss.
IETF RFC 5321 — Simple Mail Transfer Protocol lets a sender stop after a 250 from the first willing host. If that host is still the old provider because you left its MX published, MailerZ never runs alias policy, HOLD, or SRS for that envelope. History stays empty. You conclude “MailerZ is quiet.” The old store is busy.
Self-send from Gmail to Gmail can skip public MX and invent a local win. Foreign probes after exclusive cut are the gate that the new owner works. The old store is then only for stragglers, not for proving the new hop.
Destination copies on MailerZ—two Gmails after one hop—are not a reason to keep the old provider. That is one owner and two stores. If two founders need the same public string, map two destinations. Do not keep Google MX to give the second founder a “backup inbox.”
Step-by-step setup and decision path
Read the old MX TTL before the window
Write the number and the close date. Screenshot the exclusive old set for rollback. Rollback is that file, not a leftover row you leave “just in case.”
Cut exclusively
Publish only MailerZ hosts. Delete old names the same hour. One owner. Confirm docs for the dashboard set you actually copy.
Query two public resolvers
If extras remain, you edited theater or the leftover product republished. Drain does not start until the listing is exclusive.
Foreign probe the new hop
Unique subject. History 250. Header From intact. Then search the destination. Self-send is not the gate.
Read the old store on a schedule
Once or twice a day through TTL plus a day. Move stragglers. Do not staff it as production.
Export, rotate, cancel
If counsel or tax needs the archive, export first. Rotate the old password. Cancel the seat. Re-query MX the next day in case a registrar save brought the row back.
Failure modes and proof
| What you see | Likely cause | Proof |
|---|---|---|
| New mail in old store after TTL plus a day | Leftover MX or republish | Second resolver still lists the old hostname |
| History empty, old store quiet | Wrong zone or missing alias | NS plus envelope name |
| 250 empty inbox | Filter or HOLD | Recovery |
| Old MX returned after website save | Registrar email or parking | MX changed after a panel click |
| Counsel asked to “keep email working” | Archive confused with MX | Export exists; MX listing is exclusive |
| Still paying the old seat next quarter | No close date | Ticket missing TTL and cancel owner |
Proof is an exclusive listing, a history row after cut, a drain log with dates, and a cancel confirmation. Agencies run this per zone. Client A can be cancelled while Client B is still in hour twelve of a 3600 TTL.
MailerZ workflow and product boundary
MailerZ is inbound MX plus authenticated SMTP. Envelope SRS only. Header From never rewritten. After exclusive cut it receives. It does not replace your need to drain the old store. It is not IMAP, not Workspace, not an open relay. Unhosted SMTP is 550 / 550 5.7.1.
HOLD stores unknown local-parts on Free. Free is one domain, three aliases, 14-day store, send-as disabled, SMTP and API disabled. Solo is $40 per year: 3 domains, 15 aliases, 90-day store, 1,000 outgoing, five outgoing per hour, unknowns forwarded. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm pricing. The 14-day or 90-day store is MailerZ retention, not a reason to keep old MX. Limits are not an inbox SLA. No SOC 2 claim lives here.
Features describe routing. They do not turn two MX products into one archive policy. Paid plans do not buy a quarter of leftover Google MX.
Cost, alternatives, and trade-offs
| Choice | What you get | What you give up |
|---|---|---|
| TTL plus a day, then cancel | Stragglers and a closed invoice | The comfort of a second live hop |
| Keep old MX for a month | A quiet second inbox | A complete archive in Gmail |
| Export then cancel same week | A file counsel can hold | Live old webmail after the clock |
| Buy a suite “as backup” | A store. Quote live | The Gmail you already use |
Time is a line item. A dated close costs less than a quarter of dual inboxes. Leftover MX costs more than Solo. A Free-plan send-as argument still costs more than the upgrade. Paying Workspace after exclusive MailerZ MX is either an archive you forgot to export or leftover MX you forgot to delete.
How to read the drain clock
Look up the old MX record before you delete it. If TTL is 300, drain can be short. If TTL is 86400, plan at least a day plus a human day for people who send from cached office resolvers. Some networks honor TTL loosely. The extra day is for humans, not for leaving the name published.
Some panels hide TTL or reset it when you save. Screenshot the value you actually had. If you cannot see TTL, assume a day, not a quarter. A quarter is leftover MX culture, not DNS.
Negative cache is a different clock. If someone looked up MX during a typo window, they may remember a failure. That does not justify republishing the old host. Fix the new set. Wait. Probe again. Republishing Google MX “so mail works while we debug” hides whether MailerZ is reachable.
IPv4 and IPv6 can expire independently. A sender that still has the old AAAA is a cache problem, not a reason to add the old MX back. Watch the old store. If arrivals continue after both clocks plus a day, you have a published leftover, not a cache.
Write the close date as a calendar day, not “when we feel sure.” Feeling sure is how leftover MX becomes the unofficial backup. Sure is two resolvers, a quiet old store, and an export if you need one.
Archive versus live MX
Legal hold is a copy you control. It is not a public exchanger. If counsel says keep the old provider, ask whether they need a mailbox login or a public MX. Almost always they need an export or a frozen store. Frozen stores do not require MX.
Tax invoices from last year live in the destination Gmail if they arrived there, or in the old export if they arrived before cut. They do not live in a leftover MX row. Keeping MX so “old invoices can still find us” is how new invoices split after you thought you migrated.
e-discovery tools want mailboxes and files. They do not want you to leave aspmx.l.google.com published next to MailerZ. If a vendor insists on a live mailbox, keep the login through the drain window, export, then disable mail receipt on that product if the vendor allows it—without republishing MX.
Two-factor on the old store still matters during drain. A stale password shared in Slack is how a former contractor reads stragglers. Rotate when you cancel. Do not send zone passwords to support.
MailerZ HOLD and store windows recover hops MailerZ accepted. They do not recover envelopes the old host accepted because you left its MX up. Open a held body for break-glass and expect an audit row. That is a control, not a SOC 2 badge.
When the invoice is leftover MX
If you still pay Google Workspace, Microsoft 365, a registrar email upsell, or a website-builder mailbox after exclusive MailerZ MX, write why. Valid why: you still use that product as a destination inbox or as a collaboration suite. Invalid why: you are afraid to delete MX. Destinations do not need their own MX on your domain.
Registrar included email often republishes MX when someone clicks Email in the domain panel. Re-query after every website save for a week after cancel. Keep old email provider after migration best practice is a re-query, not a second year of the upsell.
Parking MX and Cloudflare Routing leftovers are the same class. Branding does not change the coin flip. Delete the names. If Routing can republish, turn the product off. The Cloudflare migration guide covers that hop. This page covers the clock after any exclusive cut.
Send-as is a second job after inbound is exclusive. Free has no send-as. Do not keep old Workspace MX because you have not bought Solo yet. That mixes a 550 5.7.1 problem with leftover inbound. Upgrade when you need to send. Do not leave MX to compensate.
Night operators extend the old seat “until Monday.” Monday becomes a quarter. Put the cancel owner on the ticket before the window. If that person is on leave, name a deputy. Unowned cancel is leftover MX with a human face.
Agencies and per-zone close dates
An agency does not get one keep-the-old-provider story. Each zone has its own TTL, leftover product, and invoice. Client A can cancel on Tuesday. Client B still has a 86400 TTL until Wednesday night. A spreadsheet column for close date beats a Slack mood.
Filename exports with the zone and the date. Do not drop ten client PSTs into one folder named “old mail.” Offboard is the inverse: when a client leaves MailerZ, their new exclusive owner should exist before you drop MailerZ MX—or they accept bounce. Leaving both published is leftover MX with your hostname in it.
Quote Agency at $39 or $390 when the fleet needs more domains. Confirm pricing. The plan does not buy dual MX. It buys capacity for maps you still close on a clock.
Tell client staff the old webmail is drain-only. If their bookkeeper keeps using it for new vendors, you have leftover MX or a communications failure. Fix the listing first. Then fix the habit.
If a second operator needs the order without a call, send this page plus the parallel-providers guide. Config first. Exclusive cut. Drain without MX. Close on the TTL. That order prevents a bake-off disguised as retention.
Paid plans do not change the physics. Solo, Starter, Business, and Agency still need one inbound owner. The upgrade changes send-as and limits. It does not make two MX products share an archive.
IPv6 versus IPv4 on the new MX hostname is reachability after the names are exclusive. Do not keep the old provider’s MX because AAAA failed. Fix the host. History will show whether the new hop accepted the envelope.
The artifacts that close keep old email provider after migration are a TTL number, an exclusive resolver listing, a drain log, an export if required, and a cancel receipt. Everything else is comfort language. Comfort language is how leftover MX survives a quarter.
Who may still open the old inbox
Bookkeepers bookmark the old webmail. Founders keep a phone mail app pointed at the old host. A contractor still has an IMAP profile. None of those people are a reason to leave MX published. They are a reason to announce the drain window and the close date in writing.
If someone must read stragglers, give them a dated login and a rule: move the message into the destination Gmail the same day. Do not reply from the old host if the public From should be the domain. Replies from the old product often send as the old hostname identity and confuse the customer you just migrated.
Shared passwords are the usual leak during drain. If three people knew the old mailbox password, rotate it the day you cut, then rotate again when you cancel. Two-factor stays on. A drain store with a Slack password is a drain store anyone can read.
Customer-facing staff should not tell senders “try the old address at Google.” There is no old public path after exclusive cut except cache. Teaching customers to discover which MX their ISP remembered is how one invoice becomes a week of tickets.
If a VIP sender is known to cache aggressively—an office firewall, a university, a bank—watch the old store for that logo specifically during the extra day. Still do not republish MX for that VIP. If they remain after the clock, call them and ask them to retry. Their resolver will miss and fetch the new exclusive set.
Personal Gmail destinations do not need the old Workspace seat. The seat was a store or a collaboration suite. After exclusive MailerZ MX, Gmail as destination is enough for inbound. Keeping Workspace MX “because we still use Docs” is leftover MX. Docs do not require your domain’s MX.
Rollback without extending leftover MX
If the new hop is wrong, restore the dated exclusive old screenshot and delete MailerZ names the same hour. That is rollback. It is not “add both until we decide.” Adding both is the incident with a new label.
After rollback, the drain clock applies to MailerZ, not to the old host. Keep MailerZ history readable for TTL plus a day in case some senders already cached the new set. Then cancel MailerZ if you are truly leaving, or fix the map and cut again in a new window.
Do not treat a failed foreign probe as a reason to keep both MX “overnight.” Overnight dual publish is how Tuesday’s bank lands on the old host while Wednesday’s probe hits MailerZ and you close the ticket as green.
Theater rollback is common: you restore MX on Cloudflare while NS still points at the registrar. Query two resolvers after rollback the same way you query after cut. The screenshot is useless if you paste it into the wrong panel.
Send-as rollback is separate. If outbound 550 5.7.1 appears, do not restore old MX. Check paid plan and dashboard credentials. Free has no send-as. Mixing inbound leftover MX with outbound authorization is how both jobs stay open.
Night cuts need a morning re-query. Registrar products republish. Parking MX returns. Cloudflare Routing can write hosts again if you did not disable the product. Keep old email provider after migration setup includes that morning check even when the drain clock is only an hour.
If you need another operator to run this without a call, send this page, the parallel-providers article, and leftover MX language on troubleshooting. Config. Exclusive cut. Drain without MX. Close on TTL. Rollback is one exclusive screenshot, never both names.
Weekend cuts hide republish until Monday. If you cut Friday night, the morning re-query is Saturday and again Monday after the first website save. Keep old email provider after migration best practice is those two checks, not a Monday mood that the old seat “might as well ride the month.”
CATCH-ALL FORWARD during drain trains the destination with guesses while you are still deciding whether leftovers returned. HOLD unknown. Named aliases only for strings you printed. A noisy old store after exclusive cut is leftover MX. A noisy MailerZ HOLD is a different ticket: guessed local-parts, not two exchangers.
Do not keep the old provider because you have not written SPF yet. SPF, DKIM, and DMARC are send jobs. Inbound exclusive MX does not wait on a perfect TXT. Mixing authentication homework with leftover MX is how the drain clock never starts.
If the old product is also your destination—Gmail Workspace as both MX and inbox—cut MX to MailerZ and keep Gmail as the destination only. That is keep-the-inbox, not keep-the-provider-as-exchanger. The Workspace invoice then pays Docs and the mailbox you already use, not a second public hop. Quote Workspace live if someone still wants seats. Do not invent a reason MailerZ needs those seats to receive.
FAQ
What is the safest way to handle keep old email provider after migration?
Keep the old mailbox login through the old MX TTL plus a day so you can drain cached arrivals. Delete the old MX the hour you publish the new exclusive set. Export the archive if counsel needs it, then cancel the seat. A live leftover MX is not a retention policy.
Does this require a new mailbox?
No. Gmail or Outlook can stay the destination on the new hop. The old provider you keep briefly is a drain store, not a second public identity. MailerZ is not IMAP. Buy hosting only if you need folders on the domain instead of Gmail.
Will it work with Gmail or Outlook?
Inbound reaches those destinations for senders who hit the exclusive new MX. Self-send can hide leftover old MX. If the old Google or Microsoft row is still published, some customers never leave that store. Free has no send-as.
What DNS records are involved?
One exclusive MX set on the printed name after cut. NS that names the live panel. Verification TXT on the new hop. SPF, DKIM, and DMARC when you send. The old MX hostname must be absent at every priority. See RFC 5321 and RFC 1035.
What should I test before production?
Read the old MX TTL before the window. After cut, two resolvers, a foreign probe, history 250, then watch the old store for stragglers only. Close when the clock plus a quiet day is done. Do not keep old MX to test.
Key takeaways
- Keep old email provider after migration as a drain store, not as a live MX.
- The clock is old MX TTL plus a day, not a quarter of leftover billing.
- Archives are exports. They do not require public exchangers.
- New mail in the old store after the clock means leftover MX or republish.
- Foreign probe after exclusive cut. Self-send is not the gate.
- Re-query after registrar or website saves. Products republish.
- Free receives. Solo $40/yr starts send-as. Confirm /pricing.
- Envelope SRS only. Not IMAP, not an inbox SLA, not SOC 2.
Conclusion and next action
If you want to keep the old provider after cutover, keep the login and delete the MX. Read TTL. Drain. Export if counsel needs a file. Cancel the seat. MailerZ can show hops it accepted. It cannot merge a leftover host you left published for comfort. Start free on one domain and write the close date before the window.
Ready to cut with a close date
Start free with one domain and a drain window you can actually end.
Inbound on Free. Solo when send-as is the job. Sign in if the domain is already there.
Review quarterly, or sooner if registrar email products republish MX after a website save. Author: MailerZ editorial, Secuno LLC.