When you try to duplicate a database view from one Notion workspace to another, the operation often fails or produces a broken view. This happens because Notion views are tightly linked to their source database and workspace permissions. This article explains the technical reasons behind this limitation and provides practical workarounds to move or recreate views across workspaces.
Key Takeaways: Database View Duplication Across Workspaces
- Duplicate page > Database block: Duplicating a page containing a database view only copies the view structure, not the underlying data or filters.
- Export as Markdown > Import: Exports lose all view configurations, requiring manual recreation of filters, sorts, and linked databases.
- Linked database view > New workspace: You cannot directly link a database across workspaces; you must duplicate the database itself first.
Why Database Views Are Workspace-Specific
A database view in Notion is a saved configuration of filters, sorts, and display properties applied to a specific database. Each view belongs to exactly one database and one workspace. When you attempt to duplicate a view across workspaces, Notion must resolve the database ID, which is unique to the source workspace. The target workspace has no record of that database ID, so the view cannot reference it. Additionally, permissions and linked databases (relations, rollups) are workspace-scoped. If your view relies on a relation to a database in the source workspace, that relation breaks in the target workspace because the related database does not exist there. Notion’s architecture stores views as metadata within the database object, not as independent objects. Therefore, duplicating a page that contains a database block does not duplicate the database itself; it only duplicates a reference to the original database. If the original database is in a different workspace, the reference points to nothing.
Steps to Move a Database View to Another Workspace
To successfully recreate a database view in a different workspace, you must first duplicate the database itself. Then you can rebuild the view configuration. Follow these steps in order.
- Duplicate the entire database
In the source workspace, open the database page. Click the three-dot menu in the top-right corner. Select Duplicate. In the dialog, choose the target workspace from the dropdown. This creates a copy of the database, including all properties and data, in the target workspace. - Note the original view settings
Before duplicating, open each view you want to recreate. Write down the filter rules, sort order, and any group or calendar settings. Take a screenshot of the view layout so you can match the column width and display options. - Create a new view in the target database
Open the duplicated database in the target workspace. Click the + button next to the last tab in the view bar. Select the same view type as the original (table, board, calendar, gallery, list, timeline). - Apply the saved settings
Click the view name and choose Properties. Add the same columns and reorder them as in the original. Then set filter conditions, sort rules, and grouping exactly as you recorded. For calendar views, set the date property. For board views, set the group property. - Recreate linked database relations
If the original view used a relation to another database, duplicate that related database into the target workspace as well. Then in the target database, create a new relation property pointing to the duplicated related database. Update any rollup properties to use the new relation.
If Notion Still Shows a Broken View After Duplication
Duplicate page shows a blank database block
This occurs when you duplicated a page that contains an inline database block. The block references the original database in the source workspace. To fix this, delete the blank database block. Then insert a new database block and choose the duplicated database from the target workspace. You can also use the Linked database view option and select the duplicated database.
Linked database view shows no data
A linked database view is a copy of a view that displays data from the original database. When you try to link a view across workspaces, Notion cannot find the original database. The only solution is to duplicate the source database into the target workspace first. After duplication, create a linked view of the duplicated database within the target workspace.
Filters and sorts are lost after export and import
Exporting a database as Markdown or CSV strips all view configurations. Filters, sorts, and display settings are not saved in the export file. After importing the data into a new database in the target workspace, you must manually recreate every view. This is the most time-consuming workaround but is reliable for preserving data.
Notion Database View Duplication Methods Compared
| Item | Duplicate database across workspaces | Export and import database |
|---|---|---|
| Data preserved | All properties and rows | All properties and rows |
| View settings preserved | No views copied | No views copied |
| Relations preserved | Broken if related database not duplicated | Broken; must recreate |
| Time required | 5–10 minutes plus recreation | 10–30 minutes plus recreation |
| Best for | Large databases with complex properties | Simple databases with few properties |
You can now move a database view to another workspace by duplicating the source database and manually recreating the view configuration. Next, try using the Linked database view feature within the same workspace to avoid the cross-workspace limitation. An advanced tip: use the Notion API to programmatically duplicate a database and its views into another workspace if you have developer resources available.