> For the complete documentation index, see [llms.txt](https://docs.overflowcms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overflowcms.com/editor-guide/importing-from-webflow.md).

# Importing from Webflow

## Importing from Webflow

### Importing from Webflow

If you're already managing content in Webflow's CMS, you don't have to re-create it by hand. Export any collection as a CSV and OverflowCMS reads its columns, suggests a field mapping, and imports every row — into a brand-new collection or into one you already have. There's no practical size limit: small files import instantly, large ones finish in the background while you keep working.

#### 1. Export your collection from Webflow

In the Webflow Designer, open **CMS > \[your collection] > Export as CSV**. This downloads a `.csv` file with one column per field, plus Webflow's own `Slug`, `Created On`, `Updated On`, `Published On`, and `Archived`/`Draft` columns.

#### 2. Start the import

Open the site in OverflowCMS and click **Import from Webflow** on the site's collections page.

![Site page with the "Import from Webflow" button](https://overflowcms.com/images/docs-screenshots/webflow-import-1.png)

Choose a destination — a new collection (give it a name) or an existing one — then upload the CSV file, or paste its contents directly if that's easier.

![Upload step: destination, collection name, and CSV file/paste input](https://overflowcms.com/images/docs-screenshots/webflow-import-2.png)

Click **Analyze CSV**.

#### 3. Review the field mapping

OverflowCMS reads the header row, suggests a field label and type for each column (text, rich text, image, date, boolean, etc.), and picks a likely `Slug` source column automatically. Review this before importing:

* Uncheck any column you don't want to bring in.
* Adjust a field's label, type, or (when importing into an *existing* collection) which existing field it maps to.
* Change the **Slug source column** if the auto-detected one isn't right — or leave it on "Auto-generate from title" to derive slugs from the title field instead.
* Turn on **Publish imported items immediately** if you want the rows to go live right away; otherwise they land as drafts so you can review them first.

![Column mapping review, with field labels and types per column](https://overflowcms.com/images/docs-screenshots/webflow-import-3.png)

Click **Import N rows**.

#### 4. Let it finish

Small imports complete immediately and show a result summary (imported / published / skipped, plus a per-row reason for anything skipped).

![Import result: imported/published/skipped counts](https://overflowcms.com/images/docs-screenshots/webflow-import-4.png)

Large files (thousands of rows) are handed off to run in the background — you can leave the dialog open and watch a live progress bar, or close it and check back later; the collection's item count updates as rows land. There's no file-size cap: the CSV is uploaded once and processed in small batches behind the scenes, so a large export finishes in roughly the same time per row as a small one.

Click **Go to collection** to see the imported items — its content table is paginated and sortable by any column, so a large import stays easy to browse; see [Publishing Workflow](/editor-guide/publishing-workflow.md) for a look at that view.

#### Tips

* Re-importing into an **existing** collection maps CSV columns to that collection's current fields — anything you uncheck, or that doesn't match a field, is skipped for that row rather than blocking the whole import.
* Rows that fail validation (e.g. a required field left blank) are counted under "Skipped" with a reason, not silently dropped — check the result screen's error list.
* Re-running an import is safe to try — nothing is written until you click **Import N rows** on the mapping step.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.overflowcms.com/editor-guide/importing-from-webflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.