> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Coming from Stagera

> Export Stagera crew, jobs, and inventory as CSV/XLSX (or dump via their OpenAPI), then import through Assets

**Stagera** (stagera.ai) operators in AV / production houses move data by exporting **CSV / XLSX** (or building sheets from a customer-side API dump), then importing through **Organization → Imports** (`/assets?tab=imports`). There is **no** Stagera connector. Soundcheck does **not** connect to Stagera API keys. PRO-307: files only.

Empty-state Imports is **drop-first**. Drop files on the empty state; don't lead with pick-target-first. There are **no** in-product "Coming from Stagera" cards. There is no Organized / Processing / Queued UI to watch.

**Who can import (web UI):** organization **owner or admin** on the active org, with the `data-import` flag enabled. Prefer in-app target templates when you need a known-good column set.&#x20;

Shared mapping traps (email hard-required on **Crew**, upload types, ICS rejected): [Coming from another system](/features/imports/coming-from#mapping-traps-every-source).

<Tip>
  Walkthrough video is TBD. Until it ships, follow the export steps and screenshot Tips below.
</Tip>

## What you can bring over

| In Stagera                                                       | Import target (UI label)                      | Notes                                                            |
| ---------------------------------------------------------------- | --------------------------------------------- | ---------------------------------------------------------------- |
| People → Crew (import CSV shape / export remap)                  | **Crew**                                      | `first_name`, `last_name`, `email`, `phone`, `role`, plus extras |
| Jobs → Import Events template / jobs list                        | **Events** (+ **Clients**; venue is a string) | Also accepts ICS **in Stagera**; Soundcheck **rejects** ICS      |
| Warehouse → Smart inventory import (XLSX template)               | **Inventory**                                 | Template headers locked below                                    |
| Pick lists / pack manifests (API dump when UI export is missing) | event pack lines when supported               | Shape for season zip; do not promise wizard pack drop-in today   |
| Quotes / invoices / payroll / purchases                          | n/a                                           | Ledger-adjacent; not the season Crew / Events path               |
| Vehicles / reservations                                          | n/a / metadata                                | Not required for a first season load                             |

Prefer **customer CSV / XLSX exports and list downloads from the Stagera UI** when available. Use their OpenAPI only as a **customer export aid** to produce a season zip, not as a Soundcheck connector.

## Official export steps

### Crew

1. In Stagera, open **People → Crew**.
2. Use the Crew **Import CSV** column shape as your remap target (same columns are useful when exporting or rebuilding a sheet):
   `first_name`, `last_name`, `email`, `phone`, `role`, `hourly_rate`, `skills`, `notes`, `is_active`
3. If you have an API dump, keep CrewMember `id` as a provenance / future `external_id` column. The live spreadsheet Crew wizard still dedups on **email** today.

Map at least first / last / email. **Email is hard-required**. Phone-only rows fail. Map `role` → Crew position. Leave `hourly_rate`, `skills`, and `is_active` **unmapped** (no free-form metadata Inventory/Crew dump field).

<Tip>
  Screenshot placeholder: People → Crew → Import CSV column list visible. Caption as Stagera product UI.
</Tip>

### Events / Jobs

1. Open **Jobs**.
2. Use **⋯ → Import Events** template columns as the remap target:
   `name`, `event_date`, `start_time`, `end_time`, `venue`, `status`, `description`, `client_name`, `client_email`, `client_phone`
3. Stagera also accepts `.ics` / `.ical` **inside Stagera**. Soundcheck's importer **rejects** ICS / webcal. Convert to CSV first.

Map `name` → event title, `event_date` → event date, times → start / end time. If you have API `end_date` / multi-day, map toward `event_end_date` when your environment exposes it; otherwise keep in metadata. `venue` is a **string** on the job (not a separate Stagera Venue collection). Build a BYO **Venues** sheet if you need the address graph. Split `client_*` into **Clients** when you want directory matches before gigs.

<Tip>
  Screenshot placeholder: Jobs → Import Events dialog with CSV columns visible. Caption as Stagera product UI.
</Tip>

### Inventory

1. Open **Warehouse → Smart inventory import**.
2. Download the XLSX template and export or reshape your warehouse to match.

Template headers (evidence-locked): **Name**, **Item Code**, **Category**, **Subcategory**, **Brand**, **Model**, **Quantity**, **Unit**, **Condition**, **Location**, **Status**, **Serial Number**, **Cost**, **Weekly Rate**, **Daily Rate**, **Sales Price**, **Replacement Value**, **Rental/Sales**, **Case Type**, **Case Length (in)**, **Case Width (in)**, **Case Height (in)**, **Weight (lbs)**, **Container Name**, **Package Items**, **Purchase Date**, **Warranty Expiry**, **Internal Notes**, **External Notes**.

Soundcheck **Inventory** spreadsheet targets are thin today. Map only fields the wizard actually offers (typically):

* **Name** → inventory name (required; matching is by name)
* **Category** → category (when offered)
* **Quantity** → quantity / stock (when offered)
* **Condition** → condition (when offered)
* **Location** → location (when offered)

Leave Brand, Model, Item Code, Serial Number, Daily Rate, case dimensions, rates, costs, notes, and other Stagera columns **unmapped**. Do **not** invent manufacturer, model, daily\_rate, serial, physical-dimension, or free-form metadata Inventory fields. Keep those extras in your source sheet for reference only.

Do not invent Department / Workflow / Phase / Series / Work Item fields.

<Tip>
  Screenshot placeholder: Warehouse Smart inventory import template download or mapping step. Caption as Stagera product UI.
</Tip>

### Pick lists (optional)

PickList + PickListItem may require an API dump when the UI export path is not confirmed. Map event-scoped lines toward pack items when your season zip and product support it. Keep stage / warehouse / quote flags as **metadata**. Do **not** promote Stagera pick-list stage progression as a Soundcheck runtime.

### API dump (customer-side only)

Admin → **Integrations → Developer Tools**. OpenAPI: [https://app.stagera.ai/api/v2/openapi.json](https://app.stagera.ai/api/v2/openapi.json) · docs: [https://stagera.ai/api-reference](https://stagera.ai/api-reference)

Use that to **produce** CSV / JSON for a season zip. It is **not** a Soundcheck connector. Do not paste Stagera API keys into Soundcheck.

<Tip>
  Screenshot placeholder: Admin → Integrations → Developer Tools. Caption: customer export aid, **not** a Soundcheck connector.
</Tip>

## Recommended zip / sheet layout

```
season-stagera/
  01-crew.csv                    # first_name,last_name,email,phone,role,... + id as external_id if present
  02-clients.csv                 # optional split from events or clients dump
  03-venues.csv                  # BYO if only venue string on jobs
  04-inventory.xlsx              # stagera-inventory-template shape
  05-events-jobs.csv             # name,event_date,start_time,end_time,venue,client_*
  06-pack-lists.json|csv         # optional PickList + items → pack lines
  README.txt                     # API version if used; export date; workspace
```

Drop the files on **Organization → Imports**. Load order: **Crew → Venues → Clients → Songs → Setlists → Events** (add **Inventory** before Events when you have warehouse sheets; Songs / Setlists are usually N/A for AV houses).

## Stagera-specific mapping notes

* Venue is a **string** on Event. BYO a Venues sheet for addresses.
* Stagera accepts ICS; Soundcheck does **not**. Convert.
* Inventory commercial extras (weekly / sales / replacement / serial / dims) stay **unmapped**.
* Do not wire Stagera API keys into Soundcheck.
* Do not promise pack lists or schedule machines via the CSV wizard alone until your environment shows those columns.

<Tip>
  Screenshot placeholder: Soundcheck Organization → Imports map step with Name / Category / Quantity / Condition / Location only. Drop-first empty state.
</Tip>

Full shared traps: [Coming from another system](/features/imports/coming-from#mapping-traps-every-source).

## Import order

1. **Crew**
2. **Venues** (BYO if needed) / **Clients**
3. **Inventory** (warehouse XLSX)
4. **Events** (jobs CSV; attach pack lines when you have them)

Canonical product order: **Crew → Venues → Clients → Songs → Setlists → Events** (Inventory and Leads when you need them).

## Import path

1. Open **Organization → Imports** (`/assets?tab=imports`). Drop files on the empty state (drop-first). Review detected targets, map columns (especially **Email** on Crew), preview, commit.
2. Save a mapping **template** once Crew / Jobs / Inventory headers are mapped.
3. After commit: open **Gigs**, ask people to accept invitations, spot-check inventory / clients, re-import once (expect **0 new** rows).

<Note>
  Older bookmark: **Settings → Organization → Imports** (`/settings/organization/imports`). Prefer **Organization → Imports**. On some builds (including DEV), that Settings path can bounce an owner to `/gigs` instead of the importer. Treat that as a product gap, not a docs typo. `/imports` is a redirect only.&#x20;
</Note>

No Google Sheets connector. No MCP connect URL in this guide. No native Stagera connector.

Partial commit (some rows written when others fail) is shipping via PR **1446** on DEV. Hedge production: until your environment shows it, one bad row can still block the whole file.&#x20;

Full wizard: [Operator data imports](/features/imports/overview). Season recipe: [Importing your season](/faq/workflows/importing-your-season).

## Related

<CardGroup cols={2}>
  <Card title="Coming from another system" icon="right-left" href="/features/imports/coming-from">
    Hub for Planning Center, Back On Stage, Master Tour, Stagera, and LASSO / Shoflo
  </Card>

  <Card title="Operator data imports" icon="file-import" href="/features/imports/overview">
    Organization → Imports wizard, targets, and permissions
  </Card>
</CardGroup>
