Import Data (How to Migrate)

Importing Tour Content with CSV

Migrate tour content into Tourient using CSV files and the Importer tool. It's platform-agnostic: if your content can be exported into the column format below, it can be imported — from STQRY, CultureConnect, a spreadsheet, or anywhere else.

You'll import three files, in this order:

1. sponsors.csv — your sponsors

2. tours.csv — each tour (the start page)

3. stops.csv — each stop within a tour

Order matters because tours reference sponsors, and stops reference their parent tour. If you import stops before their tours exist, the links won't resolve and you'll have to fix them by hand.

Download all three CSV templates.

Preparing

• Test with a few rows first. Import one tour and its stops, confirm they look right, then run the full set.

• The templates list the essential fields, but you only need fill in what your source has. Blank columns are skipped.

• Keep titles stable. The import matches entries by Title, so a title that changes between runs is treated as a new entry and creates a duplicate. Settle titles before importing, and change them in the CMS afterward rather than in the CSV. (The slug column still matters for linking stops to tours — see below.)

About slugs

A slug is the short, URL-friendly name that identifies a tour or stop — lowercase, words joined by hyphens, no spaces or punctuation. It's the part of the web address after your domain. Sunnyside Cat Walk → sunnyside-cat-walk → yoursite.tourient.app/sunnyside-cat-walk.

Slugs matter for the import for two reasons:

• They must be unique. No two tours can share a slug; no two stops within the same tour can either.

• They link entries together. A stop names its tour's slug in its parent column; a tour names its sponsors' slugs in its sponsors column. The slug in one row must exactly match the slug in the row it points to.

The import process

You'll run this same process three times, once for sponsors, once for tours, once for stops. Each run has two parts: create the import, then map the fields.

Step 1 — Create the import

1. Log in to the CMS.

2. Go to Tools → Import Data (or visit /cms/utilities/importer).

3. Enter a name, e.g. Migration from STQRY.

4. Upload the CSV file.

5. Set Data type to Entries.

6. Choose the destination collection:

   • sponsors.csv → sponsors

   • tours.csv → tours

   • stops.csv → tours

7. Choose the Blueprint (see the reference table below).

8. Choose the site / language to import into.

9. Under Import Strategy, select Create New Items (unless you're bulk-updating a specific field).

10. Click Save and continue.

Step 2 — Map the columns

1. Next, you'll see a Configuration section. Here, every available field in either a tour or stop appears, and you can map the columns from your CSV to those fields. You may notice fields that aren't in the CSV template. If you have data for those, you can add them, or add them later.

2. Most columns map straight across. Some need extra settings (below). When finished, click Save & Run, and the migrated tours will appear in the Tours listing.

Blueprint & template — fill with the same value on every row:

Link columns (parent, sponsors) — point to other entries. You put a slug in the cell, and the importer finds the entry with that slug and links it.

• Set Related Field to slug.

• Leave Create when missing? off so broken links show as errors instead of empty entries.

Example — a stop that belongs to the Sunnyside Cat Walk tour has this in its parent cell:

sunnyside-cat-walk

Example — a tour sponsored by both Acme Co. and the City Museum has this in its sponsors cell, pipe-separated:

acme-co|city-museum

Each slug must exactly match the slug of a row you already imported (a tour row for parent, sponsor rows for sponsors).

Asset columns (featured_images, featured_image, audio_file, logo, offer_image) — images and files. You put the file's full URL in the cell, and the importer downloads it for you.

• Related Field: URL

• Base URL: the common root your file URLs share, so the importer can tell new files from ones already imported

• Download when missing?: on (fetches each file into the asset container)

• Folder: where downloaded files land (defaults to mirroring the URL path)

Example — a stop with three photos has this in its featured_images cell, pipe-separated:

https://cdn.mysite.com/stops/town-hall-01.jpg|https://cdn.mysite.com/stops/town-hall-02.jpg|https://cdn.mysite.com/stops/town-hall-03.jpg

For those URLs, the Base URL would be the shared root:

https://cdn.mysite.com/stops/

Example — a stop's audio file has this in its audio_file cell (one file, so no pipe):

https://cdn.mysite.com/audio/town-hall.mp3

Accepted values for Tours

Several tour columns only accept specific values. Put the value on the left in the CSV cell, not the label. .

tour_type

tour_method — the default transit method (only applies to GPS tours)

wayfinding_method

Unique Field

Use Title as the Unique Field. For this to work, tour and stop titles must be unique — no two tours sharing a title, and no two stops within the same tour.

Matching on Title is what makes re-running safe: fix a few rows, run again, and it updates those entries instead of creating duplicates. If you edit a title between runs, the importer sees a new entry and creates a duplicate — so settle titles before importing.

Step 4 — Run it

Run the import. Check the results before moving to the next file.

A note on body text

The imported_content column holds a stop’s text content. On import it goes into a single Imported Content field below the blocks area. It's imported as-is, so you can reformat, split it into more blocks, or add media blocks afterward.

Languages

Import one language only — your primary language. Once the content is in, use Tourient’s translation tools to add other languages. There’s no need to prepare translated CSVs or run the import more than once.

Limitations

• Captions and credits aren't imported. featured_images brings in the files and possibly alt text; per-image captions or credit lines must be added by hand afterward.

• Repeating / structured fields can't come through CSV — sponsor tiers, related links, tour groups, and richer blocks (quizzes, embeds, galleries with settings). CSV covers the core content; the rest is set up in the CMS afterward.

• Large image sets are slow. Hundreds of images and dozens of audio files take a while.

• Audio must be MP3 or M4A, up to 10 MB per file.

• Some fields generate automatically and don't need importing (stop counts, tour distance/duration).

Tips

• Pipe ( | ) separates multiple values in any cell (images, multiple sponsors).

• Leave a field blank to skip it — the importer won't overwrite an existing value with an empty cell unless configured to.

• Re-running with the same title updates existing entries instead of duplicating them.