Back to the guides

PRACTICAL SOFTWARE GUIDE

Webflow CMS CSV imports: update matching items without creating duplicates

Treat a CMS import as a controlled data migration: preserve identifiers, create a restore point and reconcile a small pilot before the full update.

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Decide whether rows should create or update items

Webflow can import every CSV row as a new Collection item or link rows to existing items and update matches. The update path relies on the Item ID exported by Webflow. Preserve that identifier as data, not as a label someone can rewrite. If a spreadsheet has lost the original Item ID column, treat it as a new import and investigate duplicates before proceeding.

Build a representative pilot file

Export the current Collection and keep an untouched copy. Create a pilot with one unchanged item, one item whose plain-text field changes, one item with a reference, one rich-text item and one row intended to be new. Use synthetic or approved content. Record the expected slug, status and field values for every row before uploading.

  1. Create a named backup or confirm an appropriate restore point exists.
  2. Choose the option to link and update matching items only when the Item IDs are intact.
  3. Map each column deliberately; do not map an ambiguous column merely because its name looks similar.
  4. Complete the pilot and compare the resulting Collection items with the acceptance table.
  5. Export the Collection again and reconcile row counts, IDs and changed fields.

Review fields that do not round-trip cleanly

Webflow documents that rich text exports as HTML, references export as text or URLs and multi-reference fields export as comma-separated text. Images and files can retain Webflow-hosted URLs, while file fields are not imported through the same CSV migration path. Inventory these fields before assuming the export is a complete portable backup.

A worked reconciliation example

Imagine a fictional directory with 120 suppliers. Five descriptions need correction and two suppliers are new. Export the Collection, keep the Item IDs for the five existing suppliers, and prepare two rows without those IDs for the new entries. After the pilot, verify that the five existing URLs still resolve and that only two new items were created. This is a planning example, not a measured Webflow test.

Keep an import record

Retain the source export date, pilot filename, mapping table, selected import mode, operator, backup point and reconciled counts. If translated locales are involved, record which locale view produced the export because Webflow states that a Collection export contains the current locale view.

Sources and verification

Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.

Continue your evaluation

Practical guides for this topic

Put your tools to work.

Need help choosing or setting up your tools? Tell Koldia what you want to improve.

Discuss your project