What Happens to Your Email When the Subscription Expires

The phrase "what happens to your email when your subscription expires" has two entirely different answers, and which applies decides how much mail you can lose. If your subscription is a hosted mailbox — Fastmail, Zoho, Proton, Microsoft 365, iCloud+, most legacy paid providers — the address is the paid feature, and lapsing puts your mail through a staged sequence ending in permanent deletion. If your subscription is an overlay — most AI email clients, Superhuman, Shortwave, a browser extension — the mail lives on Gmail, Microsoft 365 or an IMAP host underneath, and lapsing removes the tool but not the mailbox.

This guide is the honest map of both: the shutdown phases, roughly how long each vendor gives you, what to do inside the grace window, and how to reactivate or export before it closes. Every window here can change on the vendor's schedule — check their live help page before relying on a specific number.

What actually moves — and what doesn't#

The mental model that catches people out treats "a subscription" as one atomic thing that either exists or doesn't. Real expiration works on two axes: whether the mail lives with the vendor you pay, and how that vendor stages the shutdown after you stop. Both matter.

If mail lives with the vendor, expiry starts a staged clock ending in permanent deletion. If it lives elsewhere — a Google or Microsoft account a tool merely connects to over IMAP or OAuth — expiry closes the tool but the mail keeps arriving at the account it was already arriving at. The table below is the row-by-row split, so you can locate your situation before touching anything.

The row that catches people out is the address itself. In a hosted-mailbox subscription the address only functions while the vendor delivers to it — the moment send/receive is disabled, external senders get bounces even though the mailbox is still restorable behind the scenes. In an overlay subscription the address never depended on the tool; it belonged to Gmail, Outlook or IMAP, and it keeps working when the tool goes away.

The staged shutdown most hosted providers use#

Almost every hosted email service runs the same three-step wind-down after a lapse; what differs is which action happens on which day. Vendors name the phases differently — Microsoft says Expired, Disabled and Deprovisioned; Fastmail describes an expired state, then a grace period, then deletion; Google Workspace calls it suspended — but the shape is consistent enough to plan against.

The three phases in order#

Phase one — send/receive disabled. Outbound mail is refused; inbound bounces or defers at the vendor's mail servers. Login usually still works, so you can read history and export. Microsoft 365 calls this Expired (users still have full access); Fastmail calls it expired, before the deep grace period ends.

Phase two — login disabled. Regular sign-in stops accepting credentials; only the billing owner or admin can pay to reactivate, through a specific admin path. Microsoft 365 calls this Disabled (admin-only). On most consumer providers this is the second half of the grace period — reactivation still works, but self-service password reset generally does not.

Phase three — deletion. The mailbox, address, contacts, calendars and every setting are removed. Not reversible. Vendors publish the day — roughly 30 days at most consumer providers, up to 90 at Microsoft 365 Business, something in between elsewhere — but the numbers change. Check the vendor's live help page rather than any third-party table, including this one.

Pre-expiry checklist#

Whether you plan to reactivate, migrate, or accept the loss, the same seven-item checklist applies inside the grace window. Every item has, in real lapses, turned into lost mail when skipped.

• Confirm which phase your account is in — sign in through the normal interface and note whether send, receive and admin actions each still work, because the phases are not always announced.
• Read your specific provider's published grace-period docs. Windows vary by plan, region and payment method; a Business plan's numbers are not a Personal plan's, and last year's are not necessarily this year's.
• Note the deletion date if the vendor publishes it on your account page, and add a calendar reminder for 24 hours before it.
• Export mail — MBOX or EML for most providers, PST for Microsoft 365 — while login still works. Use whichever tool the vendor supports, and verify the file opens in a second, unrelated client before treating it as a backup.
• Export contacts (vCard or CSV) and calendars (ICS). These are usually deleted with the account, not separately.
• Note filters, rules, aliases, forwarding and signatures. They are almost never included in the mail export and have to be re-created by hand at the new host.
• Decide before the deadline whether you are reactivating, migrating or accepting the loss. Deletion is permanent and cannot be deferred past the last phase.

The steps: reactivate, export or migrate before the window closes#

Run this sequence in order. Every step assumes the previous one succeeded and was verified, not just clicked. If the account is already in phase two, skip step one — login is what phase two disables.

1. 1

   Sign in and confirm which phase you are actually in

   Try the normal user URL first. If that fails, try the admin or billing-owner URL. If both fail, use the vendor's account-recovery flow. The result tells you which phase you are in, which decides which actions are still available.

2. 2

   Read the account status page for a real deletion date

   Most hosted providers show a specific deletion date on the billing page once cancellation is confirmed. That date, not the vendor's marketing copy about grace periods, is your real deadline.

3. 3

   Reactivate now if you want to keep the account

   In phase one a single card payment usually restores everything with no data loss. In phase two only the billing owner can reactivate — self-service is typically disabled — and it is worth calling support if the admin path also refuses.

4. 4

   Export mail, contacts and calendar in the same session

   Do all three at once while login is working. Logging out during a lapsed state has been known to trigger a session revalidation that locks users out earlier than the published window. One session, one export, verified in a second client.

5. 5

   If you are migrating, provision the destination first

   Create the new mail host, verify test send and receive on a subdomain or the vendor's temporary hostname, and only then move mail into it. Do not touch the MX record until both sides are proven.

6. 6

   Point MX at the new host after export is verified

   If the domain is yours (not a shared-domain consumer plan), drop the MX TTL to 300 seconds 24 hours before the change, then cut MX, SPF, DKIM and DMARC together. External senders pick up the new destination within minutes rather than hours.

7. 7

   Do not leave the last step to the last day

   Treat the published deletion date as the outside bound. Complete every export and cutover at least a full week before it, so one failed step is not fatal.

What breaks and when — the phase-by-phase table#

Naming the specific things that break in each phase is how you avoid them. Nearly every "my subscription expired and I lost mail" incident traces to one of these six moments.

Rollback plan if the lapse was accidental#

Phase one is designed to be reversible — that is the point of the grace window. Rollback becomes irreversible only after phase three. Run these steps in order.

1. 1

   Reactivate through the billing page, not through support

   Card-based reactivation usually restores send/receive within minutes and every other setting within an hour. Do this first — the fastest fix for a lockout is not being locked out any more.

2. 2

   Verify send and receive with a real outside message

   Send a message from an unrelated account (a phone Gmail, a colleague) and confirm it arrives, then reply and confirm the reply lands. Some vendors mark reactivated accounts as under review for 24 hours before restoring full send limits, so a legitimate reactivation can still bounce for a day.

3. 3

   Restore aliases, forwarding, and app passwords

   A reactivated account usually keeps mail and folder structure, but auxiliary features are sometimes reset. Re-check aliases, forwarding rules, filters and any app-specific passwords a third-party client depends on.

4. 4

   Update billing details so the same lapse cannot repeat

   Move billing to a payment method with a longer expiry, confirm the billing email is monitored, and add a calendar reminder for 30 days before the card on file expires.

Doing it without downtime#

A hosted-mailbox expiry does not have to mean any period without mail, if the switch is planned in phase one rather than phase two. Three habits make the difference.

First, start the migration inside phase one, not on the day of deletion. Phase one gives full read and export access; every hour there is cheaper than an hour in phase two, where only the admin path works.

Second, dual delivery during the observation window. Some providers accept an inbound forwarding rule while outbound is disabled; set that forward in phase one so mail arriving before the DNS change copies to the new host. On providers that disable forwarding alongside send/receive, use a temporary catch-all at the new host after MX flips.

Third, not a technical trick — plan the cutover on a quiet weekday evening or a weekend morning rather than in the panic of the last day. Any low-volume hour beats "now" when "now" is the deletion date.

Where AI Emaily fits in this picture#

A note on where AI Emaily lands in the split above. AI Emaily is an AI-native email client that connects to existing Gmail, Outlook / Microsoft Graph and IMAP mailboxes rather than hosting mail itself. If our subscription lapses, our tool goes — assistant, drafts, agent runs, audit log — but your mailbox is untouched because it never lived on our servers. That is the overlay side of the table. There is no permanent free tier; a seven-day free trial on Pro or Autopilot is on the pricing page, card required, nothing charged if you cancel before day seven. We build AI Emaily.

The honest concession: if you want zero third-party access to your mail — no OAuth grant, no assistant reading your inbox — no overlay is the right answer, ours included. Stay in the provider's native client. And if you are on a hosted-mailbox subscription that is actively lapsing, the priority is the export, not any client choice — check your provider's grace-period page first, then pick a destination.

Putting it together#

Two axes decide what happens when your email subscription expires: whether the mail lived with the vendor you paid, and which phase of the staged shutdown you are in. Overlays lose the tool, not the mailbox. Hosted mailboxes run send/receive, then login, then deletion — usually inside 30 to 90 days, but always per their own published policy rather than any generic table.

Whichever case you are in, the actions inside the grace window are the same: read the vendor's docs, export while login works, decide before the deadline. Deletion is not a soft target. Vendors do delete on schedule.