How to create collections via CSV file?

💻 Environment/Context

CSV
Collection Creation
Collection Management
Bulk collection creation

In order for you to create a new collection(s) on the platform via CSV Import, the Collection management > Can create collection permission should be enabled on your account.

If you don't see it, reach out to your admin or refer to the Account Type Permissions Overview article for more information.

❓ Issue/Question

How to create collections and sub-collections using templates?
How to create collections with CSV files
Creating collections in bulk

👌 Resolution/Answer

Step 1 - Prepare your CSV file

CSV Columns Info

Column	What it means	Required?	Example
Path (slash-separated)	The full folder path to create	✅ Yes	`New Collection/Photoshoot/Team A`
Tags (coma-separated)	Tags ScorePlay should apply to this collection	No	`Photoshoot, cutouts`
Team ID (coma-separated)	Link a team entity to the collection	No	Leave blank if unsure
External ID	Any outside reference ID	No	Leave blank
Raw Name	Notes or original folder name	No	Leave blank
Date (DD/MM/YYYY)	Event or upload date	No	`14/11/2025`

Important Reminders:
- The column headers must match exactly as shown above. Do not rename them.
- Never use / inside a collection name — it will be interpreted as a folder separator and split into two collections.

How does the Folder Tree work?

Everything starts from a root collection. Slashes define the hierarchy:

Root Collection/
├── Sub-collection A/
│   ├── Sub-sub A1
│   └── Sub-sub A2
├── Sub-collection B/
│   ├── Sub-sub B1
│   └── Sub-sub B2
└── Sub-collection C/

In the CSV, this translates to:

Path (slash-separated)
Root Collection
Root Collection/Sub-collection A
Root Collection/Sub-collection A/Sub-sub A1
Root Collection/Sub-collection A/Sub-sub A2
Root Collection/Sub-collection B
Root Collection/Sub-collection B/Sub-sub B1
Root Collection/Sub-collection B/Sub-sub B2
Root Collection/Sub-collection C

💡 Tip: Always include parent collections as separate rows — even if they have no tags. ScorePlay needs each level of the tree to exist.

Step 2 - Fill in the CSV
- Open a blank spreadsheet (Google Sheets, Excel, etc.)
- Add the column headers exactly as listed in the table above. Alternatively, you can download this template: CSV Model file and fill in the information
- Under Path (slash-separated), enter the full folder paths — always start from the root
- Fill Tags (coma-separated) with relevant labels for each collection
- Add Date (DD/MM/YYYY) if applicable (e.g., event date)
- Leave other columns blank unless you have specific Team IDs or External IDs to link
- Export/download as CSV (Comma Separated Values)
  - 💡 Tip: If you run the same structure for every event, save the CSV as a template — only change the root name and date for each time.

Step 3 - Upload to ScorePlay
- Navigate to Configure > Collection Management
- Click Import from CSV
- Click Select a CSV and choose your file
- ScorePlay shows a preview of the collections to be created
- Review the preview — confirm the tree looks correct
- Click Import ScorePlay creates all collections automatically
  - ⚠️ Note: The CSV import currently supports a maximum of 10 rows per import. For larger structures, split your CSV into batches of 10 and import them one at a time, waiting for each confirmation before proceeding.

🔖 Notes

Never use / inside a collection name — it will be interpreted as a hierarchy separator and create unintended sub-collections
Always include parent rows — every level of the tree must have its own row, even without tags
Save your CSV as a reusable template — for recurring events, only change the root name and date each time
Column headers must be exact — any mismatch will cause the import to fail silently or map incorrectly
How to move collections?