Importing Existing Content Into a Collection
A dedicated CSV import lets you bring an existing product catalog, roster, or case-study library into a Piskes collection without re-entering it by hand.
If your product catalog, team roster, or case-study library already exists in a spreadsheet, you don't need to re-enter it by hand into a Piskes collection — a dedicated CSV import now handles it directly.
From any collection, upload a CSV and map its columns to the collection's fields. Rows are validated against those fields as they're imported: a required field left blank, or a value that doesn't fit the field's type, is skipped and reported back with its row number rather than silently dropped or breaking the whole import.
Updating, not just creating
You can choose a key field — a product code or slug, for example — and the import will update existing items that match it instead of creating duplicates. That makes it safe to re-run an import after a spreadsheet changes, rather than something you can only do once.
What to expect
Imported items land as drafts by default, or published immediately if you choose. A single import handles up to 1,000 rows; anything beyond that is truncated and reported so you know to split a larger file rather than have it fail partway through without explanation.
This closes a real gap for anyone moving a site onto Piskes from a spreadsheet, an old CMS export, or another platform's product feed — the collection structure gives you a place to put structured content, and this gives you a practical way to fill it in bulk, not just one item at a time.