Why Notion Workspace Import Cannot Preserve Original Page Creation Date

When you export content from another tool and import it into a Notion workspace, you may notice that every imported page shows the import date as its creation date instead of the original date the page was created. This behavior can cause confusion when you rely on page metadata to track when content was first authored. Notion assigns a new system-level creation timestamp to every page at the moment it is added to the workspace, and the import process does not read or transfer any original creation date from the source file. This article explains why Notion discards the original creation date, how the import pipeline handles timestamps, and what workarounds exist if you need to preserve that information.

Notion uses a single internal identifier for each page that includes a creation timestamp generated by its own servers. When you import a file such as HTML, Markdown, or CSV, Notion creates a brand-new page object and stamps it with the current UTC time. The import parser ignores any date metadata embedded in the source file because Notion does not expose a field for custom creation dates in its import schema. As a result, every imported page will appear to have been created at the moment of import, regardless of when the original content was written.

This limitation is not a bug but a deliberate design choice. Notion treats creation date as an immutable system property that cannot be modified through the user interface or through imports. The only way to record the original date is to store it manually in a separate property or in the page body. This article walks you through the technical reasons behind this behavior and shows you how to work around it without breaking your workflow.

Why Notion Replaces the Original Creation Date During Import

Notion stores every page as a record in its internal database. Each record has a set of system properties that Notion manages automatically. One of those properties is Created, which records the exact timestamp when the page was first created in the workspace. This property is tied to the page’s unique identifier and is generated server-side at the moment of creation.

When you import a file, Notion’s import handler performs the following steps:

1. Parse the source file (HTML, Markdown, CSV, etc.) and extract text content, images, and attachments.
2. Create a new blank page object in the target workspace or database.
3. Insert the extracted content into the new page’s body.
4. Generate a new system-level Created timestamp equal to the current UTC time.

The import pipeline never looks for a date field in the source file. Even if your export file contains a created_at or date metadata tag, Notion ignores it. The system properties are write-protected from user input and from import operations. This is a security measure to prevent users from backdating pages or manipulating audit trails.

Another factor is that many export formats do not include a reliable creation date. For example, a Markdown file exported from another tool may contain a YAML front matter field like date: 2022-03-15, but Notion’s Markdown importer only reads the body content and ignores front matter entirely. HTML exports from platforms like Confluence or WordPress may embed a creation date in a <meta> tag, but Notion’s HTML importer does not parse that tag. The importer is designed to handle content structure, not metadata.

What Happens to the Original Date Information

The original creation date is not lost if you still have the source file. It simply is not transferred to Notion. If you export a page from Notion and re-import it into the same workspace, the re-imported copy will receive a new creation date. The original page retains its original date, but any duplicate created by import will show the import time.

How to Preserve the Original Creation Date After Import

Because you cannot change the system Created property, the only reliable method is to store the original date in a separate database property. This approach works for database imports where you can define custom columns.

1. Create a database with a Date property
   Before importing, create a new database in Notion. Add a property called Original Created and set its type to Date. This property will hold the date you want to preserve.
2. Import your data into the database
   Use Notion’s import feature to bring in your CSV, Markdown, or HTML file. The imported pages will appear with the current date in the system Created field, but the Original Created property will be empty.
3. Extract the original dates from your source file
   Open your original export file in a text editor or spreadsheet. Locate the creation dates. For a CSV file, the date column is usually visible. For Markdown, check the YAML front matter. For HTML, search for datetime or date attributes.
4. Enter the original dates into the database
   Open each imported page in Notion. Click the Original Created property and manually type or paste the original date. You can also use the Edit property option in a database view to update multiple rows at once if you have the dates available.
5. Sort or filter by your custom date property
   Once all dates are entered, you can sort the database by the Original Created field instead of the system Created field. This gives you the chronological order you need.

Alternative: Add the Date in the Page Body

If you do not want to use a database property, you can paste the original creation date at the top of the page body. Use a callout block or a heading to make it visible. This method is less structured but works for any page type, including pages that are not part of a database.

1. Open the imported page
   Navigate to the page that was created by the import.
2. Add a callout block at the top
   Type /callout and press Enter. In the callout text, write something like “Original creation date: March 15, 2022.”
3. Repeat for each imported page
   Manually add the callout to every page that needs the date. This is time-consuming but works for small imports.

Common Misconceptions and Limitations

Can I edit the system Created property with a formula or API?

No. The system Created property is read-only in the user interface and in the Notion API. The API returns the value but does not allow you to update it. Any attempt to set the Created property via the API will be ignored or cause an error.

Does the Notion API import endpoint preserve the original date?

The Notion API’s Create Page endpoint also assigns a new creation timestamp. When you create a page programmatically, you cannot specify the Created time. The API does not accept a created_time parameter. The only timestamps you can set are in custom Date properties.

Will a future update add this feature?

Notion has not announced any plans to allow custom creation dates during import. The company’s public roadmap and changelog do not mention this capability. Users who need this feature should rely on the manual workaround described above.

Notion System Properties vs Custom Properties: Key Differences

Item	System Created Property	Custom Date Property
Editable	No	Yes
Set during import	Always set to import time	Left empty
API modifiable	No	Yes
Supports past dates	No	Yes
Available in all views	Yes	Yes

Notion’s design deliberately separates system-managed timestamps from user-managed properties. The system Created property is a reliable audit record, but it cannot be backdated. Custom Date properties give you full control over date values, including dates that predate the import. Use a custom Date property when you need to preserve original creation dates from external sources.