Notion Mail shuts down September 22: what to save by September 21

Notion has set September 21, 2026, as the general deadline for preserving Mail‑only data before the inbox closes on September 22 across web, desktop and iOS, on all plans. Unsaved Mail‑only data will be permanently deleted; email history remains in Gmail. Organizations relying on HIPAA coverage had an earlier June 30 transition date, which the general deadline does not extend. Notion’s shutdown notice separates these requirements, along with the information users need to migrate or recreate.

The announcement received TechCrunch coverage on June 25. With the deadline approaching, the useful question is how to preserve a working inbox: the unfinished reply, the proposal scheduled for next week, the reusable attachment and the view a colleague checks for new requests. Each needs a different kind of verification. A downloaded file alone cannot establish that all of those workflows will still work.

Start with the state each item needs to reach. A historical conversation needs to remain readable; an unfinished message needs to remain editable; a scheduled message needs the correct future send time. The matrix below translates Notion’s published shutdown guidance into a working inventory. Its final column provides checks to make in your own account, rather than assuming that an export has completed every part of the transition.

For a shared workflow, record an owner and a destination against each item. That helps separate work that has been preserved from work that still needs rebuilding. Include a few important conversations in the inventory so someone can compare the old workflow with its replacement without reconstructing the project from memory.

Notion documents its export control under Settings → Account → Export your data. The same settings area contains controls for connected addresses, so it is worth distinguishing the task you are performing before clicking through. Notion’s Mail settings guide says disconnecting an address deletes the associated Mail account and its views, AI labels and notification preferences. Complete preservation and verification before making account‑cleanup decisions; disconnecting is not an export step.

For files attached to snippets, the separate retrieval route is Notion Mail → Settings → Snippets. Notion directs users to download those attachments manually; the account export control should not be treated as confirmation that they have been saved. Open each important downloaded file while the original is still available, and keep it with the response that uses it. For an unfinished message, check the subject, recipients and body in the destination.

Notion’s composition documentation explains why snippets deserve that closer look: a snippet can contain an entire email, including its subject and recipients, and it can have its own shortcut. Record those elements alongside the saved content. A useful preservation record might identify a proposal response, the attachment it expects and the fields the sender must replace each time. Rebuilding a shortcut can wait; retaining enough context to use the response correctly is the immediate job.

A message intended for next Tuesday needs a delivery check as well as a content check. Make a small schedule inventory with recipient, subject, intended date and time, and time zone; compare it with Gmail’s Scheduled view after migration. Google’s scheduling documentation says sending uses the time zone selected when scheduling, supports up to 100 scheduled messages, and can occur a few minutes after the chosen time. A draft sitting in Gmail therefore needs separate attention if you expected it to send automatically.

If a scheduled message needs changing in Gmail, Google documents a sequence of canceling the send, editing the resulting draft, and scheduling it again. Check for an existing scheduled copy before creating another one. This is particularly useful when several people coordinate customer communications: the person checking the message should record whether it remains scheduled, was deliberately paused, or has already been sent. That record makes it easier to prevent a second person from reconstructing a send that is already in place.

Rules deserve a similar distinction between saved instructions and working behavior. Notion’s settings distinguish AI auto‑label descriptions from Gmail filters. Gmail can export its own filters as XML and import them through Settings → See all settings → Filters and Blocked Addresses, according to Google’s filter guide. The documented Gmail import format does not establish compatibility with an exported Notion AI instruction. For a rule that needs rebuilding, first search for the messages it should match and inspect the results. Then choose the action deliberately, especially if it archives, forwards or deletes mail.

The disappearing inbox sits alongside email features that continue. Notion’s Mail AI Connector documentation explicitly says that connector is staying. It is available across Notion plans, with matching email addresses required for the Mail account and workspace. The connector can search a connected inbox, but its documentation says it cannot read attachments. Preserving a proposal file and retaining AI access to the email that accompanied it are therefore separate checks; search results alone do not verify the file.

The separately named Gmail AI Connector requires Notion Business or Enterprise, an eligible paid Google Workspace plan, and installation by someone who is both a Google administrator and Notion workspace owner. Connecting that Google organization also changes the existing setup: Notion says the Mail connection disconnects and is replaced by the Gmail AI Connector. Identify the connection already enabled and coordinate any change with its owner. These requirements apply to that organization‑level connector; they do not mean every departing Mail user needs a paid replacement.

A team that tracks incoming work through a Notion email database needs an explicit handover. A preserved view can still look familiar while no longer showing the latest requests. Give the person who uses it a clear route to the replacement inbox or tracking process, and record the point at which the old view becomes historical. For any workflow that promises a response, assign someone to confirm that newly arriving mail reaches the place the team now monitors.

Finish with a small set of concrete results: a conversation opened in Gmail, an unfinished reply ready to continue, a future send accounted for and a reusable attachment that opens correctly. Record any unresolved item with its owner and next action while there is time to fix it. This leaves the person taking over with a usable destination and a clear account of the work still outstanding.