Migrating from Notion to Webflow requires translating a block-based JSON tree into flat CMS fields and HTML, overcoming temporary image URLs, and mapping relational databases to multi-reference fields.
Migrating from Notion to Webflow has no native export-import path and requires a custom-built data pipeline. The fundamental architectural mismatch is significant: Notion stores all content as a nestable, block-based JSON tree where pages, paragraphs, and database rows are all block objects, while Webflow's CMS expects flat Collection Items with discrete field types and validated HTML strings in Rich Text fields. Several Notion property types—including Formula, Rollup, People, Created By, and Last Edited By—have no Webflow equivalent and must be computed into static values or discarded before migration. A production-grade migration requires a Notion block-to-HTML conversion pipeline, a dedicated image asset re-hosting step to handle expiring AWS S3 signed URLs, and a two-pass architecture for resolving relational references between Collections.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Decide what content deserves to move before you plan how to move it.
Objective A content inventory with a keep/rewrite/retire decision on every article and an agreed URL strategy.
Keep these open
-
Inventory all content in Notion
Count articles, categories, attachments, images and embedded media, and pull page views and last-updated dates for each article. Usage data is what makes the next decision defensible rather than political.
Data Profiler Get real record counts instead of estimating from memory -
Make a keep, rewrite or retire call on every article
Most knowledge bases are half stale. Migrating everything imports the staleness and doubles the work; use views and last-updated to triage, and get the owning team to confirm. This usually removes 30-50% of scope.
Migrating stale content is the most common knowledge-base migration mistake — it costs effort and actively degrades the new site.
-
Agree the URL and redirect strategy
Decide the Webflow URL structure and whether you can serve 301 redirects from the old paths. Public help centres carry real search traffic and inbound links; losing it is a measurable commercial impact.
Without 301 redirects from old article URLs you lose accumulated search ranking and every external link and bookmark breaks.
-
Map the information architecture
Document the current category tree and design the target one, checking whether Webflow supports your nesting depth. Deeply nested hierarchies frequently have to be flattened, which changes navigation for everyone.
-
Confirm permissions, audiences and localisation scope
Establish which content is public, internal or restricted, and how Webflow models that. Then confirm how many locales you have and whether translation relationships between articles survive the move.
Don't move on until
- Full content inventory with page views and last-updated dates
- Keep / rewrite / retire decision recorded per article
- URL and redirect strategy agreed with whoever owns SEO
02 Data Audit Audit the markup, the links and the assets — that is where KB migrations break.
Objective A content export with markup, internal links and every embedded asset accounted for.
Keep these open
-
Export content and assess markup fidelity
Export articles in the richest format available and inspect what survived: tables, code blocks, callouts, nested lists, anchors and embedded video. Rich formatting is where fidelity is lost, and it is lost quietly.
HTML-to-Markdown conversion routinely mangles nested lists, tables and code blocks. Inspect the output rather than trusting the converter.
Data Profiler Profile the Notion export for nulls, outliers and type drift -
Inventory every internal link and cross-reference
Extract all internal links, anchor links and article cross-references. These break by default: the target URL structure differs, so every internal link needs rewriting as part of the load, not afterwards.
Internal links left pointing at old URLs turn the new knowledge base into a maze of 404s on day one.
-
Inventory images, attachments and embedded media
List every asset with its URL, size and type, and confirm each still resolves. Assets hosted on the old platform's CDN will 404 the moment you decommission it, so they must be rehosted, not referenced.
Images referenced from the source platform's CDN break when the old account closes. Download and rehost every asset.
-
Find and fix broken links and orphans
Crawl for existing broken internal and external links, and find articles no category links to. Fix them before migrating — a migration is a bad time to discover pre-existing rot.
-
Check for PII and internal information in public content
Scan for customer names, internal hostnames, credentials in code samples and screenshots containing real data. Republishing these on a public help centre is a disclosure, and screenshots are the usual culprit.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Normalise metadata
Standardise authors, tags, timestamps to UTC, and locale codes. Author mapping needs a decision for people who have left — attribution to a deleted user usually fails the import.
Don't move on until
- Content exported with markup fidelity assessed
- Every internal link and asset reference inventoried
- Broken links and missing assets fixed or logged
03 Field Mapping Map structure, metadata, permissions and — above all — URLs.
Objective A mapping covering article fields, taxonomy, permissions and a complete old-to-new URL map.
Keep these open
-
Map the article schema
Map title, body, excerpt, author, dates, status, tags, SEO metadata and any custom properties. Confirm which fields Webflow lets you set on import versus which it computes — computed dates are a common surprise.
Schema Mapper Opens pre-loaded with the Notion → Webflow field pair -
Map the taxonomy and hierarchy
Map categories, sections and tags to the target structure, resolving any nesting-depth limit explicitly. If you must flatten, decide how the lost level is preserved — usually as a tag or a title prefix.
JSON to CSV Converter Flatten nested API responses into a reviewable sheet -
Map permissions and audience segmentation
Map public, logged-in, and role-restricted visibility to Webflow's model. Verify the mapping deliberately: internal content accidentally published publicly is the highest-severity failure in this whole category.
Permission mapping errors publish internal documentation to the open web. Verify visibility on every restricted article after load.
-
Build the complete old-to-new URL map
Produce a row per article mapping the old URL to the new one, then confirm exactly where the 301s will be served — Webflow, a CDN, or your own web layer. Without this artifact the redirect step cannot be executed at all.
-
Define the markup conversion and link-rewrite rules
Specify how each markup construct converts and how internal links are rewritten using the URL map. Write it as a repeatable transform, not manual edits — you will run it more than once.
Data Format Converter Reshape the export into the format Webflow's importer expects -
Plan localisation and freeze the spec
Confirm how translated articles link to their source language in Webflow, then version and sign off the mapping spec.
Don't move on until
- Article schema and taxonomy mapped
- Permission and audience model mapped to target equivalents
- Complete URL map produced and redirect method confirmed
04 Test Migration Pilot the hardest articles, then read them.
Objective A pilot load whose formatting, links, assets and search all hold up under human review.
Keep these open
-
Configure Webflow with the agreed structure
Create the category tree, permission groups, locales and branding before loading. Articles loaded before their categories exist land uncategorised and have to be moved by hand.
-
Pick the most difficult articles as the pilot
Choose 20-50 articles for difficulty: the longest, the most heavily formatted, ones with tables and code blocks, deep internal linking, many images, embedded video, restricted visibility, and non-Latin scripts. Easy articles prove nothing.
-
Run the conversion and load with link rewriting
Apply the markup conversion, rewrite internal links from the URL map, upload and re-reference assets, then load. Log every conversion warning rather than suppressing it.
-
Read every pilot article side by side
Open source and target together and compare rendering. This step is manual on purpose: no automated check catches a table that collapsed into a paragraph or a code block that lost its indentation.
-
Click every link and load every asset
Verify each internal link resolves, each image loads from the new host, each attachment downloads and each embed plays. Assets still served from the old CDN are the defect that surfaces only after decommissioning.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Test search and permissions
Search for known terms and confirm the right articles rank, then verify every restricted pilot article is invisible to an anonymous browser. Test permissions from a logged-out session, not an admin one.
Don't move on until
- Complex articles render correctly with formatting intact
- Every internal link and asset in the pilot resolves
- Search returns sensible results for the pilot content
05 Cutover Publish, redirect, and keep the search traffic.
Objective All in-scope content live in Webflow with redirects serving and search engines informed.
Keep these open
-
Load the full content set ahead of the switch
Run the full conversion and load into Webflow, unpublished or on a staging domain. Content migration differs from data migration here: you can stage the whole thing before anyone sees it.
-
Publish the runbook with the redirect step first-class
Sequence the freeze, final delta, publish, redirect activation, sitemap submission and link updates, with owners for each. Redirect activation is the step with lasting commercial consequences, so it gets explicit ownership.
-
Freeze editing and migrate the delta
Stop editing in Notion, then convert and load anything changed since the full load. Announce the freeze to every team that publishes — content teams are used to editing whenever they like.
-
Publish and verify permissions live
Publish the content set, then immediately verify restricted articles are not publicly reachable using an anonymous session. Do this before announcing the new site, not after.
Verify restricted content from a logged-out browser. An admin session will show you everything and tell you nothing.
Migration Validation Tool Confirm the final delta landed before you reopen -
Activate 301 redirects and submit the sitemap
Turn on the redirects from the URL map, then spot-check a sample of high-traffic old URLs and confirm each returns 301 to the right article. Submit the new sitemap and keep the old one reachable until search engines have recrawled.
Redirect chains and redirect loops both leak ranking. Verify each redirect resolves in a single hop.
-
Repoint in-product and support links
Update help links embedded in your product, in support macros, in email templates and in onboarding material. These are the links your existing customers actually use, and they are easy to forget.
Don't move on until
- All content loaded, categorised and correctly permissioned
- 301 redirects live and verified from a sample of old URLs
- Sitemap submitted and support links repointed
06 Validation Watch traffic, links and search rankings for weeks, not hours.
Objective Verified content completeness, healthy redirects, and search traffic recovered to baseline.
Keep these open
-
Reconcile content counts and assets
Compare article counts by category and status, plus asset counts, against source. Confirm every article in the keep list is present and every retired one genuinely is not.
Migration Validation Tool Reconcile Notion and Webflow record-for-record -
Crawl the new site for broken links and assets
Run a full crawl for 404s, broken images and missing attachments, and fix everything it finds. Repeat the crawl after the fixes rather than assuming they worked.
-
Verify the redirects at scale
Test every mapped old URL for a single-hop 301 to the right destination. Chains and loops both leak ranking and are invisible unless you check the whole map, not a sample.
-
Monitor organic traffic and rankings for four to eight weeks
Track organic sessions, impressions and rankings for your top articles against baseline. A dip in the first two weeks is normal; one that has not recovered by week six is a redirect or indexing problem to investigate.
Do not decommission the old platform until search traffic has recovered — you may still need the old URLs to diagnose a ranking loss.
-
Verify search, permissions and feedback loops
Confirm on-site search returns good results for real queries, re-verify restricted content from a logged-out session, and check article feedback and analytics are collecting.
-
Sign off and decommission on a delay
Get acceptance against the Discovery criteria, keep Notion available read-only until traffic has recovered, take a final export, and only then close the account.
Don't move on until
- Article counts reconciled and no broken links remain
- Redirects returning 301 with no chains or loops
- Organic traffic recovered to within tolerance of baseline
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
Notion Property Types Webflow Field Types
| Notion field | Webflow field | Notes |
|---|---|---|
| Title | Name (required) | Direct map. Webflow requires a Name field on every Collection. |
| Rich Text | Rich Text | Requires Notion JSON → Markdown → HTML conversion pipeline. |
| Number | Number | Direct map. |
| Select | Option (Single) | Direct map. Options must pre-exist in Webflow schema or be created via API before item creation. |
| Multi-Select | Option (Multiple) | Direct map with same pre-creation requirement. |
| Date | Date/Time | Direct map. Convert ISO 8601 string from Notion to Webflow's accepted format. |
| Checkbox | Switch (Boolean) | Direct map. |
| URL | Link | Direct map. |
| Direct map. | ||
| Phone | Plain Text | Webflow has no native Phone field type. Serialize to Plain Text. |
| Files & Media | Image or File | Must download from Notion's temporary S3 URL and re-upload to Webflow Assets API. |
| Relation | Reference / Multi-Reference | Requires two-pass migration. Target collection items must exist before reference can be set. |
| Rollup | Plain Text or Number | No native equivalent. Compute the rollup value in your script and store the result as a static field. |
| Formula | Plain Text or Number | No native equivalent. Evaluate the formula result from the Notion API response and store the static output. |
| Created Time | Date/Time | Map to a Date field. Note: Webflow's createdOn field is system-managed and cannot be overwritten via the CMS API. Store separately. |
| Last Edited Time | Date/Time | Same constraint as Created Time. |
| Created By | Plain Text | No equivalent. Serialize to "First Last" string or discard. |
| Last Edited By | Plain Text | No equivalent. Serialize or discard. |
| People | Plain Text | No equivalent. Serialize as comma-separated names or emails. |
| Status | Option (Single) | Map status groups to single-select options. Not all status values may translate meaningfully. |
| Unique ID | Plain Text | Store as a plain text field for cross-reference tracking. Useful as a permanent key in your ID mapping store. |
| Verification | Plain Text | No equivalent. Serialize state ("verified" / "unverified") as plain text or discard. |
| Button | Discard | UI element only. Not data. Cannot and should not migrate. |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Rich Text Content | high | Notion's block-based JSON structure must be fully converted to sanitized HTML, and unsupported block types such as Toggles, Callouts, Columns, Embeds, and Equations require lossy degradation strategies that result in layout and formatting loss. |
| Images & Media Files | high | All image assets return temporary S3 signed URLs that expire in one hour, making direct URL mapping a guaranteed failure mode; every asset must be individually downloaded and re-uploaded to Webflow's Assets API during migration. |
| Relation & Reference Fields | high | Relational references cannot be resolved in a single pass because Webflow Item IDs are generated at write time, and any target item that fails to migrate in Pass 1 will cause cascading 400 validation errors for all items that reference it in Pass 2. |
| Formula Properties | high | Webflow has no native Formula field type, so formula results must be read from the Notion API response as pre-evaluated static values and stored in a plain text or number field, permanently losing the dynamic calculation logic. |
| Rollup Properties | high | Rollup fields have no Webflow equivalent and must be computed at migration time and stored as static values, meaning any future updates to source records in Webflow will not recalculate the rollup automatically. |
| Select & Multi-Select Options | medium | All option values must be pre-created in the Webflow Collection schema via API before item creation begins, and any option encountered during migration that was not pre-seeded will cause item write failures. |
| People & User Properties | medium | Notion People, Created By, and Last Edited By fields have no Webflow equivalent and must be serialized to plain text strings or discarded, resulting in permanent loss of structured user attribution data. |
| System Timestamp Fields | medium | Webflow's createdOn field is system-managed and cannot be overwritten via the CMS API, meaning original Notion creation and last-edited timestamps must be stored in separate custom Date fields rather than native metadata fields. |
| Inline & Nested Databases | medium | Notion databases embedded inline within a page cannot be migrated in place and must be extracted, migrated separately as their own Webflow Collection, and then linked back via a hyperlink, losing their inline contextual presentation. |
| Phone Number Properties | low | Webflow has no native Phone field type, but phone number values can be mapped directly to a Plain Text field with minimal data loss, requiring only a schema decision before migration begins. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Block-to-HTML Conversion Pipeline
Notion's nested JSON block array must be parsed and converted into a single, validated HTML string that conforms to Webflow's Rich Text field sanitization rules, requiring a two-step Notion JSON → Markdown → HTML transformation to avoid silent element stripping or 400 Bad Request rejections.
Expiring Image Asset URLs
Notion's API returns AWS S3 signed URLs for image blocks that expire after exactly one hour, requiring every image to be downloaded and re-uploaded to the Webflow Assets API to obtain a permanent CDN URL before any CMS item write occurs.
Two-Pass Relational Reference Mapping
Webflow Reference fields require the target item's 24-character Webflow Item ID, which does not exist until the target Collection has been fully migrated, forcing a two-pass architecture where a local ID mapping store must be populated before any referencing items can be written.
No-Equivalent Property Degradation
Notion property types including Formula, Rollup, People, Created By, Last Edited By, and Verification have no native Webflow field equivalent, requiring each to be evaluated to a static value or explicitly discarded before item creation to prevent 400 validation errors.
Schema Pre-Creation Requirement
Webflow requires that all Option values for Single and Multi-Select fields exist in the Collection schema before any items referencing those options are pushed via the API, meaning the full option set must be extracted from Notion and created in Webflow as a prerequisite step.
API Rate Limit Throughput Constraints
Webflow's CMS API is capped at 60 requests per minute, meaning a migration involving 2,000 images alone consumes approximately 33 minutes of upload time before any item writes begin, requiring rate-limit-aware queuing and accurate time estimates for large datasets.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I export Notion to Webflow using CSV?
Yes, but it is highly limited. A CSV export will transfer basic text fields, but it strips all rich text formatting, drops page content, breaks relational links, and exports images as temporary URLs that will expire.
Why do my Notion images break in Webflow after an hour?
Notion hosts images on AWS and provides signed URLs that expire exactly 60 minutes after generation. To fix this, your migration script must download the image file and re-upload it to Webflow's asset manager before linking it in the CMS.
How do I handle Notion relations in Webflow?
Notion Relations map to Webflow Reference or Multi-Reference fields. You must use a two-pass migration: first migrate the parent items to get their Webflow IDs, then migrate the child items and inject those IDs into the reference fields.
What is the Notion API rate limit?
The Notion API allows an average of 3 requests per second. Exceeding this will trigger a 429 Too Many Requests error, requiring your migration script to implement exponential backoff.