---
title: "Migrate from Luma"
description: "Move your events, ticket types, questions and guests from Luma to your Sherpo store, with a script, with your AI, or by hand, and send your audience to their new pages."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.sherpo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Luma

Your events on Luma become [event](/overview/categories#event) products on your Sherpo store: the same times and places, the same ticket types, the same questions, and every guest already going, who keeps their place. Sherpo takes no share of your ticket sales ([Payments and payouts](/overview/payments)), and an event on Sherpo can sell more than tickets: a recording, slides and notes in its [entries](/overview/categories#entries-and-timed-release), a membership, or a course beside it.

## What moves

| Moves | Stays on Luma |
| --- | --- |
| Events: title, description, time, time zone, place, map pin, capacity, waitlist and approval | Check-ins of events already held |
| Ticket types, their prices and capacity | Luma's ticket codes and QR codes: Sherpo issues its own |
| Registration questions and each guest's answers | Payments and payouts, which stay with the Stripe account Luma paid into |
| Guests going, with what they paid and when they registered | Guests Luma hasn't approved, until you decide them |
| | Coupons, the cover image and the join link, which you add again |
| | Calendar subscribers, newsletters, feedback and event chat |

## Before you start

1. **Your store**, on a [plan](/overview/plans) that holds your guests: every guest you import becomes a customer of your store.
2. **Payouts**, if you'll sell paid tickets on Sherpo: connect your Stripe account in the merchant app ([Payments and payouts](/overview/payments)).
3. **What you'll read from Luma**: an API key for each calendar, which needs Luma Plus, or, on any plan, each event's guest list exported as a CSV from its Guests tab.

Your Luma calendar maps to your store. Each event becomes a product, listed on your store's pages like any other once you publish it.

## Choose how to move

- **With a script**, through the merchant API: [Import from Luma](/merchant-api/guides/import-from-luma) reads Luma's API, or a guest CSV, and recreates each event with its ticket types, questions and guests, as often as you run it. It suits many events, or a developer at hand.
- **With your AI**, through the merchant MCP server: [below](#with-your-ai).
- **By hand**, in the merchant app: create the event, its sessions and ticket types ([Products](/merchant-app/products)), then give each guest their ticket by email with **Grant access** ([Access](/merchant-app/pricing-and-access#access)). A ticket you grant takes no seat, so lower the event's capacity by the guests you add. It suits a handful of events with a few guests each.

Rehearse on one event before the rest, and keep each new event a draft until you've checked it.

### With your AI

Connect the [merchant MCP server](/merchant-mcp/connect) to your AI client, and Luma's own MCP server too, which reads your events on any Luma plan. Then ask for the move, one event at a time:

> Move my Luma event "Launch night" to my Sherpo store as a draft event: same time, time zone and place, a tier and a one-time price for each ticket type, and its registration questions. Then record an order for each guest who's going, by their email, for the tickets and amount they paid, dated when they registered, and set their answers.

Your AI does what the script does, through the tools: [`create_product`](/merchant-mcp/tools/create_product), [`create_event_session`](/merchant-mcp/tools/create_event_session), [`create_tier`](/merchant-mcp/tools/create_tier), [`create_price`](/merchant-mcp/tools/create_price), [`create_product_question`](/merchant-mcp/tools/create_product_question), [`record_order`](/merchant-mcp/tools/record_order) and [`set_customer_answers`](/merchant-mcp/tools/set_customer_answers). Check its work with [`list_event_attendees`](/merchant-mcp/tools/list_event_attendees), whose count should match the guests going on Luma.

## What your guests get

Each imported guest holds a ticket to the event, recorded as an order of what they paid on Luma, and counts against its capacity. Someone new to your store is invited by their email and finds the event in their library when they first sign in with that address, with their ticket's QR code for the door. Recording an order moves no money: nothing is charged again, and nothing is refunded.

For an event still ahead, each guest gets the registration email when they're imported, with their ticket code and a calendar file, and then the reminders before each session as browser notifications. To import without a word, turn the registration email off for that event alone in [Customer messages](/merchant-app/settings#customer-messages) first, and tell your guests yourself where their ticket moved. Your automations run on each order as on a sale, so pause any that shouldn't.

## Online and hybrid events

There is no streaming of Sherpo's own, nor on Luma: a stream is a link or an embed. Put the join link, or the embedded live video, in an entry of the event that opens shortly before the session, so only ticket holders reach it ([Entries and timed release](/overview/categories#entries-and-timed-release)). After the event, add the recording as another entry: everyone who held a ticket finds it there.

## In-person events

The venue, its address and its map pin move with the event, and Sherpo draws a map of the place on the event's page. Keep the address for ticket holders only with `reveal_location`, as Luma's "shown to guests" does. At the door, scan each guest's QR code in the merchant app ([Check guests in](/merchant-api/guides/event-check-in)).

## Hosts

Luma's co-hosts become members of your business, with what each may do: invite them in the merchant app ([Business and team](/merchant-app/business-and-team)).

## Send your audience to Sherpo

Luma can't redirect an event page elsewhere. Once an event is published on Sherpo, point every link you shared at its new page, put your store's address on your Luma calendar, and close registration on Luma, so nobody buys a ticket in both places. A guest who registers on Luma before you close it is imported by the next run of the script.

## Past events

Import a past event when its history matters to you: its guests and what they paid stay in your orders and analytics, and the guests can reach any recording you add. A past event sends no registration email and sells no tickets. Otherwise, keep its export from Luma.

## Questions

**What does Sherpo take from a ticket?** Nothing: Stripe's own fee is the only one ([Payments and payouts](/overview/payments)).

**Can guests be refunded on Sherpo?** A refund of a ticket sold on Luma is made on Luma's Stripe payment. Record it on Sherpo too, so the ticket ends there as well.

**Which time zone does an event show?** The one it had on Luma: each session keeps its own.

**Do guests need an account?** No: they're invited by email, and their first sign-in with that address opens everything they hold.

Source: https://docs.sherpo.io/overview/migrate-from-luma/index.mdx
