How to Import Gmail into Notion (via CSV)

Export formats

Gmail Exporter Guide

Notion is where a lot of people keep their second brain — trackers, CRMs, project hubs and knowledge bases. Email is one of the richest inputs to that system, but copying messages into Notion by hand is tedious. Exporting Gmail to CSV and importing it as a Notion database solves that in one pass. Here is how to do it cleanly and privately.

Why the CSV route works best

Notion imports CSV files directly and turns each column into a database property. That makes CSV the most reliable bridge from Gmail: no third-party connector that needs full mailbox access, no sync that silently breaks, and no data leaving your control except the file you choose to import. If CSV is new to you, start with export Gmail to CSV. If you prefer structured data for a more advanced setup, export Gmail to JSON is an option too, though Notion's own import expects CSV.

Step 1 — Export the mail you want in Notion

1. Install a local exporter. Add Gmail Exporter to Chrome. The CSV is built on your device — nothing is uploaded.
2. Search for the right subset. Decide what the Notion database is for — leads, newsletters to read, project mail — and search that first. The search-then-export flow keeps the import tight.
3. Export to CSV. You get one row per message with columns for sender, subject and date, ready for Notion.

Step 2 — Import the CSV as a Notion database

1. In Notion, open the page where you want the database and choose Import → CSV (or drag the file in).
2. Notion creates a new database with a property for each column. Confirm the header row mapped correctly.
3. Set property types: turn the date column into a Date property and the sender into Email or Text. Proper types make sorting, filtering and calendar views work.
4. Add your own properties — Status, Tags, Follow-up — and each email becomes a workable record.

What to build in Notion

• An email tracker. Follow-ups, waiting-on and done, all filterable in one board view.
• A lightweight CRM. Each sender is a contact; link records to companies and log interactions. Pair with build an email list from Gmail.
• A knowledge base. Import reference threads and receipts so they are searchable inside your Notion workspace instead of buried in Gmail.
• A reading queue. Import newsletters and triage them with a status property.

Keep it current

This is an import, not a live sync, so you refresh it by exporting new mail and importing again. Export just the messages since last time using a date operator, and either create a new database or merge the rows into the existing one. The date-range export makes these top-ups quick. For a fuller picture of what is worth importing, a quick inbox analysis helps you decide which senders and topics deserve a database of their own.

Tidy the file first

A clean CSV imports into a clean database. Before importing, remove duplicate and empty rows and check the header — the same light hygiene from removing duplicate contacts. It saves you editing records inside Notion afterwards.

Keep it private

Connectors that pipe Gmail into Notion automatically want ongoing access to your mailbox and move your messages through their servers. The CSV route keeps everything local: you export the file on your own machine and import only what you choose. If keeping your mail private is part of why you use Notion for yourself, that matters — see is it safe to export your Gmail?

The bottom line

Getting Gmail into Notion is a two-step, no-connector job: export the right mail to CSV locally, then import it as a database and add your own properties. You get a tracker, CRM or knowledge base built from your real correspondence, kept current with occasional exports, and private the entire way through.

Set property types for a database that works

Notion turns each CSV column into a database property, but it defaults most of them to plain text. Spend a minute upgrading the important ones and the database comes alive:

With proper types in place, you can flip the same data between a table, a board and a calendar, and filter it any way you like — the flexibility that makes Notion worth importing into in the first place.

Choose the right database shape

What you build depends on what the email represents. A few common shapes:

• Tracker: a board with To reply / Waiting / Done columns for messages that need action.
• CRM: a People database where each sender is a contact, linked to companies and logged interactions.
• Knowledge base: reference threads and receipts, tagged by topic and fully searchable inside your workspace.
• Reading queue: imported newsletters with a status property so you triage on your own time.

Deciding the shape before you import tells you which subset of Gmail to export and which properties to add, so the database is useful the moment the import finishes.

Connect email to the rest of your workspace

The reason to bring email into Notion rather than leaving it in Gmail is connection. A message about a project can link to that project's page; a contact can link to a company; a receipt can attach to an expense log. Once your correspondence lives as database records, it stops being a walled-off inbox and becomes part of the same web of pages as your notes, tasks and docs. That cross-linking is something no email client offers, and it is the whole payoff of the import.

Keeping the database current

This is an import, not a live feed, so you keep it fresh by exporting new mail periodically and importing the additions. Export just the messages since last time with a date operator, and either append them or merge into the existing database. A short monthly refresh keeps the workspace current while ensuring you never grant a connector standing access to read your entire mailbox.

Private by design

Third-party tools that sync Gmail into Notion automatically require ongoing mailbox access and pass your messages through their servers. The CSV route keeps everything in your hands: the file is built locally, you review it, and you import only what you intend to. For a system that is meant to be your private second brain, it makes sense that the data feeding it should stay private too — and exporting locally is how you guarantee that.