When you import data into a Notion database, you may see a “Database Schema Conflict” error. This happens when the structure of the incoming data does not match the existing database schema. The conflict usually occurs because of mismatched property types, missing required fields, or duplicate column names. This article explains the root cause of the schema conflict and provides clear steps to resolve it on import.
Key Takeaways: Resolving Notion Database Schema Conflict on Import
- Database property type mismatch: The most common cause — a column in the imported file has a type that conflicts with the existing Notion property type
- Settings & Members > Import > Map Fields: Use the field mapping dialog to align each imported column to the correct Notion property before completing the import
- Manual schema audit before import: Review the target database property types and ensure the import file columns match them exactly to prevent conflicts
Why a Database Schema Conflict Occurs During Import
A database schema conflict in Notion arises when the import operation tries to create or update properties that conflict with the existing schema of the target database. Notion databases are schematically strict — each property has a defined type such as Text, Number, Select, Date, or Relation. When you import a CSV, Excel, or other file, Notion attempts to map each column to a database property. If a column contains data that does not match the property type — for example, a column with mixed text and numbers mapped to a Number property — Notion cannot resolve the conflict and returns the error.
The conflict also occurs if the imported file includes columns that duplicate existing property names but with different types. For instance, if your database already has a property named “Status” of type Select and your CSV also has a “Status” column with free-form text, Notion sees a type conflict. Similarly, missing required properties that have validation rules can trigger the error. Understanding this root cause lets you fix the file or the database schema before retrying the import.
Steps to Resolve the Schema Conflict on Import
Follow these steps to resolve the “Database Schema Conflict” error when importing data into a Notion database. The process involves prepping the import file, adjusting the target database schema, and using the correct import settings.
- Identify the conflicting property types
Open the target database in Notion. Note every property name and its type by clicking the property header. For example, if you see “Price” as a Number property, any imported column called “Price” must contain only numeric values. Make a list of all property names and types. - Clean the import file to match the schema
Open your CSV, Excel, or other import file. Rename columns to match the Notion property names exactly. Ensure data in each column matches the property type: text for Text, numbers for Number, valid date strings for Date, and so on. Remove any extra columns that have no matching property in the target database. - Use the Map Fields dialog during import
In Notion, go to Settings & Members > Import. Select your file. When the preview appears, click the “Map Fields” button. A dialog shows each column from your file and the matching Notion property. If a column shows a red warning or mismatch, click the dropdown and select the correct Notion property. Skip unmatched columns by choosing “Don’t import.” - Add missing properties to the target database
If the import file contains columns that do not exist in the target database, you have two options. Option one: add those properties to the Notion database by clicking the + icon in the last column header and selecting the correct property type. Option two: remove those columns from the import file. Adding properties is often faster and preserves all data. - Change property types in the target database if needed
If a property type in the database does not match the data you need to import, change the property type. Click the property header, select “Edit property,” and choose a compatible type. For example, change a Text property to Select if your import file contains predefined options. Note that changing types may affect existing data — test on a copy first. - Retry the import with the corrected file and schema
After adjusting the file and the database schema, go back to Settings & Members > Import. Re-upload the cleaned file. Use the Map Fields dialog again to verify all mappings are green (no conflicts). Click “Import.” The operation should complete without the schema conflict error.
If Notion Still Shows a Schema Conflict After the Main Fix
Import file has duplicate column names
If your CSV or Excel file has two columns with the same header, Notion cannot map them correctly. Open the file and rename one of the duplicate columns. For example, change “Cost” and “Cost” to “Cost” and “Cost (Estimated).” Then re-upload and remap.
Database contains a formula property that references imported columns
Formula properties in the target database may depend on other property types. If you change a property type to match the import file, the formula may break and cause a conflict. Before importing, check all formula properties. If a formula references a property you are about to change, either update the formula to use the new type or remove the formula temporarily.
Relation or Rollup properties block the import
If the target database has Relation or Rollup properties, the import may conflict because these properties require data from another database. Remove or disable Relation and Rollup properties from the target database before importing. After the import succeeds, re-add them and link the records manually or via a second import.
Imported data contains empty cells in required fields
If a Notion property is set to “Required” in the database settings, any imported row with an empty value for that property causes a conflict. Open the database and remove the required constraint on that property before importing. After import, you can re-enable the constraint and fill in missing values.
Database Schema Conflict Causes: Import File vs Notion Database Properties
| Conflict Cause | Import File Side | Notion Database Side |
|---|---|---|
| Property type mismatch | Column contains data type that does not match the Notion property type | Property is set to a type incompatible with the column data |
| Duplicate property names | Two or more columns share the same header name | Database already has a property with that name but different type |
| Missing required properties | Column for a required property is missing entirely | Property is marked as Required in database settings |
| Extra columns with no match | File contains columns that do not exist in the target database | No property exists to receive the column data |
| Relation/Rollup dependencies | Data attempts to link to a relation or rollup property incorrectly | Relation or Rollup property expects linked data from another database |
Once you align the import file columns with the Notion database property types and remove schema blockers like required fields or relation dependencies, the import should succeed. Always test with a small sample of rows first to catch conflicts early.
Now you can confidently import data into Notion without encountering the “Database Schema Conflict” error. Start by auditing the property types in your target database and cleaning your import file. For advanced control, use the Map Fields dialog to manually align each column. If you frequently import similar data, consider creating a template database with the exact property types you need to avoid future conflicts.