Import events from a CSV file

Import events into Eventually from a CSV file, or export your current events, edit them in a spreadsheet, and re-import the file to update those events in place. The import tool accepts CSV exports from Squarespace, Shopify, and Eventbrite, or the Eventually template for custom data and bulk edits.

You can also import informational, calendar-only events that do not require registration by setting the disable_registration column to a truthy value.

Export events for bulk editing

On the Events page, use Export CSV to download events in the same 25-column format as the Eventually import template. Every exported row includes the event id, so re-importing the file updates those events instead of creating duplicates.

1. Open Events in the left sidebar.

2. Optional: switch the list tab, search, category filter, or open a series so the list shows only the events you want to edit.

3. Click Export CSV in the Events toolbar, to the left of Import Events and New event.

4. Choose the current-scope option or All events.

5. Edit the downloaded spreadsheet, then re-import it with Import Events.

The current-scope menu label matches the list you are viewing:

• Upcoming only

• Drafts only

• Completed only

• Series only on the series tab

• These occurrences when you are inside a series

Current-scope exports keep the active list filter, search, category, and series scope. All events ignores those list scopes and exports every non-discarded event for the site, including drafts, completed events, past events, and series occurrences. Discarded events are not included.

Access the import tool

From your dashboard, open Events in the left sidebar, then click Import Events next to New event.

Prepare your CSV file

In the import modal, download the Eventually CSV template, upload a file you exported with Export CSV, or upload a CSV export from Squarespace, Shopify, or Eventbrite.

Click Download Eventually CSV template to get the template with these columns:

The more_info_url and more_info_button_text values are copied to recurring event instances and preserved during import without changing the registration type.

Create or update with the id column

Eventually-format rows use the id column to decide whether to create or update:

• Blank id: create a new event.

• Matching id for an event on the site: update that event in place.

• Unknown id: the row fails with an Event ID … not found error and does not create a new event.

Exported rows always include id. Keep those values when bulk-editing existing events. Start from the template, or clear id, only when you intend to create new events.

When you re-import an Eventually CSV for an existing event, ticket tiers are matched by name and updated in place instead of being deleted and recreated. Exact tier names are matched first; a name that differs only in casing or spacing can still update the matching tier. A matched tier keeps its tier-specific settings, such as access codes, sale windows, per-order limits, default status, and position, while CSV-controlled values like name, price, and capacity are updated. New tiers in the file are created, and tiers removed from the file are dropped. Because matching is name-based, changing a tier's name can leave the old tier unmatched and create a new one. If a tier cannot be applied — for example a duplicate or ambiguous name, a rejected value, or a tier that could not be removed — the Import Complete view lists a tier-level message for it, showing up to the first 50 messages.

Categories, tags, cost, and time zones

These columns have specific create and update rules during Eventually-format import.

• Categories on update: A non-blank categories cell replaces the event’s categories. Categories listed in the cell are kept or added; categories omitted from the cell are removed. A blank categories cell leaves existing categories unchanged.

• Categories on create: A blank categories cell creates the event with no categories.

• Tags: The tags column works on create and update. Non-blank values assign those tag names. A blank tags cell leaves existing tags unchanged and does not clear them.

• Cost: Exports leave cost blank when ticket_types is present. On create, the importer reads cost only when ticket_types is blank, so leave cost empty if the row already defines ticket types.

• Time zones: Imports accept timezone names and near-miss spellings with spaces, such as America/Los Angeles, and normalize them so buyer-facing event times use the event timezone instead of the viewer’s clock. Exported start_at and end_at values use the event’s own timezone wall-clock time, not UTC. For how event times display after import, see Date, time, timezone, and location autocomplete.

• Delimited values: Exported categories, tags, ticket_types, and registration_questions values that contain commas or other sub-delimiters are escaped so a round trip does not split them incorrectly. Prefer editing an export when those fields contain special characters.

Registration question ticket-type scope

The registration_questions column supports an optional fifth segment that scopes a question to specific ticket types. The full format is Label:field_type:options:required:scope, where scope is a comma-separated list of ticket-type names. A question with no fifth segment — or an empty one — is asked on all tickets, so files created before this feature import exactly as before.

Exports write ticket-type names, not IDs, so a file can round-trip across sites where ticket-type IDs differ. For example, a question scoped to the Early Bird ticket exports as Team Name:text::true:Early Bird.

On import, each name in the scope is matched exactly against the event's current ticket types. If none of the names match, the question is skipped and reported as Question 'Label' skipped — none of its ticket types exist on this event. If only some names match, the question is kept on the matching types and the unmatched names are reported as Question 'Label': ticket type 'Name' not found — kept on its remaining types. Renaming a ticket type between export and import breaks the name match, so the question is reported rather than silently widened to all tickets.

The field_type segment accepts the ten registration question types: text, long_text, email, phone, number, date, dropdown, multi_select, yes_no, and checkbox. List types — dropdown (Single select) and multi_select — read their choices from the options segment, so imported date, email, phone, number, and multi-select questions keep their type instead of being converted to text.

Status, location type, and guest experience tier

These Eventually-format columns only apply a value when the cell matches an accepted option. Blank cells stay quiet and do not change an existing event.

• Status accepted values: draft, published, cancelled, completed.

• Location type accepted values: in_person, virtual, hybrid.

• Guest experience tier accepted values: simple, engaged, high_touch.

On create, an unrecognized or blank status creates the event as draft; an unrecognized or blank location_type uses in_person; an unrecognized or blank guest_experience_tier uses engaged.

On update, an unrecognized or blank value in any of these columns leaves the event’s current setting unchanged. An invalid status does not move a published event to draft or take it off sale. Keep the exported status when bulk-editing live events, and use a recognized value only when you intend to change it.

Unrecognized values and advisories

For Eventually-format CSV files, the preview can show a blue advisory when a non-blank timezone, status, location_type, or guest_experience_tier value is not recognized. Advisory rows still import; they are not the same as skipped-row warnings.

• Skipped rows: The preview lists rows that will not import, with a count such as “N rows will be skipped.”

• Advisory rows: The preview lists rows that will import with an unrecognized value, with a count such as “N rows will import with a value we didn’t recognize.”

• Blank cells: Empty cells in those columns do not produce an advisory.

• Repaired time zones: Near-miss timezone spellings the importer can normalize, such as America/Los Angeles, do not produce an advisory.

When a timezone is unrecognized:

• New events fall back to a timezone detected from the address when possible, otherwise your team default. That fallback can shift start times.

• Updates to existing events keep the event’s saved timezone, so a timezone change you meant to make does not apply until the CSV value is fixed.

After import, the completion summary reports how many rows imported with an unrecognized value, lists affected rows, and notes the fallback timezone used for new events. Failed rows remain a separate list from advisories. Fix the source CSV when an advisory appears rather than assuming the typed value was applied.

CSV exports from Squarespace, Shopify, and Eventbrite do not include these Eventually-format advisory checks for timezone, status, location type, or guest experience tier.

Upload and import

1. In the import modal, click Click to choose a CSV file or drag and drop your CSV file.

2. The file size limit is 5 MB for CSV uploads.

3. Click Preview to review how your rows will be imported.

4. Review the preview. Check skipped-row warnings, blue advisories for unrecognized values that still import, and the interpreted start times shown for each row.

5. Confirm the import to create new events and apply updates.

Preview dates and times use the same interpretation the import will write, including your account’s date-format preference for ambiguous slash dates such as 12/01/2026. If a date or time cannot be read, the preview shows the raw cell value instead of inventing a time, and that row is treated as a problem to fix before import.

After importing

Review the results on the Events page:

• Open each new or updated event to add images, fine-tune descriptions, or adjust attendee registration fields.

• Assign or review categories for calendar filtering.

• Review tags used for internal organization.

• Configure recurring schedules for classes or workshops.

• Set up automated emails for confirmations and reminders.

Troubleshooting

Related guides

• Edit an event — Update event details after importing

• Customize event categories — Organize events into filterable groups

• Manage tags for your events — Rename, merge, and organize internal tags

• Creating recurring events — Set up repeating schedules