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

# Switching to Run of Show from another tool

> Move your run of show to Soundcheck from Shoflo, Rundown Studio, Cuez, Stagetimer, Google Sheets, Excel, Word or PDF run sheets, and your songs from BandHelper or OnSong. What the AI import reads, what moves over, what has no equivalent, and a migration checklist.

Most teams arrive with years of rundowns in another tool or in spreadsheets. You don't have to retype them. This page shows how to bring each kind over, what comes with it, and what you'll have to set up by hand because Soundcheck has no equivalent.

![Paste into Run of show dialog with a file upload and a box to paste a schedule](https://mintcdn.com/soundchecklive/DQsOfwUk5leizXB5/images/run-of-show/paste-data-light.png?fit=max\&auto=format\&n=DQsOfwUk5leizXB5\&q=85\&s=72b1215eadbcb1e6a32697890a47d90e)

## The short version

| You're coming from | Fastest way in | What to expect |
| - | - | - |
| **Shoflo** (LASSO) | Export the rundown to CSV, then **Upload a timeline** in **Paste data** | Titles, start and end times and notes come over. Department columns and cue numbers don't have their own fields. |
| **Rundown Studio** | Export to CSV or Excel, then **Upload a timeline** | Same as Shoflo. |
| **Cuez** | Export or print the rundown to PDF, or copy the rows as text, then **Paste data** | Same as Shoflo. |
| **Stagetimer** | Keep it for your stage timer. Build the run of show in Soundcheck. | Soundcheck has no stage or speaker timer. |
| **Google Sheets** | Copy the block and paste it into the grid, or download as .xlsx or .csv and upload | The quickest route when your columns are already start, end, length, what. |
| **Excel** | Upload the .xlsx | Only the first sheet is read. |
| **Word or PDF run sheets** | Upload the .docx or PDF | The text is read and turned into rows for you to review. |
| **BandHelper or OnSong** (songs) | Get your song list into a spreadsheet, then import **Songs** | Title, artist, length, key, tempo and notes come over. |

There's no direct connection to any of these tools. Everything comes in as a file or as pasted text.

## The AI import: Paste data

**Paste data** reads a schedule in almost any shape, from an emailed run sheet to a 200-row production spreadsheet, and turns it into rows you review before anything is added.

**1. Open it**

Open the gig's **Run of Show** tab, switch to **List**, and choose **Paste data** above the grid. The **Paste into Run of show** dialog opens.

**2. Add your rundown**

Paste the text into the box, or choose a file under **Upload a timeline**. A file's text lands in the box first, so you can delete a cover page or someone else's schedule before going on.

**3. Map it**

Choose **Map into Run of show**. An AI model reads the text and proposes rows.

**4. Review the rows**

Tick the rows you want and untick the rest. Values the AI isn't sure about arrive unticked, so look at those first.

**5. Fill**

Choose the **Fill** button. The rows are added and autosave, with **Undo** available.

You need to be able to edit the gig's run of show to use it. See [Importing a schedule](https://docs.soundchecklive.io/features/gigs/run-of-show/importing.md) for the full detail.

### Files it reads

| Format | Extensions | Notes |
| - | - | - |
| PDF | `.pdf` | The text in the PDF is read. If a PDF comes through empty, it's probably a scan: copy the text out and paste it instead. |
| Word | `.docx` | Older `.doc` files aren't accepted. Save as `.docx` first. |
| Excel | `.xlsx` | **Only the first sheet** is read, up to 5,000 rows and 64 columns. Older `.xls` files aren't accepted. |
| CSV and TSV | `.csv`, `.tsv` | Read as text rows. |
| Text | `.txt` | Read as is. |

* **Size limit: 8 MB per file.** A spreadsheet or Word file also has to stay under 16 MB once it's opened.
* **Very long files are cut off** after about 128,000 characters of text. Split a long multi-day rundown and import one day at a time.

### What each row carries

Each row the AI proposes has four things: a **name**, a **start time**, an optional **end time**, and **notes**. Times are read against the gig's date.

Anything else in your source, such as an Audio column, a cue number or a Private Notes column, either lands in the row's notes or is left out. Check the review before you choose **Fill**. After that, the rows are ordinary items: move them into sections, link them, add people and mark key times. See [Building and editing](https://docs.soundchecklive.io/features/gigs/run-of-show/building.md).

> [!NOTE]
>
> Imports only add rows. They never delete or overwrite what's already in the run of show.

### Pasting cells straight into the grid

If your spreadsheet's columns are already in the grid's order (start time, then what), you don't need the AI at all. Add as many empty rows as you need, copy the block in Google Sheets or Excel, select the first **Time** cell in the grid, and paste. Times like `6:42p` are read the same as typed values. See [Pasting, filling and copying cells](https://docs.soundchecklive.io/features/gigs/run-of-show/building.md#pasting-filling-and-copying-cells).

### Key times from a call sheet

For the handful of times everyone works to (crew call, load in, doors, curfew), use **Paste key times** next to **Paste data**. Names that match your key time list set those key times. See [Pasting key times](https://docs.soundchecklive.io/features/gigs/run-of-show/importing.md#pasting-key-times).

## Coming from each tool

### Shoflo

**1. Export**

In Shoflo, open the rundown and export it to CSV from its **⋯** menu. Prefer CSV over PDF or Word.

**2. Tidy it**

Delete empty rows. Shoflo's default columns are `NUMBER, Items, Start, Duration, Prod Notes, Audio, Video, Lighting, Private Notes`.

**3. Import**

In Soundcheck, open the gig, choose **Paste data**, and upload the CSV under **Upload a timeline**. Review and **Fill**.

**4. Rebuild what has no field**

Put the cue number at the front of each title (*LX 14 · Walk-in*). Move department text into **Notes**, one line per department, if the import didn't. Leave Private Notes out if your crew shouldn't see them, because everyone on the gig can read a row's notes.

Moving a whole LASSO account (crew, venues, clients, events)? See [Coming from LASSO / Shoflo](https://docs.soundchecklive.io/features/imports/coming-from-lasso.md).

### Rundown Studio

Export the rundown to CSV or Excel. Upload it under **Upload a timeline** in **Paste data**. Custom columns come over the same way as Shoflo's department columns: into notes or not at all. Rundown Studio's live timers, show-caller mode and output screens have no equivalent in Soundcheck. See [Run of Show on show day](https://docs.soundchecklive.io/features/gigs/run-of-show/show-day.md#what-show-callers-expect-and-what-to-do-instead).

### Cuez

If you can export a file, upload it. If not, print the rundown to PDF and upload that, or select the rows, copy them, and paste them into **Paste data**. Scripts, the Automator and MOS connections to graphics and playout have no equivalent in Soundcheck.

### Stagetimer

Stagetimer is a timer, not a run of show, and Soundcheck doesn't replace it. Soundcheck has no stage, confidence-monitor or speaker timer. Most teams build the run of show in Soundcheck and keep Stagetimer on the confidence monitor, typing the segment lengths from the run of show into it.

### Google Sheets

Two routes:

* **Columns already line up:** copy and paste the block into the grid, as above.
* **Any other layout:** choose **File → Download** in Sheets, pick **Microsoft Excel (.xlsx)** or **Comma-separated values (.csv)**, and upload it in **Paste data**. Put the schedule on the first tab first. You can also select the cells, copy them, and paste the text straight into the **Paste data** box.

### Excel

Upload the `.xlsx` in **Paste data**. Move the schedule to the **first sheet** before you upload. A workbook with one sheet per day needs one import per day: save each day as its own file, or copy each day's rows into the box.

### Word or PDF run sheets

Upload the `.docx` or `.pdf`. The text lands in the box, so delete headers, contact blocks and anything that isn't the schedule before you choose **Map into Run of show**. A planner's timeline that a client sends you through the client portal comes in the same way, with **Review** on the notice. See [Timelines from clients](https://docs.soundchecklive.io/features/gigs/run-of-show/importing.md#timelines-from-clients).

### BandHelper or OnSong (songs and setlists)

Songs live in one library that every setlist and run of show uses.

**1. Get your songs into a spreadsheet**

Export your song list from BandHelper or OnSong to a spreadsheet or CSV, if your plan allows it. Keep one row per song.

**2. Import songs**

Go to **Settings → Apps & data → Import & export**, drop the file, and pick the **Songs** target. **Song Title** is required. Artist, length (`HH:MM:SS` or seconds), key, tempo (1 to 999) and notes come over. An **Acts** column tags songs to acts.

**3. Import setlists, if you have them**

Import **Setlists** after **Songs**. Rows that share a setlist title become one setlist, with its sets in order.

**4. Or paste one set at a time**

In a gig's **Setlist** view, choose **Paste data** and paste a set list, one song per line. Titles already in your library are matched. New titles are marked **New** and added to the library.

Charts, lyric sheets and audio don't come over in a spreadsheet. Attach them to each song afterwards. See [Adding songs in bulk](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/importing-songs.md).

## Templates: bring your standard shows once

Your standard show shapes matter more than any one past show.

* **One at a time:** import the rundown into a gig, clean it up, then choose **Save as Template** in the Run of Show section's **⋯** menu. See [Templates](https://docs.soundchecklive.io/features/gigs/run-of-show/templates.md).
* **Many at once:** run of show templates can be bulk-imported as a Soundcheck import document under **Settings → Apps & data → Import & export**. See **Run of show templates** in the [import format reference](https://docs.soundchecklive.io/features/imports/import-format-reference.md).
* **Starting fresh:** the 22 starter templates (wedding, general session, festival stage, awards show and more) may be closer to your show than your old file.

## What moves over, and what has no equivalent

| In your old tool | In Soundcheck |
| - | - |
| Rows with titles and times | Rows (items), with start, end and length. |
| Segments, blocks | Sections, which fold away and can sit on a stage and a track. |
| Durations that roll forward | Rows without their own time follow the row before. **Segue into next** chains them. |
| Hard start times | A row's own start time, with **Timing** set to **Clock**. |
| Notes, producer notes | **Notes**. |
| Speaker on a row | **Speaker**, with a role and minutes. |
| Playback source | **Playback**: **Live**, **Track**, **DS iPad** or **Other**. |
| Files on a row | Row files in **Details…**. Gig-wide files go on the **Documents** tab. |
| Client view | The [guest live page](https://docs.soundchecklive.io/features/gigs/live-page.md) (early access), a PDF with **No Surprises**, or the client portal's **Your schedule**. |
| Song library and setlists | The [song library](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/song-library.md) and saved setlists, with key and tempo. |
| Templates | [Templates](https://docs.soundchecklive.io/features/gigs/run-of-show/templates.md), plus 22 starters. |
| **Custom columns** (Audio, Lighting, Video, Graphics) | **No equivalent.** Use one line per department in **Notes**, and people with a **Department** and **Task note**. |
| **Cue numbers** | **No equivalent.** Put the number at the start of the title. |
| **Back timing, over/under** | **No equivalent.** Shift times when the show runs late. |
| **GO button, standby, show-caller mode** | **No equivalent.** See [show day](https://docs.soundchecklive.io/features/gigs/run-of-show/show-day.md). |
| **Stage, speaker or confidence-monitor timers** | **No equivalent.** Keep a stage timer such as Stagetimer. |
| **Real-time co-editing with live cursors** | **No equivalent.** Autosave merges edits; see [Publishing and collaboration](https://docs.soundchecklive.io/features/gigs/run-of-show/publishing-and-collaboration.md). |
| **Version history and restore** | **No equivalent** beyond the last published version. |
| **Comments on a row** | **No equivalent.** |
| **Private columns per company** | **No equivalent.** Every editor and crew member on the gig reads the same notes. |
| **Teleprompter, MOS, show-control triggers** (QLab, OSC, MIDI, Companion) | **No equivalent.** |
| **Calendar sync of cue times** | **No equivalent.** |
| **Offline editing** | **No equivalent.** The app reads offline. |

## What you get that a rundown tool doesn't have

The run of show lives inside the gig, next to the people, money and paperwork:

* People on a row get a checklist task at that time, and see their call in **Your times** on their phone.
* Key times such as Doors and Curfew come from the rows, and show across the gig.
* Setlists sit in the night as rows, with set lengths added up from the songs.
* Music requests and do-not-play warnings check the sets for you.
* Day sheets, music schedules and advance packets come from the same run of show.

## Migration checklist

**1. Pick three shows**

Pick one typical show, one big show and one multi-day show. Import those first, not your whole archive.

**2. Import each into a test gig**

Use **Paste data** with the export or file. Note which columns didn't come over.

**3. Agree your conventions**

Decide how your team writes cue numbers in titles, which departments get a line in **Notes**, and which [tracks](https://docs.soundchecklive.io/features/gigs/run-of-show/schedule-view.md) you use.

**4. Turn the best one into a template**

Clean it up and choose **Save as Template**. If every new gig should start from it, choose **Make default for new gigs** in its **⋯** menu on the templates page.

**5. Bring your songs**

Import **Songs**, then **Setlists**, from a spreadsheet. Spot-check keys and lengths.

**6. Set your key times**

Check the key time list in **Settings → Labels → Gigs → Key times** matches the words on your call sheets, so **Paste key times** matches them.

**7. Decide on publishing**

Choose whether crew see edits as they save or only after **Publish**. See [Publishing and collaboration](https://docs.soundchecklive.io/features/gigs/run-of-show/publishing-and-collaboration.md).

**8. Keep your stage timer**

If you use a confidence-monitor or speaker timer, keep it.

**9. Run one real show side by side**

Run your next show from Soundcheck with the old tool open as a backup. Print a PDF backup too.

**10. Bring the rest as you need it**

Past shows only need importing when you'll run them again.

Want help moving over? Email [info@soundchecklive.io](mailto:info@soundchecklive.io).

## Worked example: an AV company leaving Shoflo

A corporate AV company runs about 40 general sessions a year in Shoflo, with Audio, Video and Lighting columns and cue numbers.

1. They export last year's flagship general session from Shoflo to CSV.
2. In a test gig, they choose **Paste data**, upload the CSV, and choose **Map into Run of show**. 62 rows come back with names and start times. They untick three empty header rows and choose **Fill**.
3. The Audio, Video and Lighting columns came through as notes on some rows and not on others, so they settle on one convention: *SQ:*, *VX:* and *LX:* lines in **Notes**, and cue numbers at the front of titles (*VX 3 · Opener video*).
4. They group the rows into sections (*Walk-in*, *Opening*, *Keynote*, *Awards*, *Walk-out*), put the A1, V1 and LD on their cues with a **Department** and a **Task note**, and choose **Save as Template**.
5. They keep Stagetimer for the confidence monitor, because Soundcheck has no speaker timer.
6. Every new general session now starts from that template, and crew get their calls and cues on their phones.

## Questions this page answers

* [Can I import from Shoflo, Rundown Studio or Cuez?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Which file types and sizes can I upload?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Do my custom columns and cue numbers come over?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Can I paste straight from Google Sheets or Excel?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Can I import my song library from BandHelper or OnSong?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Does Soundcheck replace my stage timer?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [How long does it take to move over?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)

## Related

> [card] [Importing a schedule](https://docs.soundchecklive.io/features/gigs/run-of-show/importing.md)
>
> Paste data, key times, set lists and client timelines.

> [card] [Adding songs in bulk](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/importing-songs.md)
>
> Spreadsheets, Spotify and starter packs.

> [card] [Templates](https://docs.soundchecklive.io/features/gigs/run-of-show/templates.md)
>
> Save your standard shows once.

> [card] [Run of Show on show day](https://docs.soundchecklive.io/features/gigs/run-of-show/show-day.md)
>
> What's different from a show-calling tool.

> [card] [Coming from another system](https://docs.soundchecklive.io/features/imports/coming-from.md)
>
> Moving crew, venues, clients and events.

> [card] [Glossary](https://docs.soundchecklive.io/features/gigs/run-of-show/glossary.md)
>
> Rundown terms and their Soundcheck names.


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