Coming from another system

You bring a spreadsheet in. You cannot ingest Planning Center plans, Back On Stage setlists, or Master Tour tour books as files. There is no native connector for any of these products. Import CSV, XLSX, TSV, or TXT through Settings → Data & knowledge → Import & export only, loose or in a .zip. Every source uses the same route: get a CSV (or XLSX / TSV / TXT), open Settings → Data & knowledge → Import & export. Drop or paste first on the empty state, review the detected target(s), map columns, preview, then commit. Don’t lead with an older pick-target-first wizard. There is no source-specific mapper (no Planning Center / PCO / CCLI product path in the importer). There are no in-product “Coming from X” cards. Who can import (web UI): organization owner or admin on the active org. There is no Google Sheets connector. Export the sheet, then upload or paste.

​

Operator checklist

1. Export CSV / XLSX / TSV / TXT from your current tools. A season zip can be dropped as is: Imports unzips it and reads the supported files inside. Avoid PDF / Word as the primary source.
2. Prefer columns that match live wizard targets: Crew, Venues, Clients, Songs, Setlists, Events, Leads, Inventory. Keep extra columns. On Inventory, Venues, and Clients, columns you leave unmapped are saved with each record as extra data. On Crew, Events, Leads, Songs, and Setlists, they are not imported.
3. Open Settings → Data & knowledge → Import & export, drop or paste files, review detected targets, map columns, preview, then commit. Do not rely on an older “pick a target first” wizard as the primary path.
4. After commit: open Gigs, have people accept invitations, spot-check venues / clients / Show Prep. Use product ops / Playbooks for department structure. Do not expect that in the import file.
5. Re-import the same file once (expect 0 new rows).

Import lists before gigs: Crew → Venues → Clients → Songs → Setlists → Events (Inventory and Leads when you need them). Deepened migration guides (export steps, zip layout, traps, screenshot Tips):

​

Watchlist / BYO only

ShowOps.AI and Umbrella (umbrella.live) have no public export schema captured yet (blocked-no-dump). Bring your own season spreadsheet with Soundcheck-native headers; do not invent competitor column tables. Disambiguate ShowOps ≠ showops.co. Season spreadsheet recipe: Importing your season. Pack clear sheets in load order (Crew → Venues → Clients → Songs → Setlists → Events), include a short README with source product and export date, then drop the zip (or the individual CSV / XLSX files) on Settings → Data & knowledge → Import & export. A Soundcheck workspace zip dropped there restores its csv/*.csv files; to commit its UEF JSON instead, use Settings → Data & knowledge → Import & export.

​

Shared import path

1. Sign in as an organization owner or admin and select the org you are loading.
2. Confirm you see Settings → Data & knowledge → Import & export.
3. Prefer the in-app template for the target when you need a known-good column set.
4. Import lists before gigs. Canonical load order in the product is Crew → Venues → Clients → Songs → Setlists → Events (Inventory and Leads when you need them). Each coming-from page lists the practical order for that source.
5. After commit: open Gigs, have people accept invitations, spot-check venues / clients / Show Prep, then re-import the same file once (expect 0 new rows).

One bad row doesn’t block the file: valid rows commit and rows with errors are skipped. Download the error CSV from the results screen, fix those rows, and import them again. See When a row is bad.

​

Mapping traps (every source)

These traps apply across Planning Center, Back On Stage, Master Tour, Stagera, and LASSO / Shoflo. Source pages call out product-specific gotchas and point back here.

• Picker label for roster rows is Crew (internal type MEMBER). Prose may still say crew, roster, or worship team.
• Email is hard-required on Crew today (you cannot Don’t-import it). Dedup is email. There is no member external_id column in the spreadsheet wizard. Phone-only Crew rows fail.
• Email heuristics bind only email, e-mail, email address, not Planning Center Home Email / Work Email / Other Email. Map explicitly.
• Phone heuristics bind phone, phone number, mobile, cell, not Mobile Phone Number.
• Song artist heuristics: artist, performer, band, composer, author, by, so Planning Center Author maps to the artist. Songs dedupe by title + artist, so the same title with an empty artist collapses. A song listed twice in one file shows as a duplicate row in Review. The Songs target has no CCLI column, but it keeps a Song ID column (Song ID, song_external_id), and Setlists can name songs by that ID once Songs are in.
• A header with the word ID in it (Song ID, venue_external_id) maps only to an ID field, never to a title or name. If no ID field fits, it stays unmapped; map it yourself or leave it out.
• Accepted uploads: .xlsx / .csv / .tsv / .txt only. ICS / webcal is rejected (Planning Center Services calendar is webcal; Stagera can emit ICS; both bounce here).
• Eventric only names Dates, Venues, Cities, and Promoters for Tour Details. Do not invent further Tour Details columns. Do not invent LASSO ops CSV dictionaries or ShowOps / Umbrella Program / Signal / Hold tables. Do not promise CCLI numbers, charts, plan order, rundown days[].run_of_show cues via the CSV wizard alone, or Back On Stage booked-roles coming across.

Practice files under docs/sample-imports/ use sample-import headers, not native competitor exports. Operators must map. A native export does not drop in unchanged. Full wizard detail: Operator data imports. Season recipe: Importing your season. Partner / AI shape: Universal Event Format (not the same as spreadsheet mapping).