How to bring past events and guest lists over to a new tool

How independent event hosts can move past events and guest lists into a new tool, and what to check first.

By Uncommon Comforts · 2026-10-10

Uncommon Comforts is published by the team behind Connections, whose products are compared here alongside other tools.

Bringing past events and guest lists to a new tool takes three things: access and export files from the old tool, a place in the new tool where the records can land as drafts, and a review before anything goes live. Gather the guest list as a CSV and the past event pages, check how the new tool accepts them, then move events and guests in and check the details before publishing.

Option	Own platform fee	Card payment fee	Brings past events and guests
Connections Events, Free ^[1]	3% platform fee on Free ^[1]	not published	Pastes past event pages to drafts and lands guest CSV on a roster ^[1]^[1]
Connections Events, Pro ^[1]	Pro sales carry no platform fee, so the only fee is the card payment fee from Stripe, the separate card payment service. ^[1]	not published	Same import of past events and guest lists ^[1]^[1]
Any other tool: check its import and draft behavior	not published	not published	Check whether it takes a pasted page or a file, and whether lists land as drafts

What you need before you start

Before moving past events and guest lists to a new tool, gather what the move needs. Start with login access to the tool that holds the old records, so event pages and attendee lists can be opened and exported. Have the export files ready, usually a CSV of guests, and the past event pages themselves. Check how the new tool accepts that data before starting, since some tools take a pasted event page and others want a file. Decide what you want to bring: all past events or only the ones that still matter. Know what the guest list will become once it lands, such as contacts you can email later. Note the privacy rules that apply to the people on the list, and keep written consent where the rules require it. Set up the new account before the move so there is a place for the records to go. Confirm whether the new tool publishes anything on its own when data arrives, so nothing goes live before it is meant to. Keep a backup copy of the old files aside until the new records look right.

Step by step

Set up the new tool before bringing anything over, and open it on a plan that does not charge you yet. You want a place where drafts can sit until you check them. Nothing is published and nobody is emailed until you say so. ^[1]

Export the guest lists from the current tool. Most tools let you save an attendee list as a CSV, which is a plain table of names and contact details that other tools can read.

Bring past events over. Look for an import option in the new tool; some tools accept a link to the old event page, and others want a file of the event details. In a tool with a page import, pasting the old event page and choosing the events you want turns each one into an unpublished draft. ^[1]

Bring the guest lists over so the guests become useful records. When a guest CSV lands on a past event's roster, the guests become contacts you can reach later. ^[1]

Review each draft before anything goes public. Nothing should be published and nobody should be emailed until you say so. ^[1]

Check the details that matter for your kind of event, such as ticket prices, dates, and who handles the card payment, before you confirm the move.

Tools that can do it

Connections Events is made by the team that publishes this site. It brings past events and guest lists in from Luma, Eventbrite or Meetup, so it fits a host who has kept records in one of those tools. ^[1] A pasted page becomes an unpublished draft, and a guest CSV lands on a past event's roster and makes the guests the host's contacts. ^[1] A host adds a ticket with a name and price from the ticket menu on the event page. ^[1] Guests carry a QR ticket that the host scans at the door to check them in. ^[1] Guests can add the ticket to Apple Wallet, and they get automatic reminders 24 hours and 1 hour before an event. ^[1]^[1] People who follow the host get an email when the host publishes a public event. ^[1] A new event with no photo gets a designed cover from a gallery of 36 across nine kinds of event. ^[1] When a guest cancels or capacity is raised, the waitlist fills the free seats and each guest is told they are in. ^[1] The analytics tab shows a sales figure over time and a sales-by-ticket-type table. ^[1] Guests can add photos to the event once it starts, and the album shows on the event page. ^[1] Co-hosts are free. ^[1] A host can copy a Register link or an iframe card to put a registration button on their own website. ^[1]

For any other tool, ask the same questions before you commit: what export files it accepts, whether past events and guest lists can be brought in as drafts, and what fee applies to ticket sales. A host can start Connections Events on the free plan with no card on file, which gives a safe place to test the move. ^[1]

Common mistakes to avoid

Keep the old export file until the new records look right, so a mistake does not lose the list. Do not bring lists over without checking the consent and privacy rules that apply to the people on them. Review each draft before it goes live, since a published event can reach people you did not mean to contact. Do not assume reminders go out on their own until the tool says so; check what each tool sends. When you sell tickets, know both the tool's own fee and the card payment fee, since the two are charged together. Do not skip checking whether a guest list becomes usable contacts that can be emailed later, or it may arrive as dead records. Check how a waitlist fills and what guests are told, rather than assuming seats go to the next person. Confirm how check-in works at the door before the event, so the plan is ready when guests arrive.

Frequently asked questions

Can event hosts bring old events and guest lists into a new tool?

Yes. In a tool with a page import, a host pastes the old Luma, Eventbrite or Meetup page, ticks the events they want, and each one becomes an unpublished draft. ^[1] A guest list exported as a CSV lands on a past event's roster and makes the guests the host's contacts. ^[1] The host reviews the drafts and publishes only when the records look right.

Is it free to bring past events into a new tool?

A host can start on Free with no card on file, and nothing is published and nobody is emailed until the host says so. ^[1] Free has a 3% platform fee on sales, while every paid plan has a 0% platform fee. ^[1] Pro has no platform fee on its sales, and the only fee is the card payment fee from Stripe, the separate card payment service. ^[1]

What is the fee to sell tickets in a new tool?

On Free the platform fee is 3%, and every paid plan has a 0% platform fee. ^[1] The card payment fee comes from Stripe, the separate card payment service, and is charged on top of the tool's own fee, so a host should plan for both. ^[1] Pro has no platform fee on its sales, and the only fee is the card payment fee from Stripe, the separate card payment service. ^[1]

Do guests get reminders after an event is moved to a new tool?

In Connections Events, guests get automatic reminders 24 hours and 1 hour before an event. ^[1] For other tools, check what reminder emails each one sends, since behavior differs. Reminders are part of keeping the moved event running smoothly, so confirm the schedule before you rely on it.

Can new guests check in and pay at the door after the move?

Guests carry a QR ticket that the host scans at the door to check them in. ^[1] A host sells tickets from the ticket menu on the event page. ^[1] Confirm how check-in works in any tool you choose, and know both the tool's own fee and the card payment fee before the event so the plan is ready.

Connections Pro is $39.99, removes the event, guest and manager walls, and its sales pay no platform fee, only Stripe's card fee. ^[1] Connections Free costs $0, and going over a limit stops the feature rather than billing you. ^[1]

Try Connections Events

Sources

Connections Events' own description of itself (the product of this site's publisher)