Guides
Moving from Notion to a CRM: what blocks you, what stays, how to leave
A Notion database holds 250,000 rows, so size rarely pushes anyone out. What blocks a salesperson is everything the database does not receive on its own, starting with the exchanges with the customer. Keep Notion for your documents, and move your prospect and deal databases into Kasar, which imports them with no file and keeps their types.
Facts checked on November 7, 2026
01What a Notion database can hold
According to Notion's help center, checked on November 7, 2026, a database holds up to 250,000 rows and 500 properties, and each database page weighs at most 2.5 MB. The same page explains how to lighten a slow database, which shows where the friction sits day to day: display, long before the ceiling. For a team tracking a few thousand companies, volume decides nothing.
That is also why people build their first CRM there. Notion publishes a gallery of CRM templates, a database comes together fast, and it sits next to the company wiki. The problem shows up later, when the database has to follow a living relationship: you then have to type every exchange into it, or build an agent to do so.
02Where a CRM built on Notion stops
Emails on the record
- In Notion, as of November 7, 2026
- On Business and Enterprise, a Custom Agent tied to Gmail or Outlook creates or updates a row, following the instructions you write for it
- In Kasar
- Connect Gmail or Outlook: exchanges with your contacts land on their records
LinkedIn and WhatsApp
- In Notion, as of November 7, 2026
- We found no native capture into a database on its Custom Agents, automations and pricing pages
- In Kasar
- LinkedIn through the Chrome extension, WhatsApp by QR code, in the inbox
Sending an email
- In Notion, as of November 7, 2026
- The “Send mail to” action goes out from a Gmail account, on a paid plan
- In Kasar
- Reply from your Gmail or Outlook address; sequences that stop at the reply from Pro up
Automating
- In Notion, as of November 7, 2026
- Paid plans; the Free plan opens a single type of automation
- In Kasar
- 3 active automations on Free, 20 on Pro, no limit on Max
Limiting access by row
- In Notion, as of November 7, 2026
- Business plan: row rules based on a Person property or “Created by”. Automations do not act on restricted pages
- In Kasar
- Row-level access control on Max
The first point weighs the most. A database that does not receive exchanges goes stale in the first busy week, and follow-ups get forgotten. A Custom Agent closes part of the gap, once you write its instructions and set its permissions; in Kasar, connecting the mailbox is enough. Database automations do not make up for it: their triggers are a page added, a property edited or a recurring schedule, and none of them sees what happens outside Notion.
03What to leave in Notion
Leaving Notion as a CRM does not mean closing your wiki. Your procedures, scoping notes and product documentation belong there, and no CRM replaces them. Only the data describing a sales relationship should move: prospects, contacts, companies, deals, and the databases that extend them, such as a partner or candidate tracker.
The line gets drawn column by column. Whatever serves to filter, sort or follow up becomes a field, so a property to import. Whatever reads as prose stays in the page body, which the import does not carry over. If a page note has to follow the record, copy it into a text property first. Using unusual types? Add a text property for any Place too: that type comes through the import empty.
04The move, step by step
- 1
List your sales databases
Prospects, companies, deals, partners. For each, decide what it becomes: contacts, companies, opportunities, or an object of its own.
- 2
Share them with Kasar
From the import screen or the Notion integration, click Connect Notion and pick the databases. Share the ones they link to as well: a relation to an unseen database stays empty.
- 3
Import in the right order
Companies first, contacts next, deals last. The mapping comes from the database schema: a select keeps its options, a date stays a date.
- 4
Read the review screen
It names any limit hit before you start. The report then counts the records created, to compare with each database’s row count.
- 5
Rebuild your automations
They do not transfer. Rebuild them in Kasar from the need: a deal changes stage, a task gets created, the owner is told.
- 6
Set the cutover date
The import is one-off: running it again rereads the database, nothing syncs afterwards. Make the Notion database read only on the day the team switches.
The full table, property by property, is in the guide to export a Notion database to a CRM. If part of your data sleeps in a spreadsheet, moving from Excel follows the same cutover logic, through files.
Before leaving the Notion database
- Linked databases are shared with Kasar.
- Useful notes are copied into a text property.
- Your documents and wiki stay in Notion.
- The import report matches the row count.
- Still typing into Notion after the cutover date.
Frequently asked questions
A well-designed database tracks a few dozen prospects, and Notion publishes templates for it. The limit comes with the team and the volume of exchanges: email takes a Custom Agent set up on a Business plan, and we found no native capture of LinkedIn or WhatsApp as of November 7, 2026.
According to its help center as of November 7, 2026: 250,000 rows and 500 properties per database, and 2.5 MB per database page. Kasar’s direct import reads 10,000 rows per database; beyond that, split the database into several CSV files through filtered views.
No. Keep your documents, procedures and wiki there. Only the databases describing sales relationships move to the CRM. Notion stays your documentation space, Kasar becomes the home of the customer relationship.
Yes. Kasar reads the database through the Notion API once you have shared it, and keeps the type of each property. A CSV is still useful beyond 10,000 rows, or to archive the state of the database on the day you leave.
No, they get rebuilt, which is often a chance to simplify them. In Kasar, an automation starts from a trigger, such as a pipeline stage change, goes through conditions and ends in actions: create a task, notify a user, call a webhook.
Sources
Every fact on this page can be checked on the official page below, read on the date shown.
- Notion, optimize database load times and performance · read on November 7, 2026
- Notion, database automations · read on November 7, 2026
- Notion, pricing · read on November 7, 2026
- Notion, CRM templates · read on November 7, 2026
- Notion, connect mail to Custom Agents · read on November 7, 2026
- Notion, Custom Agents · read on November 7, 2026
- Notion, assign custom database permissions · read on November 7, 2026
- Notion API, page properties · read on November 7, 2026
- Notion, export your content · read on November 7, 2026