Verified migration behavior

Copying a rectangular Google Sheets range and pasting it into a blank Notion page created a simple table automatically. This is useful for a small static reference table, but it is not a database migration.

Test setup

We created two private synthetic Sheets ranges. Each had five columns—name, quantity, due date, URL, and formula total—and two data rows. The second range used different values, then its header was made bold for a formatting retest. Each range was pasted into a new private Notion page.

Tested steps

  1. Create a rectangular source range with headers and synthetic data.
  2. Calculate the Total column with a Sheets formula.
  3. Copy the entire range and paste it into a blank private Notion page.
  4. Confirm the Notion result has the same row and column count and inspect every value/link.
  5. Repeat with independently varied data.
  6. Bold the second source header, copy again, and inspect the resulting Notion header markup.

Both independent ranges became 3 × 5 simple tables. The formatting retest retained bold header text.

Field and format retention matrix

Source feature Notion result Retained?
Header and cell text Same visible strings Yes
Rows and columns Same 3 × 5 grid Yes
Zero and positive numbers Same visible values in simple-table cells Display only
ISO date strings Same YYYY-MM-DD text Display only
Plain HTTPS URLs Same text and clickable links Yes
Formula totals Only calculated values such as 20, 0, 50, and 30 No formula logic
Bold header Bold spans in the Notion table cells Yes
Database property types No typed number/date/URL properties were created No

Choose the migration path

Use clipboard paste for a small, static table whose visible values are the deliverable. If the destination needs typed properties, filters, sorts, formulas, relations, or row pages, create/import a Notion database instead. Notion’s current import guidance recommends CSV for spreadsheet data and lets operators map columns to database properties.

Evidence boundary

The test proves clipboard behavior for the listed field types only. It does not establish retention for colors, merged cells, validation, comments, charts, or database relations. Reconcile row counts and key fields after any larger migration.