A database that mirrors a real system, live
We keep a Notion database as a live, two-way mirror of records that actually live in a CRM or ops system, instead of a static copy someone updates manually.
A Notion database is a structured collection of entries inside a page, each with its own set of properties (text, dates, status, people, and more), viewable as a table, board, calendar, gallery, or timeline. Databases can relate to each other too, so a project entry can link to its tasks or its client, all within Notion.
Each database defines its own properties, columns with a type, and every entry is a page that can carry a full sub-page of content underneath those properties.
The same database can be viewed as a table for detail, a board grouped by status, a calendar by date, or a gallery for visual browsing, all showing the same underlying data differently.
Relations let one database reference entries in another, and rollups can pull a value (a count, a sum) from the related entries back into the first database, which is how Notion gets close to relational structure without being a full database engine.
A relation only ever connects Notion to Notion. A sales pipeline database can relate cleanly to a client-notes database sitting right next to it, but it has no built-in way to relate to the deal that actually closed in your CRM, or the invoice that got paid in your accounting system.
Anything outside Notion has to be brought in manually, or kept in sync through the API, before a relation or rollup can use it at all.
We keep a Notion database as a live, two-way mirror of records that actually live in a CRM or ops system, instead of a static copy someone updates manually.
When a relation-style lookup needs data that lives outside Notion, a client's account balance, say, we build that connection so the database shows it without someone checking a separate tool.
Tell us what it is, and we'll connect it.
Show us the database that needs to reflect something happening in another system, and we'll build that connection. Databases are the structural core of Notion, and they're still just one part of how your business actually runs; the rest deserves the same attention.
Let's talk →A Notion database is a structured collection of entries with defined properties, viewable as a table, board, calendar, gallery, or timeline, all pulling from the same underlying data.
A regular page is a single document. A database is a collection where each entry is itself a page, with shared properties you can filter, sort, and view in different layouts across the whole collection.
Yes, using a relation property. One database's entries can reference entries in another, and a rollup property can then pull a value from those related entries back into the first database.
Not natively through a relation property, which only links Notion to Notion. Connecting a database to an external system's data requires syncing through the Notion API.