> ## 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.

# Importing your season

> Bring a whole book of business into Soundcheck: spreadsheets, paperwork, recurring sync, or clone a sandbox workspace zip.

You're moving to Soundcheck with a season already on the books: thirty gigs in a spreadsheet, a folder of signed contracts, a CRM you're leaving behind, or a sandbox org you want to clone. Don't re-type any of it. This recipe covers the four intake paths and when to use each.&#x20;

## Pick your path

| Your data looks like… | Use | Why |
| - | - | - |
| A spreadsheet or CSV export | [Import your data and start running](https://docs.soundchecklive.io/features/imports/overview.md) | Bulk, structured, safe to re-run. Up to 50,000 rows a job |
| Contracts, call sheets, riders, emails | [AI file ingestion](https://docs.soundchecklive.io/features/ai/file-ingestion.md) | CheckAI Private Preview: existing beta testers review extracted records before writing |
| A live system that keeps producing bookings | [n8n CRM sync](https://docs.soundchecklive.io/integrations/n8n-crm-sync.md) | Recurring webhook feed instead of one-off loads |
| A sandbox (or golden) org you want to clone | [Export a workspace](https://docs.soundchecklive.io/features/imports/workspace-export.md) | Download UEF JSON + wizard-ready CSVs; restore on Imports or Import a Soundcheck file |

The spreadsheet, paperwork, and sync paths land in the same normalized data via the [Universal Event Format](https://docs.soundchecklive.io/features/imports/universal-event-format.md), so mixing those is safe. A gig imported from a spreadsheet and one extracted from a contract behave the same afterward. Workspace clone uses that same UEF/CSV shape; see below.

## The spreadsheet season

Prefer loading **Crew → Venues → Clients → Songs → Setlists → Events** so gigs match real rooms and clients instead of creating name-only stubs. Open **Settings → Apps & data → Import & export** and drop files first. Full wizard: [Import your data and start running](https://docs.soundchecklive.io/features/imports/overview.md). Leaving Planning Center, Back On Stage, Master Tour, Stagera, or LASSO / Shoflo? Use [Coming from another system](https://docs.soundchecklive.io/features/imports/coming-from.md) for export steps and zip shapes (ShowOps / Umbrella stay BYO until a dump exists).

**1. Shape the export**

One row per gig (or per crew member per gig; see grouping below) with columns for name, date,
venue, customer, and crew contacts. If your old system has stable IDs, keep the ID column.
Mapped external IDs make re-imports update in place instead of duplicating.

**2. Parse**

Open **Settings → Apps & data → Import & export**. Upload the file (`.xlsx` / `.csv` / `.tsv` /
`.txt`, up to 25 MiB) or paste CSV/TSV (up to 8 MiB). Soundcheck normalizes the headers and
samples the rows. There is no Google Sheets connector. Export first.&#x20;

![Import & export page with the drop zone for spreadsheets above recent imports](https://mintcdn.com/soundchecklive/YID1u3xi3y5B4ur8/images/imports/import-wizard-light.png?fit=max\&auto=format\&n=YID1u3xi3y5B4ur8\&q=85\&s=611242a778fc47ab214e217530171271)

**3. Map**

Mapping is required. Review the proposed column → field mappings and adjust. Several crew rows
for the same gig? Set **row grouping** to `group_by_external_id` so they collapse into one event
with multiple members. Soundcheck proposes it when the rows that share a gig ID agree on the gig. Save the mapping as a template if you'll import this shape again.

![Map step of an Events import for a season export, with Gig Name as the event title, Gig Date as the event date, and Event Type, Start Time and End Time auto-matched](https://mintcdn.com/soundchecklive/SK0diQsPrD96SAMt/images/imports/season-mapping-light.png?fit=max\&auto=format\&n=SK0diQsPrD96SAMt\&q=85\&s=444d39bb79f8123392cbed7f61e48bbb)

**4. Review: the dry run**

Choose **Continue to Review**. The **Review** step shows what each row will create, update or
skip, with **Errors**, **Warnings** and **Creates** tabs for row-level problems and the venues and
clients the import adds. Nothing is written yet.

![Review step of the season import with the Errors, Warnings and Creates tabs, the action for each row, and the Commit button](https://mintcdn.com/soundchecklive/SK0diQsPrD96SAMt/images/imports/season-preview-light.png?fit=max\&auto=format\&n=SK0diQsPrD96SAMt\&q=85\&s=e0d53408822c2180096d6eedb51ba19e)

**5. Commit**

Choose **Commit** to write the records. **Results** shows the new and updated events, venues,
clients and invitations, and any skipped rows, so you can audit the run. Re-running the same file
later produces updates, not duplicates. Use that as your confidence check.

![Results step after committing the season import, with the counts of new and updated events, new venues, clients and invitations, and skipped rows](https://mintcdn.com/soundchecklive/SK0diQsPrD96SAMt/images/imports/season-results-light.png?fit=max\&auto=format\&n=SK0diQsPrD96SAMt\&q=85\&s=af13a382f23187e18e0ec0b9c7cb6152)

> [!NOTE]
>
> A bad row doesn't block the whole file. Valid rows commit and rows with errors are skipped. The
> job only lands as **Partial** if a row that passed review fails to write. Download the error file
> from the results screen to see each skipped or failed row and why, then fix and re-import. See
> [When a row is bad](https://docs.soundchecklive.io/features/imports/overview.md#when-a-row-is-bad).

> [!TIP]
>
> Import venues-and-clients-heavy data early. Once your venue directory is populated, every future
> gig at those rooms auto-fills its logistics, and the season you just imported can be grouped into
> [tours](https://docs.soundchecklive.io/features/gigs/tours.md) for per-run financial roll-ups.

## After you commit

Do not stop in the import history tab:

1. Open **Gigs** and confirm the season list.
2. Ask crew to accept org invitations from imported members.
3. Spot-check venues, clients, and Show Prep (songs / setlists).
4. Re-import the same file once. Expect **0 new** rows.

## The paperwork pile (CheckAI Private Preview)

CheckAI beta is **Private Preview, available only to the existing beta tester group**. Signing up, choosing a paid plan, upgrading, contacting support, or viewing a public demo does not grant access. Other organizations can attach their files for reference and enter or import structured records manually.

For gigs that exist only as documents (a signed contract, a forwarded email thread, a call sheet PDF), use [AI file ingestion](https://docs.soundchecklive.io/features/ai/file-ingestion.md):

1. Open the enabled Files preview on a gig and add the documents. Source files attach immediately; extracted records are reviewed separately.
2. CheckAI reads each file and proposes structured records: schedule items, crew with fees, ledger items, leads, and event fields.
3. Review the proposals and matches against existing data. Select the correct records; leave uncertain or incorrect rows unselected.
4. Review combined proposals across files, checking overlapping or conflicting details against the originals.
5. Select **Commit selected** to apply the chosen records in the web app. Crew records are added without sending invitations. External AI clients use a separate confirmation flow; see the [ingestion guide](https://docs.soundchecklive.io/features/ai/file-ingestion.md).

This pairs with the spreadsheet path: import the season's skeleton from the export, then drop each gig's contract on it to fill in schedules, fees, and money.

Paperwork dropped on **Settings → Apps & data → Import & export** is parsed before review. Word, PowerPoint, RTF, OpenDocument, and PDFs with a text layer are converted to Markdown on Soundcheck's servers and never leave them. A scanned or image-only PDF shows **Needs OCR** in the queue; where hosted OCR is turned on, that document alone is sent to Firecrawl Parse to be read. A scan that could not be read, or paperwork over the 25 MB parse limit, shows **Not parsed** and stays with CheckAI. A password-protected or empty file fails on its own and the rest of the drop continues. Photos are not parsed and stay with CheckAI vision.

## Clone a sandbox workspace

Use this when you already have a Soundcheck org (sandbox or golden fixture) and want another org to start from the same catalogs.&#x20;

1. On the source org, open **Settings → Apps & data → Import & export** and click **Download workspace** to get the zip (UEF JSON plus wizard-ready CSVs for crew, clients, inventory, venues, songs, setlists, events, and leads).
2. On the destination org, either:
   * Drop `csv/*.csv` on **Settings → Apps & data → Import & export** (drop-first), or
   * On the same page, use **Import a Soundcheck file** with `uef/workspace.json` (or the zip).
3. Crew rematches on email. Clerk memberships are not copied. A row is skipped when that email is **already a claimed member** on the destination. Importing a Soundcheck file emails no one: members land as unclaimed roster entries without an invitation. An exported **Owner** whose email is new is written as an unclaimed Admin roster row when the importer is an Owner. Only an Owner can invite an Admin, so any other importer skips that row, with a warning. If that email already belongs to a member, that member keeps their current role. Do **not** clone a sandbox into a real org if you do not want that person as an admin. Other unmatched members land as unclaimed roster entries with their exported role. Over the API or MCP, pass `send_invites: true` to email each new member a Clerk invitation instead. Duplicate setlist titles rematch. A second pass is updates only (**0 new**). Files, branding, integration tokens and lead budgets stay out of the zip. Position day rates and shift fees are in it only for people who can view finances.

Member MCP can clone a workspace (`export_workspace` → `preview_import_file` → `import_file`). Public MCP cannot. The Import & export page still works. Full detail: [Export a workspace](https://docs.soundchecklive.io/features/imports/workspace-export.md).

## Common pitfalls

> [accordion] Crew rows were skipped during commit
>
> An invitation needs a way to reach the person. Each crew row must have an email or a phone
> number. Rows without either are skipped, and the **Review** counts reflect that before you commit.

> [accordion] I imported the same file twice and worried about duplicates
>
> Re-importing is safe. Rows matched by external ID or natural key (like title + date for events)
> update in place instead of duplicating. Fixing a file and re-importing it is the expected way to
> correct mistakes, not a risk.

> [accordion] I can't see Settings → Apps & data → Import & export
>
> Imports are rolling out gradually and need an **owner, admin, or gig coordinator** signed into the
> right org. If the page is missing, [contact support](mailto:info@soundchecklive.io) to have it
> turned on, or confirm you are an owner, admin, or gig coordinator on that organization. See [roles &
> permissions](https://docs.soundchecklive.io/settings/team/roles-permissions.md).&#x20;

> [accordion] My spreadsheet has gigs, but the fees are only in the contracts
>
> Use both paths: import the gigs from the spreadsheet first, then drop each contract onto its gig
> and let ingestion propose the ledger items and crew fees.

> [accordion] Past seasons: should I import those too?
>
> If you want history and reporting, yes. Imported past gigs can be marked
> **Completed**/**Settled** so your books reflect them. If you only care about what's ahead,
> importing just the upcoming season keeps things lighter.

## Related

> [card] [Import your data and start running](https://docs.soundchecklive.io/features/imports/overview.md)
>
> Start-here path: order, wizard, bad rows, and what to do after commit.

> [card] [AI file ingestion](https://docs.soundchecklive.io/features/ai/file-ingestion.md)
>
> Extract records from contracts and call sheets.

> [card] [Universal Event Format](https://docs.soundchecklive.io/features/imports/universal-event-format.md)
>
> The shared schema behind every intake path.

> [card] [n8n CRM sync](https://docs.soundchecklive.io/integrations/n8n-crm-sync.md)
>
> Recurring sync for sources with a webhook.

> [card] [Export a workspace](https://docs.soundchecklive.io/features/imports/workspace-export.md)
>
> Clone a sandbox: download the zip, restore CSVs or UEF on the destination org.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.