Project or work management platform
Not a CRM - fails on core objects, pipeline stages, status, resolution, value, scope of work, expected close date, actual close date, opportunity owner, linked buyer, email sync, schedulable activity types, opportunity reporting
Core objects
Not at all
Notion's database property reference lists only generic types (text, number, select, status, date, relation, rollup, person, etc.) with no shipped Opportunity, Person, Organization or Activity object types. All entity structure, including any CRM template, is buyer- or template-configured on top of generic databases.
Source: https://www.notion.com/help/database-properties, https://www.notion.com/help/relations-and-rollups
Verification: Verified
Pipeline stages
Not at all
No native pipeline or deal-stage object ships. The closest native property, Status, has fixed To-do/In Progress/Complete groups a buyer customizes inside a database they build themselves; it is not tied to any shipped opportunity record.
Source: https://www.notion.com/help/database-properties
Verification: Verified
Status
Not at all
No native opportunity object exists to carry an open/closed value. The generic Status property is a buyer-added field on a buyer-built database, not a shipped field on a shipped record type.
Source: https://www.notion.com/help/database-properties
Verification: Verified
Resolution
Not at all
No shipped won/lost field exists anywhere in the property reference. A buyer would add a Select property for this on a database they design themselves.
Source: https://www.notion.com/help/database-properties
Verification: Verified
Value
Not at all
No shipped 'deal value' or money field exists on any native object. Number properties can be formatted as currency, but only once a buyer adds one to a database they built.
Source: https://www.notion.com/help/database-properties
Verification: Verified
Scope of work
Not at all
No native line-items or product-catalog feature or description field ships on any object, since no opportunity object ships at all. Any representation of what's being sold is buyer-built from generic properties or relations.
Source: https://www.notion.com/help/database-properties
Verification: Verified
Expected close date
Not at all
Date is a generic property type with no dedicated 'expected close date' field shipped on any native object; a buyer adds and names a Date property themselves.
Source: https://www.notion.com/help/database-properties
Verification: Verified
Actual close date
Not at all
Same generic Date property applies; no native 'actual close date' field ships on any shipped object.
Source: https://www.notion.com/help/database-properties
Verification: Verified
Opportunity owner
Not at all
Person is a generic property for tagging workspace members on any database; no native 'owner' field ships distinct from Created by, because no opportunity object exists to carry it.
Source: https://www.notion.com/help/database-properties
Verification: Verified
Linked buyer
Not at all
Relation is a generic, buyer-configured connection between any two databases the buyer creates; no shipped link from a native opportunity to a native person record exists because neither object ships.
Source: https://www.notion.com/help/relations-and-rollups
Verification: Verified
Record preservation
In full
Notion only removes pages via explicit user deletion (to Trash, then permanent delete); nothing is auto-archived. Rollups and counts aggregate over all related pages by default, so records a buyer marks closed remain and continue to feed any view or rollup the buyer built.
Source: https://www.notion.com/help/duplicate-delete-and-restore-content, https://www.notion.com/help/relations-and-rollups
Verification: Verified
Structured lost reasons
In part
No shipped lost-reason field exists, but a buyer-added Select property is countable: board view groups by select value and shows per-group counts, and table views support Count aggregations per group.
Source: https://www.notion.com/help/database-properties
Verification: Verified
Email sync
Not at all
Notion Mail syncs two-way with Gmail only and lets users send mail, but its own documentation never ties it to Notion databases or pages, and it is being shut down 22 Sep 2026. The separate Gmail AI connector is read-only search access, not sync, and also has no database linkage.
Source: https://www.notion.com/help/get-started-with-notion-mail, https://www.notion.com/help/notion-mail-inbox-is-going-away-what-to-do-next, https://www.notion.com/help/notion-ai-connector-for-gmail
Verification: Verified
Calendar sync
In part
Notion Calendar can show a database's date-bearing items and dragging one to a new time writes the change back to the source database - documented two-way behavior. Syncing those same database items out to a connected Google/iCloud calendar is explicitly not supported; two-way behavior for natively-created Notion Calendar events against Google/Outlook/iCloud isn't stated either way.
Source: https://www.notion.com/help/use-notion-calendar-with-notion, https://www.notion.com/help/manage-your-calendars-and-events
Verification: Verified
Schedulable activity types
Not at all
No native Activity/Task object or activity-type field ships. A buyer builds a Tasks database with a Date property (schedulable, supports reminders) and a Select property for type themselves; neither is a shipped CRM feature.
Source: https://www.notion.com/help/database-properties
Verification: Verified
Opportunity reporting
Not at all
No native stage-to-stage conversion rate, win rate, or revenue forecast report ships. Notion's only native aggregations are generic Sum/Average/Count/Percent rollups a buyer configures on databases they built.
Source: https://www.notion.com/help/relations-and-rollups, https://www.notion.com/help/database-properties
Verification: Verified