Importing sites and content
The import wizard (available from the dashboard) walks you through four steps: choose a source, review what was found, optionally import members, and run.
Supported sources today:
| Source | What you get |
|---|---|
| CSV / TSV | Content collections from tabular data |
| JSON | Content collections |
| Excel (.xlsx) | Content collections, one per sheet |
| Webflow export | Content collections from Webflow CMS exports |
| Bondlayer | A full site — pages, design, styles, content, forms, and members |
The Bondlayer importer is a full-fidelity migration: page structure, styles and breakpoints, design tokens, fonts, forms, repeating lists, detail pages, and media all come across, rewired to MATRIZ’s design-token system. Anything that cannot be represented is reported explicitly at the end of the import — nothing is silently dropped.
Imports are re-runnable: importing the same site again updates what changed in place instead of duplicating it.
Restructuring imported content
Section titled “Restructuring imported content”Some sources carry data in a shape you’ll want to fold together once it’s in
MATRIZ. The most common case: a numbered family of same-typed fields — say
image_1, image_2, … image_12 — that really belong in one gallery field.
From the dashboard’s project view, open the Data tab, find the
collection, and use its row action “Collapse slots into one field…”.
Enter the pattern the fields share (using {n} where the number sits, e.g.
image_{n}), the field to land the combined result in, and whether to retire
the old fields once they’re folded in. Before anything is written you get a
dry-run report — how many rows, how many slots are filled or empty, how many
rows will actually change — which you review and explicitly confirm; nothing
is touched until you do. If the underlying data changes between your review
and your confirmation, you’re shown a fresh report to confirm instead of the
pass silently re-running on stale information.
This same pass is also offered inline, pre-filled, as step 5 of Recurring setup whenever a site has a numbered field family on its participation collection.