Create an import

The import wizard — source file, target collection, mapping.

Where: Database → Imports → Import · /projects/<project>/db/imports/new

Screenshot TODO — capture comes from testing-plan area 05-imports.

The wizard has four steps shown as a progress rail: Source, Target, Mapping, Result. If the Files module is off or no files integration is enabled, the page shows Imports need file storage instead — the CSV and errors.txt live in your project's file storage.

Step by step

1. Source. Pick the File Storage, the Delimeter, and whether the file has a CSV header. Then upload one .csv (browse or drag & drop, up to 50 MB). The file goes straight to storage and is analyzed; changing the delimiter or header option afterwards re-analyzes it without a re-upload.

2. Target. Pick the Schema — the collection the rows go into.

3. Mapping. A table shows every CSV column with Matched, Header, Column Preview (sample values), and Mapping. Columns whose header equals a schema field name are pre-matched automatically. Map the rest by hand (each field can be used once), or mark a column as Don't import. Per column, Don't import on error decides what an invalid value does: checked — the whole row goes to errors.txt; unchecked — the row is imported with that field left empty (unless the schema requires it).

4. Result. Press Import. The button stays disabled until every column has a decision — the hint reads Map every column to a property or mark it as "Don't import". You return to the Imports list, where the run's progress updates live; open it for the details.

See Import records from CSV for a worked mapping example and the field types a CSV column can target.

API reference

Endpoints: Database.