❗️Bulk data imports are currently handled directly by the Prospero team. Only data that has been properly formatted can be imported. Please reach out to us at support@prosperoapp.com with your request or questions about formatting. We are working on bringing this functionality into the app.
Supported Formats
Bulk import currently supports one file format:
CSVs are easy to generate with most spreadsheet programs:
Google Sheets - File > Download > Comma Separated Values (.csv)
Excel - File > Save As > Save as type > CSV (Comma delimited)
Numbers - File > Export To > CSV…
Supported Data Types
People
Events
Items
Other data types (like Projects, Locations, and Consumables) must currently be manually entered in-app. If you need support for another data type, let us know at support@prosperoapp.com.
Schemas
Your data must conform to Prospero’s schema to be properly processed. Schemas for supported data types are described below, along with an example CSV that you can open in your preferred spreadsheet program.
✅ Required fields must be present in a row for that row to be imported. Optional fields may be left blank.
People
The People schema contains the following fields:
| Required fields |
legal_first_name | ✅ |
legal_last_name | ✅ |
stage_name |
|
nickname |
|
title |
|
| |
phone |
|
notes |
|
Note that not all People fields are supported. The following fields can only be edited in-app:
Pronouns
Headshot
We suggest updating these fields in-app after importing your data.
Events
⏰ Timezone - When submitting your bulk import request, please specify the timezone you would like your Events imported in.
The Event schema contains the following fields:
| Required fields | Usage |
title | ✅ |
|
start_date | ✅ |
i.e., 2025-06-14 |
start_time | ⚠️ |
i.e., 7:30 or 14:00
NOTE: If
|
end_date | ⚠️ |
i.e., 2025-06-14
NOTE: If |
end_time | ⚠️ |
i.e., 7:30 or 14:00
NOTE: If |
status | ✅ | One of: -Tentative -Confirmed -Canceled |
flag |
| Leave this field blank to keep |
draft |
| Leave this field blank to keep |
projects |
| Project names separated by semicolons i.e., Footloose;The Tempest |
role_groups |
| Role Group names separated by semicolons i.e., Creative Team;Cast
NOTE: Including a Role Group name will automatically add all Roles in that Role Group to the Event, as well as the People associated with those Roles |
roles |
| Role names separated by semicolons i.e., Director;Music Director
NOTE: Including a Role name will automatically add the Person associated with that Role to the Event, if there is an associated Person |
locations |
| Location names separated by semicolons i.e., Studio A;Mainstage |
groups |
| Group names separated by semicolons i.e., Admin;Cast
NOTE: Including a Group name will automatically add all People in that Group to the Event |
people |
| Person emails separated by semicolons |
collections |
| Collection names separated by semicolons i.e., Rehearsal Set;Footloose Props
NOTE: Including a Collection name will automatically add all Items in that Collection to the Event |
items |
| name:quantity separated by semicolons (quantity is optional) i.e., Rehearsal Blocks:4;Band Uniform
NOTE: If quantity is not included, all Items in that set will be added to the Event |
consumables |
| name:quantity separated by semicolons (quantity is required) i.e., Coffee:5;Sandwiches:5 |
tags |
| Tag names separated by semicolons i.e., Press;Rehearsal |
details |
|
|
❗️If a matching Project, Role Group, Role, Location, Group, Person, Collection, Item, Consumable, or Tag is not present in your account, it will be rejected. Double-check spelling to ensure a smooth import.
Items
📦 Items vs. Item Sets - In Prospero, items belong to item sets. When importing items via CSV, these fields correspond to item sets:
name
color
details
tags
The quantity field determines the number of child items that are created within the item set. These fields correspond to the child items:
default_location
condition
lifecycle_status
Note that all child items will share the same values for these fields. If you would like to alter a specific item's values, you will need to do so in-app after importing.
The Item schema contains the following fields:
| Required fields | Item Set or Item field | Usage |
name | ✅ | Item Set |
|
color |
| Item Set | A color hex code without the leading #. Leaving this field blank will result in 000000 (black). |
details |
| Item Set |
|
tags |
| Item Set | Tag names separated by semicolons i.e., Microphone;Handheld |
quantity | ✅ |
| Minimum 1 |
default_location |
| Item | Location name i.e., Props Closet |
condition | ✅ | Item | One of: -Functional -Needs Repair -Under Repair |
lifecycle_status | ✅ | Item | One of: -In Transit -Owned -Discarded |
Note that not all Item fields are supported. The following fields can only be edited in-app:
Custom ID
We suggest updating these fields in-app after importing your data.