The Notion Coach
The Notion CoachWorkflow Optimizer
Back to Articles

Notion Mail Shutdown: What to Save Before September 22

Blue isometric illustration of envelopes moving from an inbox tray to an archive box, with a clock for scheduled messages.

Updated September 11, 2026

Notion Mail shuts down on September 22, 2026. September 21 is the last day to save its remaining data. Your sent and received email history stays in Gmail, but drafts, scheduled emails, snippets, and auto-label instructions need attention before the deadline. Notion’s shutdown checklist is the source to follow.

Start by checking the work you have not finished. A saved inbox history will not help if next week’s follow-up was still sitting in a Notion Mail draft.

Use the checklist below as your migration review. Work through each connected account, then confirm the saved result in its destination.

What needs to move?

Notion identifies four categories to save: migrate drafts and scheduled emails to Gmail, export snippet text, and save auto-label instructions. Snippet attachments require a separate manual download from Notion Mail → Settings → Snippets. See what to save.

Create one migration note with a row for each account. Record the person responsible, the categories checked, where the saved material lives, and the date it was verified. This can be a simple page; you do not need to build a new system to complete the move.

1. Check drafts and scheduled messages first

For each draft you want to keep, verify the recipient, subject, body, and attachments after migration. Open it in Gmail. Do not count the migration as complete because the source app reported success.

Scheduled messages deserve their own check. Compare the intended recipient, date, time, and time zone with the destination. If you recreate a scheduled message manually, check the original before leaving a second copy queued.

A useful review question is: “If I could not open Notion Mail tomorrow, would I know which messages still need to go out?” Resolve any uncertain answer while you can still compare both apps.

2. Save snippets with their attachments

Put reusable replies somewhere the team can find them. Keep each snippet’s name and text together, then open every downloaded attachment to confirm it is usable.

For example, a proposal follow-up snippet might contain a review link and a document attachment. Saving the sentence while losing the attachment leaves you with an incomplete reply. Check the whole message pattern, including links and any material it assumes is attached.

Do a quick cleanup while reviewing: mark outdated snippets instead of importing them into your next tool as if they were current.

3. Preserve the meaning of auto-label instructions

Save the instructions before redesigning the automation. Beside each one, write a plain sentence describing its purpose, such as separating vendor invoices from general correspondence.

Include an example of a message that should receive the label and one that should not. Those examples give you a small test when rebuilding the rule elsewhere.

Treat a replacement rule as unverified until you test it. Similar wording across two systems does not prove that both systems classify messages the same way.

4. Review reminders and views

Custom inbox views, sorting, and email reminders do not transfer to Gmail. Existing synced email databases in Notion retain previously synced messages, but stop receiving new messages after September 22. Notion explains the limits here.

Write down the views you actually use and the action each one supports. A view for “waiting on a reply” is useful because it prompts follow-up. Rebuild that action in your next setup rather than trying to reproduce every visual detail.

If a shared dashboard includes a synced mail view, tell the person who relies on it that it will stop updating. A page that still opens can look current even when new messages are no longer arriving.

What continues after the shutdown?

The Gmail AI Connector, existing mail blocks, and agent email tools connected through Gmail continue independently of the Notion Mail inbox. Notion’s continuity details distinguish those features from the retiring app.

Keep your review specific to the connection each workflow uses. List the inbox app, saved email view, and agent connection separately so your team knows what needs a replacement.

Final verification before September 21

  • Open the migrated drafts and scheduled messages in Gmail.
  • Open the saved snippets and their downloaded files.
  • Confirm the auto-label instructions have a clear storage location.
  • Recreate the reminders you still need.
  • Tell anyone using a synced mail dashboard that new messages will stop appearing.

Finish this review before September 21. Keep the migration note until you have used the replacement setup successfully.