Skip to main content
LASSO (lasso.io, live-events ops) and Shoflo (rundown / ROS; acquired into the LASSO family) operators move data by exporting CSV / XLS / PDF (or assembling sheets via Zapier / swagger dumps), then importing through Settings → Data & knowledge → Import & export. Legacy .xls exports are not supported. Save as .xlsx or .csv before upload. There is no LASSO or Shoflo connector. Files only. Disambiguate: this is lasso.io, not lassocrm.com. 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 LASSO” cards. There is no Organized / Processing / Queued UI to watch. Who can import (web UI): organization owner or admin on the active org. Prefer in-app target templates when you need a known-good column set. Shared mapping traps (email hard-required on Crew, upload types, ICS rejected): Coming from another system.
Walkthrough video is TBD. Until it ships, follow the export steps and screenshot Tips below.

​
What you can bring over

Honest ops caveat: there is no published fixed CSV column dictionary for LASSO crew / gear / invoice exports. Always read the customer header row. Field names below come from Zapier action inputs and a Workforce swagger (~2021, third-party Dart package), plus live Shoflo Default Rundown CSV headers. Do not invent LASSO CSV columns in Frames.

​
LASSO ops export steps

  1. Use in-product CSV / XLS / PDF export where the UI offers it. Capture the real header row from your dump. If the export is legacy .xls, save/convert it to .xlsx or .csv before uploading to Soundcheck.
  2. Optional: Settings → Integrations → API key (LASSO-APIKEY, https://{company}.lasso.io/api/v1). A customer may dump JSON; Soundcheck still wants files.
  3. Optional BYO via Zapier (Create / Find Event, Crew, Venue, Client, Schedule Entry, Product, Equipment Order) when native CSV is opaque:
  4. Bulk order CSV (Zapier): the only confirmed header pair is product_code,quantity.
  5. Upload resulting CSVs to Settings → Data & knowledge → Import & export.
Zapier and swagger are field sources / BYO aids, not Soundcheck connectors.
Screenshot placeholder: LASSO Zapier integration page. Caption: field source / BYO, not a Soundcheck connector. Do not invent CSV columns in the Frame.

​
High-signal LASSO field maps (Zapier / API names)

Events: Event Name / name → title; Begin Date / date_begin → event_date; End Date / date_end → event_end_date when offered; Event Code / External Code → external_id (prefer external_code); Description → notes; Venue / Client names and codes → Venues / Clients. Account Manager, Division, Market, Program, logistics date windows → keep in the source sheet or leave unmapped. Crew: First / Last / Email / Phone → Crew invite fields. External Code / external_code / code / id → provenance / future external_id. Classification, legal names, rates, travel, passport, shirt, payroll, ratings → leave unmapped. Do not publish passport / immigration detail in guides. Venues / Clients: Venue Name + Street / Locality / Region / Postal / Country / Phone / External Code → Venues address graph. Client Name / External Code / Phone / URL → Clients. Airport / Market / room dimensions → leave unmapped. Schedule / Position: ScheduleEntry Date + Start / End Time + Type → run-of-show cue name (Type or Position label) + start / end times when supported. Hours worked / billed, quantity needed, rates, roster status → leave unmapped. Do not promote Position labor graph as a first-class UEF entity from marketing alone. Inventory / order lines: Map to live Inventory spreadsheet targets when the wizard offers them:
  • External ID → external_id (stable identity; match order: importer matches external_id first, then matches by name instead)
  • Name → inventory name (required)
  • Category → category (when offered)
  • Quantity → quantity / stock (when offered)
  • Condition → condition (when offered)
  • Location → location (when offered)
  • Status → status (when offered)
  • Replacement cost → replacement cost (when offered)
  • Notes → notes (when offered)
Prefer mapping LASSO / Zapier product_code (or External Code) → External ID so re-imports update instead of duplicating. Height / width / depth / weight, rental_rate_day, warehouse, insured value, and other commercial rates stay unmapped unless a live target appears (do not invent daily_rate, physical-dim, or serial Inventory fields). Order line product_code,quantity is the only confirmed Zapier bulk-order header pair (closest published shape to pack lines: map product_code → inventory External ID / ref, quantity → quantity when pack lines are supported). Do not invent a source alias named pack_items. Unknown columns → leave unmapped, or keep them in your source sheet for reference. Prefer provenance notes in a README over inventing wizard fields.

​
Shoflo rundown CSV (detailed)

  1. Open a rundown → ⋯ → Export → CSV (also PDF / Word; prefer CSV).
  2. Filename pattern: <rundown-name>-<YYYY-MM-DD>.csv.
  3. Columns mirror on-screen names (Columns button = user-configurable). Default “Shoflo Template” headers (captured live):
  1. Help: How to export / download / print rundowns · Columns
  2. Map rundown rows → event run-of-show cues (days[].run_of_show, not a standalone Songs path).
Empty rundown rows can export; clean them before upload. PDF / Word / Guest Pass → defer.
Screenshot placeholder: Shoflo rundown ⋯ → Export → CSV with Default Rundown columns visible. Caption as Shoflo product UI.
Zip the season folder and drop the .zip on Settings → Data & knowledge → Import & export, or drop the files one by one. Imports unzips it in your browser and reads the .xlsx / .csv / .tsv / .txt files, documents, and photos inside, including files in subfolders. Anything else in the zip is left out, and you are told which files were skipped.
Drop the individual files on Settings → Data & knowledge → Import & export. Load order: Crew → Venues → Clients → Songs → Setlists → Events (add Inventory before Events when you have product sheets; Songs / Setlists usually N/A; attach Shoflo rundown as schedule on Events).

​
LASSO / Shoflo-specific mapping notes

  • Always read the customer header row for LASSO ops CSVs. There is no fixed public dictionary.
  • Workforce swagger is ~2021 and missing Inventory / Equipment Order; Zapier may be newer.
  • Shoflo headers vary by template. Default Rundown is one evidence point.
  • Songs / CCLI path does not exist in LASSO.
  • Do not invent Quote / Invoice line columns.
  • Do not invent Department / Workflow / Phase / Series / Work Item.
  • Inventory commercial extras (dims / rates / serial / free-form metadata) stay unmapped in the wizard.
Screenshot placeholder: Soundcheck Imports map step with Shoflo Items / Start / Duration → schedule fields, or LASSO External Code → external_id when offered. Inventory map shows Name / Category / Quantity / Condition / Location only. Drop-first empty state.
Full shared traps: Coming from another system.

​
Import order

  1. Crew
  2. Venues / Clients
  3. Inventory (products) when you have them
  4. Events (attach Shoflo rundown as run-of-show cues when supported)
Canonical product order: Crew → Venues → Clients → Songs → Setlists → Events (Inventory and Leads when you need them).

​
Import path

  1. Open Settings → Data & knowledge → Import & export. 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 your LASSO header shape (and Shoflo template) is mapped.
  3. After commit: open Gigs, ask people to accept invitations, spot-check venues / clients, re-import once (expect 0 new rows).
No Google Sheets connector. No MCP connect URL in this guide. No native LASSO / Shoflo connector. 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. Full wizard: Operator data imports. Season recipe: Importing your season.

Coming from another system

Hub for Planning Center, Back On Stage, Master Tour, Stagera, and LASSO / Shoflo

Operator data imports

Imports wizard, targets, and permissions