> ## Content Index
> Fetch the complete content index at: https://notionsolutions.net/llms.txt
> Use this file to discover other available public pages before exploring further.

# Notion Synced Databases: Routes, Plans, Limits and Traps
- URL: https://notionsolutions.net/notion-synced-databases/
- Published: 2026-11-11T09:00:00.000Z
- Updated: 2026-11-15T19:26:19.000Z
- Description: A Notion synced database is a one-way copy of another tool's records. See which route fits GitHub, Jira, Salesforce, Asana and GitLab, the plan each needs, where the old 20,000-row cap came from, and how history windows and sharing can remove pages or expose records.
- Author: Kevin Turner
- Tags: guide, databases

**A Notion synced database is a one-way copy of another tool's records: Notion keeps the source fields updated and read-only, and you can add your own properties beside them. The no-code route is a managed database sync from Settings → Connections: GitHub and Jira Cloud accept Business or the Mobile Business add-on; Salesforce requires Enterprise. Asana and GitLab moved to syncs built on Notion Workers, which you set up with Notion AI.** I'd sync only the records your team reads in Notion and keep all available history, because a shorter window removes pages along with the values you added to them.

For pull requests and issues, choose the managed GitHub sync; for Jira Cloud work items, the managed Jira sync; for Salesforce accounts, contacts and opportunities, the Salesforce sync on Enterprise. For Asana or GitLab, choose the Workers replacement that Notion AI sets up from a sync skill; for a tool Notion doesn't connect to, a custom Worker your team writes and maintains. If what you want is the same Notion database on two pages, you don't need a sync at all; that's a linked view, covered in its own section below.

The older GitHub, Jira, Asana and GitLab synced databases stopped updating on October 30, 2026\. [Notion's legacy-sync guidance](https://www.notion.com/help/synced-databases-legacy?ref=notionsolutions.net) confirms that the databases stay in Notion but no longer refresh, and nothing moves over automatically. The [Salesforce connection guide](https://www.notion.com/help/salesforce?ref=notionsolutions.net) gives the same October 30 cutoff for its legacy integration. A new managed sync creates separate databases, so keep the old ones while you transfer views, relations and Notion-only values.

## Which sync route fits your tool?

Start from the records you want to read in Notion, then check the plan. The plan and cost conditions below are the ones Notion's help pages state.

__Notion sync routes by source tool__
| What you want in Notion                                         | Route                                                              | Plan or cost condition                                      | Watch for                                                   |
| --------------------------------------------------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------- | ----------------------------------------------------------- |
| GitHub pull requests, issues or both                            | Managed database sync                                              | Business (Mobile Business also qualifies)                   | The GitHub App installation needs access to each repository |
| Jira Cloud spaces and work items                                | Managed database sync                                              | Business or Enterprise (or the mobile Business entitlement) | Jira Server and Jira Data Center aren't supported           |
| Salesforce accounts, contacts and opportunities                 | Managed database sync                                              | Enterprise                                                  | No leads, cases or custom objects                           |
| Asana projects and tasks                                        | Workers sync, set up in a Notion AI chat with the Asana sync skill | Notion credits each time the sync runs                      | Needs an Asana personal access token                        |
| GitLab projects, issues, merge requests, pipelines and releases | Workers sync with the GitLab sync skill                            | Runs as a Workers sync                                      | Written for GitLab.com; the token needs read\_api           |
| Another tool, or data you reshape before import                 | Custom Worker                                                      | Requires code and deployment                                | Your team maintains the Worker code                         |
| The same Notion database on two pages                           | Linked view                                                        | No sync involved                                            | Edits reach the original; filters stay local                |
| Edits that flow both ways                                       | A third-party sync tool                                            | Outside Notion's plans                                      | Notion's own syncs are one-way                              |

[![Diagram matching six needs to routes: GitHub or Jira to a managed sync on Business, Salesforce to Enterprise, Asana or GitLab to Workers, two pages to a linked view](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/notion-synced-databases-route-chooser.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/notion-synced-databases-route-chooser.webp?ref=notionsolutions.net)

Start from the records you need. GitHub and Jira also accept the Mobile Business add-on; Salesforce requires Enterprise.

[Notion's guide to syncing data from other tools](https://www.notion.com/help/sync-data-from-other-tools-to-notion?ref=notionsolutions.net) draws the line between its two routes. Use a managed sync when one of the supported connections already includes the data and settings you need; use a Worker when you need a custom source, more record types or calculations that combine data before import. A Worker requires code and deployment, and the split of work is plain: your team maintains the Worker code, and Notion runs it. The [developer guide to Workers syncs](https://developers.notion.com/workers/guides/syncs?ref=notionsolutions.net) shows what that code defines, from the database schema to the sync mode and schedule.

Cost is the other half of the Workers decision. [Notion's Asana replacement guide](https://www.notion.com/help/connect-asana?ref=notionsolutions.net) says Workers syncs run on Notion's usage-based pricing and use Notion credits each time they run, so syncing more often uses more credits. I'd set the schedule from how often someone reads the data, not from how often it changes.

## Want the same Notion data in two places?

A lot of searches for "synced database" are about something else: one Notion database that should appear on a client page and on your dashboard. That's a linked view. You add it with **/linked**, pick the database and choose or create a view. [Notion's linked databases guide](https://www.notion.com/help/guides/using-linked-databases?ref=notionsolutions.net) says edits in a linked database reflect in the original, while filters and views only apply to the linked instance. [Does editing a linked Notion database change the original](https://notionsolutions.net/notion-linked-database-edits-original/) walks through which changes travel and which stay local.

A synced block is a different tool again: it repeats page content, such as a set of instructions, in several places, and it doesn't copy database rows. [Notion synced block permissions](https://notionsolutions.net/notion-synced-block-permissions/) covers who can see and edit those copies.

Two separate databases that should mirror each other need an outside tool. In a [Zapier community thread on syncing two Notion databases](https://community.zapier.com/how-do-i-3/how-to-sync-updates-between-two-notion-databases-33146?ref=notionsolutions.net), a user who already copied new items across got stuck on updates; the forum's community manager pointed to the Updated Database Item trigger, a Find Database Item search on a unique identifier that exists in both databases, and the Update Database Item action. Whalesync markets [real-time two-way sync between Notion databases](https://www.whalesync.com/blog/notion-databases-two-way-sync?ref=notionsolutions.net), including across workspaces and with Airtable, Google Sheets and Webflow. For two databases in one workspace, I'd try a relation or a linked view before building a mirror, because a mirror is a second copy you have to keep matched.

## Set up a managed sync for GitHub, Jira or Salesforce

Check access before you open Settings. You need to be a member of the Notion workspace and have an account in the source tool that can read the data. GitHub also needs a GitHub App installation with access to the repositories, and your organization may require an owner to approve it. Salesforce needs an account with API access. For Jira, the connected account must be able to read the selected spaces, and a Jira administrator may need to approve the connection.

1. Open **Settings** → **Connections** in your Notion workspace.
2. Open GitHub, Jira or Salesforce from **Browse** or **Installed**, then choose **Database sync**.
3. Connect your account and finish the tool's authorization. For GitHub, that includes the app installation; use **Add organization…** to add another installation.
4. Pick the data: repositories and then pull requests, issues or both for GitHub, spaces for Jira, and **Accounts**, **Contacts** or **Opportunities** for Salesforce.
5. Choose custom properties where the tool offers them. Jira can include every custom property through **Sync all current and future custom properties**. In Salesforce, **Sync all current and future properties** is off by default, so no custom properties sync until you turn it on or select specific ones.
6. Set the history: all available history or a window of the last 30, 90 or 365 days.
7. Select **Create sync**.

Notion creates the databases in your Private sidebar section and runs the first import in the background. You can open them while records are still arriving, and you don't need to keep Notion open. A Jira sync creates two databases, Jira Spaces and Jira Work Items, and doesn't need a Jira webhook. Salesforce imports each object type separately, so one database may finish before another.

The connected account decides what Notion can read. If its permissions change or the connection expires, the sync may ask you to re-authenticate. I'd connect with an account whose access matches what the team should see in Notion, rather than an admin account that can read every repository, because everyone who can open the database sees whatever that account imported.

## What comes across from each tool

Each record from the source becomes a page in a Notion database, and each source field becomes a property. The table shows what each route creates and what it leaves behind.

__What each sync creates and leaves out__
| Tool                   | Databases created                                                                        | Key synced properties                                                                                                                                                        | Not synced                                                                                             |
| ---------------------- | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| GitHub                 | A new page in your Private section with the pull requests, issues or both you chose      | Title, PR Number, GitHub URL, Repository, State (Open, Draft, Merged or Closed), Author, Labels, Base Branch, Head Branch, Created At, Updated At, Closed At, Merged At      | Pull request comments and review details; the description arrives as plain text, not rendered Markdown |
| Jira Cloud             | Jira Spaces and Jira Work Items                                                          | Summary, Key, Jira URL, Status, Work Type, Priority, Assignee, Reporter, Labels, Space, Parent, Sub-items, Created, Updated, Due Date, plus the custom properties you choose | Comments and attachments; the Jira description goes into the page body                                 |
| Salesforce             | A separate database for each object type you select                                      | Accounts: Name, Type, Industry, Website, Phone, Annual Revenue. Opportunities: Name, Stage, Amount, Close Date, Probability                                                  | Leads, cases and custom Salesforce objects; custom properties until you select them                    |
| Asana (Workers guide)  | Projects and Tasks                                                                       | Project and task names, completion, owners and assignees, sections, dates, notes and Asana links                                                                             | Comments, attachments and arbitrary Asana custom fields; notes are capped at 2,000 characters          |
| GitLab (Workers guide) | GitLab Projects, Issues, Merge Requests, Pipelines and Releases, plus a GitLab Dashboard | States, assignees, labels, branches, pipeline status and release tags, with authors, assignees and labels stored as text                                                     | Issue comments, merge request discussions, repository files and job logs                               |

People fields deserve a check before you build a "my work" view. On the [GitHub sync page](https://www.notion.com/help/github?ref=notionsolutions.net), Author (GitHub) holds the username, and Author becomes a Notion person only when the author's public email matches a workspace member. The [Jira sync page](https://www.notion.com/help/jira?ref=notionsolutions.net) says Assignee and Reporter sync as Notion person properties matched by name, each with a read-only text companion holding the Jira display name. GitLab's Workers guide stores people as text, so a filter on a person property won't find them there.

## Make the synced data answer a question

Synced properties are read-only. To change a status or a label, open the record in the source tool and change it there. What you can do in Notion is build views, filter and sort records, and add your own properties, such as a team priority on pull requests or an account planning status on Salesforce accounts. Values in your own properties stay in Notion and aren't sent back. On a [Workers sync](https://developers.notion.com/workers/guides/syncs?ref=notionsolutions.net), you can't add or delete rows by hand either. I'd keep tasks you create in Notion in a separate database and relate them to the synced records.

Name your own properties so they can't collide with synced ones. Jira already brings a Priority property, so a field of yours called "Client priority" is safer than a second "Priority". Notion asks for distinct names so your properties don't conflict with the ones the sync manages.

Then build one view per question. For a client's code work, the question is often "Which pull requests for this client are still open?": filter Repository to the client's repository, State to Open or Draft, and sort by Updated At. [Choosing a Notion database view for the question](https://notionsolutions.net/notion-database-views-for-client-work/) covers picking the layout once the filter is right.

To tie synced records to your own work, add a relation property that points to your Projects or Clients database; Notion's GitHub page suggests your own properties for connecting pull requests and issues with your team's planning process. The setup in [Notion relations and rollups for clients and projects](https://notionsolutions.net/notion-relations-and-rollups/) applies here. Keep in mind that a relation you set by hand is one of your own values, so it goes with the page if the record later falls outside the history window. Relations the sync builds itself, such as Jira parents and sub-items, appear only when both pages are synced.

The sync decides which records exist and what their source fields say. Which client a pull request belongs to, and who in Notion gets to see it, stays your decision.

## How fast, how far back and how many rows?

Notion publishes a short list of numbers for its syncs. Each one depends on a condition, so the condition sits next to it.

__Published sync timing, history and row figures__
| Figure                        | Published value                                                    | Applies to                                | Condition                                                                                                |
| ----------------------------- | ------------------------------------------------------------------ | ----------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| Update time                   | "A few minutes or less"                                            | Managed syncs in general                  | Notion's stated expectation; timing varies by connection, data size and the source tool's request limits |
| Change check                  | Every minute                                                       | Salesforce                                | How often Notion checks, not a promise that every change appears within a minute                         |
| Run schedule                  | Hourly by default; every 5 minutes to every 7 days, or manual only | Asana Workers sync                        | More frequent runs use more credits                                                                      |
| Run schedule                  | Five hourly syncs, one per data type                               | GitLab Workers sync                       | Replace mode removes records missing from a completed refresh                                            |
| History window                | All, or the last 30, 90 or 365 days                                | GitHub, Jira, Salesforce                  | Counted from the record's last update, not its creation date                                             |
| Row limit per synced database | 100 on Free; 20,000 on Plus, Business and Enterprise               | The earlier synced databases, marked beta | Notion's pricing page in November 2024 and March 2025 snapshots; gone from the page by August 2025       |
| Managed sync row limit        | No number published                                                | Managed syncs                             | Help names a row limit and the fix, without a figure                                                     |
| Rows per database             | 250,000                                                            | Any Notion database                       | General database limit, not a sync setting                                                               |
| Property data per page        | 2.5 MB                                                             | Any database page                         | Combined property data; excludes files and media, formulas, rollups and the page body                    |

Read across the routes, the refresh figures run from a one-minute check on Salesforce to an hourly default on the Asana and GitLab Workers syncs. Three of the five tools publish a number; for GitHub and Jira, only the general few-minutes expectation applies. Those numbers measure different things, a check interval on one side and a run schedule on the other, so I wouldn't average them. The history options are the same on the three managed sync pages: all history, 30, 90 or 365 days. A recent run time in the sync settings shows activity, but Notion says it doesn't guarantee every source change has reached Notion yet.

The 20,000 figure people still search for came from Notion's pricing page. The [March 2025 snapshot of Notion's pricing page](https://web.archive.org/web/20250302215358/https://www.notion.com/pricing), like the November 2024 one, listed a row limit per synced database of 100 on Free and 20,000 on Plus, Business and Enterprise, one synced database on Free and an unlimited number on paid plans. From the August 2025 snapshot onward the row is gone, and the archived pages through August 2026 show a "1-way database syncs" row filled in only for Business and Enterprise. So 20,000 was the published cap of the earlier synced databases, not a current figure. Notion's sync help names a row limit for managed syncs without giving a number: when a sync reaches it, reduce the selected data or choose a shorter history window, and review what that removes before saving.

Two limits apply whatever the sync does. [Notion's database performance help](https://www.notion.com/help/optimize-database-load-times-and-performance?ref=notionsolutions.net) caps each database at 250,000 rows and the combined property data of one page at 2.5 MB. Files and media, formulas, rollups and the page body do not count toward that 2.5 MB cap; [the Notion database property limit guide](https://notionsolutions.net/notion-database-property-limit/) covers how the size caps work. Jira adds limits of its own on the number of spaces per sync and the number of database syncs each user and workspace can create, without publishing the numbers.

## Avoid the traps that remove pages or expose records

### A short history window deletes pages and your notes

The history window counts from a record's last update, not from when it was created or whether it's still open. An open pull request or an unresolved Jira work item that nobody touched in 90 days can leave a 90-day sync. When it does, Notion removes its page, including the values you added in your own properties. Shortening the window later removes every record outside the new one, and removing a GitHub repository or a Jira space removes its pages too. That's different from a view filter, which only changes what one view displays.

If your team adds client names, priorities or relations to synced pages, I'd keep all available history and filter the view instead. Before you shorten history or drop a repository, copy out any Notion-only values you need; Notion's GitHub page asks for that step too, since the removed pages take those values with them.

[![Diagram of a one-way sync: read-only synced properties beside your own editable ones, older records outside the history window removed, and Notion sharing deciding access](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/notion-synced-databases-one-way-flow.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/notion-synced-databases-one-way-flow.webp?ref=notionsolutions.net)

In a managed sync, source fields stay read-only. A record that leaves the history window takes your own property values with it.

### Viewers can see records the source would hide

Synced databases start as private pages, and from there Notion's sharing decides who sees the data. Source permissions aren't copied to each viewer, so a person with access to the Notion database may see records they can't open in GitHub, Jira or Salesforce. A Jira space's Visibility property describes the space; it doesn't control who sees its data in Notion. A GitLab issue's Confidential property doesn't enforce that rule in Notion either. Before a synced database feeds any page a client or guest can reach, check the routes in [Notion client portal permissions](https://notionsolutions.net/notion-client-portal-permissions/), and remember that a view filter hides rows from a view without changing who can open the database.

### Source changes don't always reach Notion

A permission change in the source tool may stop future updates without removing the data already in Notion. A deletion or permission change in Jira may not remove the Notion page right away. On the [Salesforce sync page](https://www.notion.com/help/salesforce?ref=notionsolutions.net), a record that Salesforce removes before the sync notices the deletion can stay in Notion. Workers syncs for Asana and GitLab go the other way: records missing from a completed refresh are removed, and removing a GitLab project from the configuration can remove its records, Notion-only information included. If a replace-mode Workers sync errors partway through a run, the developer guide says no deletions happen.

## Move off an old synced database

For GitHub, Jira and Salesforce, create the managed sync from **Settings** → **Connections** → **Database sync**. For Asana and GitLab, use the Workers replacement below. A new managed sync creates a page in your Private section instead of replacing the old database, so both stay in place while you move your work over.

1. Create the new sync with all available history, so nothing you're about to copy drops out.
2. Rebuild the views your team opens daily. Notion's help pages suggested a Notion AI prompt that @-mentions both databases and asks it to copy the filters from the legacy one.
3. Recreate relations to your own databases, then copy Notion-only values such as priorities or client names. Match records by their source IDs rather than by titles, which the Asana guide recommends for its replacement.
4. Point dashboards, linked views and page links at the new database, and keep the old one for reference.

Asana and GitLab moved to Workers instead of a new managed sync. Their older syncs stopped updating on October 30, 2026 and didn't migrate automatically. The replacement starts in a Notion AI chat in which you @-mention your existing synced database and include the Asana or GitLab sync skill. You'll need access to Workers and the tools Notion AI uses to deploy one, plus a token: an Asana personal access token, or a GitLab personal or project access token with read\_api and access to every selected project. Provide it through the secure credential input; both guides say not to paste the token into the chat, a Notion page or a database property.

The [GitLab replacement guide](https://www.notion.com/help/connect-gitlab?ref=notionsolutions.net) is written for GitLab.com; on a self-managed instance, tell Notion AI before setup, because the API address and credentials need adapting. Both guides create new databases, and page links, views, relations and Notion-only information don't transfer automatically. Notion said the separate Asana AI Connector, which lets Notion AI search your Asana data, wasn't part of this change. If the move makes you question whether Asana should stay at all, [Notion vs Asana for small teams](https://notionsolutions.net/notion-vs-asana/) compares the two for client work.

## Fix a sync that's missing records or stopped updating

First identify the sync. If an older GitHub, Jira, Salesforce, Asana or GitLab database stopped refreshing after October 30, 2026, [move it to the replacement sync](#move-off-a-legacy-sync); reconnecting the old route won't restore updates. For a current managed sync, open the connection's **Database sync** settings and read the status, recent run information and error details.

__Sync status labels and what to do__
| Status                      | What it means                                            | What to do                                                                          |
| --------------------------- | -------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| Initializing or Backfilling | Being set up or importing existing records               | Let the import continue                                                             |
| Healthy                     | Running normally; recent changes may still be processing | Give recent changes time to arrive                                                  |
| Degraded or Failing         | Something is delaying updates                            | Open the error details                                                              |
| Action needed               | The sync needs you                                       | Follow the instructions, such as reconnecting an account or restoring source access |
| Disabled                    | The sync is paused                                       | Unpause it in the sync's settings                                                   |
| Unavailable                 | No status information right now                          | Check again later                                                                   |

### Records are missing

Check the selected repositories, spaces or object types, the history window and the connected account's permissions in the source. Then check whether the first import is still running and whether a view filter is hiding the records. For the filter side, [tasks missing from a filtered Notion view](https://notionsolutions.net/notion-filtered-view-missing-tasks/) traces the rule that hides a record.

### Updates have stopped

Open the status details. Reconnect if the authorization has expired, or ask your source administrator to restore access. Temporary outages and request limits in the source can delay updates while Notion retries. On Jira, a workspace without Business, Enterprise or the mobile Business entitlement can still connect accounts, but cannot create or resume a sync until it has a qualifying plan.

### The sync has reached a row limit

Reduce the selected data or choose a shorter history window. Either one can remove synced pages, so copy any Notion-only values from the affected records before you save.

### Your own property clashes with a synced one

Rename your property so it doesn't share a name with a property the sync manages. Keep the source field and your field clearly apart, for example "Status" from Jira and "Client status" for your own review.

### Relations are missing

The related page may sit outside your history window or still be importing. Notion only creates relations between synced records when both pages are synced to Notion databases.

## My verdict and the first step

Sync when your team reads GitHub or Jira status in Notion every day and already has eligible Business or Mobile Business access; that's where the managed route fits best. Without a qualifying plan, I'd link to the source record before paying for a sync the team rarely reads. If edits need to flow both ways, consider a third-party sync: Notion's managed source fields are read-only. Whatever route you pick, the setting I'd check twice is the history window, because it decides which pages, and which of your own notes, stay in Notion.

The first step: list the repositories or spaces your team asks about in a normal week, connect an account that can read exactly those, and create the sync with all available history. Before you share it, compare the records it holds with the people who will open it, because Notion's sharing, not the source tool, decides who sees them.