Kasar
KasarNotion

Notion and Kasar: your database in the CRM, with no file

You share a Notion database with Kasar, and its rows become records, with the type of each property and the option list of each select. No CSV to produce, no column to retype: the mapping is read from the database schema.

01

The schema decides, not a flattened file

A CSV export reduces a select, a date or a checkbox to text, and you then have to tell the destination tool what each column is. Kasar reads the database directly through the Notion API: the property type chooses the proposed field, and the options of a select come along with it. This mapping skips AI altogether, since everything is already written in the schema.

02

A database can become an object

Your prospect database joins Contacts or Companies. A database describing something else, partners, properties, candidates, can also become an object of its own: Kasar offers to create it with its fields, an admin-only action. The object then gets its views, its automations and, if needed, its pipeline, just like the ones that ship with the CRM.

03

You start when you are ready

The import runs on demand, in the background. The review screen shows the preview, the duplicates and any limits hit before anything gets written. Running the import again rereads the database: that is how you refresh a column, and on an object with an identity rule (Contacts and Companies by default, to configure on a custom object), the “Update” strategy avoids duplicates on the second pass.

When it helps

The first CRM built in Notion

The team started with a prospect database and a deal database. They move into Kasar with nothing to retype, and exchanges by email, LinkedIn and WhatsApp finally reach the records. The wiki and procedures stay in Notion. The guide on moving from Notion draws the line between the two.

A partner tracker to bring over

A database lists your integrators with their status, region and owner. It becomes a Partners object, its option list intact. The owner, a person in Notion, attaches to a member of your workspace on a field such as the owner.

Two databases linked together

Your contacts point to your companies through a Notion relation. Kasar replaces each relation with the titles of the linked pages, as long as the target database is shared with it. Import companies first. When mapping contacts, set the column to Relation: the title finds the company record.

Setting it up, step by step

  1. 1

    Open the import from an object page, then at the upload step pick the “Notion” source, next to “File”.

  2. 2

    Click “Connect Notion”. In the Notion window, choose the pages and databases you share with Kasar, including the ones your relations point to.

  3. 3

    The “Notion databases” list appears. If one is missing, share it from Notion and refresh the list.

  4. 4

    Select the database. Kasar fetches the rows and proposes the mapping; an admin can accept the creation of an object matching the database.

  5. 5

    Read the review screen, choose the duplicate strategy, then start. The report details what was created, updated or skipped.

What Kasar captures, and where it goes

  • Title, text, number, checkbox, date, email, phone and URL, each into a field of the matching type.

  • Selects, statuses and multi-selects, with the name of each option.

  • Percentages, converted: a value Notion stores as 0.42 becomes 42.

  • Formulas and rollups, as their computed value, never the formula.

  • Relations, replaced by the titles of linked pages, up to 25 items per relation, a limit of the Notion API.

  • People, by name, and files, by address. The address of a file hosted by Notion expires after one hour.

Automations that go with it

Record created

What the workflow does
On the object brought over from Notion, “Distribute / assign” each new record created in Kasar, then “Create a task” for first contact in the owner’s name.

Field changed

What the workflow does
When a partner’s status moves to “Active”, “Add to a list” to enroll them in a welcome sequence.

Pipeline stage changed

What the workflow does
“Create a task” for the next stage, and “Notify a user” if the deal reaches negotiation.

Triggers and blocks carry their exact names from the Kasar automation editor.

Frequently asked questions

No. Import, from a file or from Notion, is open on every plan, Free included. Creating an object from a database takes an admin role, and the number of custom objects depends on the plan.

Kasar reads 10,000 rows per database. Beyond that, split the database through filtered views, export them to CSV and drop those files into the import, up to 10 files and 150 MB per file.

Only properties become fields. Text written inside a page stays in Notion: copy into a text property whatever should follow the record, before you start.

The import is one-off. A row changed later in Notion does not change the record until you run the import again. Set a cutover date, and make Kasar where the team does its typing.

If the database has several data sources, Kasar reads the first and says so on the review screen. A Place property comes through the import empty: copy the address into a text property before the import.

Sources

Connect your tools, keep your habits

Connect your mailbox and calendar in two minutes, the history flows in on its own.

Start for free