Why Notion Database Cannot Be Renamed Without Affecting Linked Views

You renamed a Notion database in one place and suddenly all linked views that reference that database broke or now display an empty state. This happens because a linked database view in Notion is not a copy of the data but a live filter window that points to the original database by its internal ID. When you rename the source database, the link does not automatically update everywhere, causing views that relied on the old name to lose their connection. This article explains the technical reason behind this behavior and shows you exactly how to rename a database without breaking your linked views.

Why Renaming a Database Breaks Its Linked Views

Every Notion database has a unique internal identifier that does not change when you edit the page title or database name. A linked database view stores a reference to this ID, not the name string. So in theory, renaming the source database should not break the link.

The problem occurs because of how Notion handles the link when you rename the database from a location that is not the original database page. If you rename the database from inside a linked view’s settings or from a page that is a child of another database, Notion may create a new database container instead of updating the existing one. This new container gets a new internal ID, and all linked views that pointed to the old ID now point to a database that no longer exists.

Another scenario involves the “Link to database” property used in relations. When you rename a database that is the target of a relation, the relation property still works because it uses the ID. But if you then open the relation property’s settings and reselect the database by its new name, you may accidentally create a duplicate link that breaks the original connection.

The difference between renaming the page title and renaming the database title

A Notion database is both a page and a database container. The title at the top of the page is the page title. The name that appears in the “Select a source” dropdown of a linked view is the database title. These are the same string, but Notion treats them differently. Changing the page title from the page itself updates both. Changing the name from a linked view’s source selector changes only the database title, and this can cause the link to break if the view was created using the old name string.

Steps to Rename a Notion Database Without Breaking Linked Views

Follow these steps in order to ensure all linked views remain connected after you rename the database.

1. Identify all linked views before renaming
   Open the source database and click the “…” menu in the top right corner. Select “Copy link to view” and paste it into a temporary note. Do this for every linked view that uses this database. You will use these links later to verify the views still work.
2. Rename the database from its original page
   Navigate to the original database page. Click the title at the very top of the page. Type the new name and press Enter. This changes both the page title and the database title without creating a new internal ID.
3. Update each linked view’s source reference
   Go to each page that contains a linked view of this database. Click the linked view’s title to open the view settings. Click the “Select a source” dropdown at the top of the panel. Confirm that the newly renamed database appears in the list. If it does not, click “Add a source” and search for the new name. Select it to re-link the view.
4. Check relation properties that target this database
   For any database that has a relation property pointing to the renamed database, open the relation property settings. Click the target database name. If it still shows the old name, click “Change” and select the renamed database from the list. This ensures the relation does not break.
5. Verify all linked views display the correct data
   Open each link you saved in step 1. The view should load the same data as before, now under the new database name. If a view shows “No data” or an error, repeat step 3 for that specific view.

Common Issues After Renaming a Database

Linked view shows “Source database not found” error

This error appears when the linked view’s internal reference points to a database ID that no longer exists. The most common cause is renaming the database from inside a linked view’s settings panel instead of from the original page. To fix this, delete the broken linked view and create a new one by clicking “+” on the page, selecting “Linked view of database,” and choosing the renamed database from the list.

Relation property shows the old name but still works

If the relation property still displays the old database name but the relation itself functions correctly, the internal ID is still valid. You can safely ignore the display name until you need to edit the relation. When you do edit it, select the renamed database in the relation settings to update the display name.

Duplicate databases appear after renaming

Renaming from a linked view’s source selector sometimes creates a second database with the new name while leaving the original database unchanged. This happens because Notion interprets the rename as a request to create a new database source. To fix this, delete the duplicate database and repeat the rename process from the original database page as described in the steps above.

Notion Database Rename: Original Page vs Linked View Source

Item	Rename from Original Page	Rename from Linked View Source Selector
Internal ID	Stays the same	May change
Linked views	Remain connected	May break
Relation properties	Remain intact	May require re-linking
Duplicate risk	None	Possible
Recommended method	Yes	No

Renaming from the original database page is the only safe method. Using the linked view source selector can cause data loss and broken views that require manual recovery.

Now you know exactly why renaming a Notion database can break linked views and how to avoid this problem. Always rename the database from its original page title bar to preserve the internal ID. After renaming, verify each linked view by opening its source selector and confirming the correct database is selected. For advanced setups with multiple relation properties, use the “Copy link to view” feature before renaming so you can quickly check each view afterward.