Back to Bookings

Moving a Booking to Another Event

Put a booking on a different event you run, without cancelling or refunding it

Bookings 4 min read

Moving a Booking to Another Event

Somebody books the wrong week of a camp. Or you cancel an event and run a replacement, and twenty people need to be on the new one.

Until now the only tool was cancel, refund, and ask the customer to book again, which threw away the booking reference, the ticket codes, the answers to your safeguarding questions and the money. The booking can move instead.

How it works

Open the booking on the event's bookings page and press Move booking. Pick one of your other events and you get a preview of exactly how the booking lands on it before anything happens: which session becomes which, what happens to the ticket tier, the add-ons, the booking questions and any check-ins already recorded.

Nothing is charged and nothing is refunded. The move is value-neutral, so if the new event costs more or less, you absorb the difference or settle it with the booker yourself.

Check-ins recorded on the old event are cleared from its register when the booking moves. You can move a booking back, but those check-ins don't come back with it.

What you choose

Sessions are matched up in order, skipping any session on the new event that has already run, and the grid is yours to edit. What you tick is what gets written.

You can also correct the emergency contact while you are in there, and add a reason for the move. The reason goes to the booker, and it is the only explanation they get, so it is worth writing.

What stops a move

The preview tells you when a move is not possible, and the reasons are:

  • The booking has to still be active. A cancelled booking cannot be moved.
  • The two events have to be run by the same business and the same account. A club whose admin created one event and whose coach created the other has two settlement identities, and moving between them would aim a later refund at an account that never took the charge.
  • They have to be the same type of event.
  • The new event has to be published, still running, and not already over. A draft needs publishing first.
  • Its sessions cannot all have run already, or there is nowhere to put anybody.
  • A ticketed event needs ticket types, or there is nothing to move the tickets onto.
  • Every attendee needs at least one session on the new event.
  • Age rules have to hold. An under-18 place cannot move onto an adults-only event, an adult place cannot move onto a children's event, and a date of birth the new event rejects stops the move. Nobody is quietly relabelled to fit.

What you are warned about

Warnings do not stop the move. You read them, acknowledge them, and go ahead:

  • A session on the old event with no match on the new one is dropped
  • A session on the new event that nobody on this booking is going to
  • Check-ins already recorded are cleared from the register. The record is kept on the move itself
  • An add-on the new event does not offer. The charge stands and the line stays on the booking with its name and price, so nobody is refunded for something you chose to carry across, but it is no longer linked to an add-on you can edit
  • A ticket tier the new event does not have, so the place sits under a different tier. What they paid does not change
  • The two events are priced differently, flat rate against per session for example. Nothing is recharged, so the booker keeps what they paid
  • Answers to questions the new event does not ask. They are kept rather than deleted
  • Questions the new event asks that this booking has never answered, so you know to follow it up
  • The two events are priced in different currencies. Nothing is converted or recharged
  • The event is delivered differently, in person against remote
  • A discount from the original event, which stays on the booking as a record of what was charged and is not re-applied
  • The move takes the new event past its capacity

The booker is told

They get a notification and an email naming both events, with your reason. Their booking reference, their ticket codes and everything they paid stay exactly as they were.

Who can move a booking

The desk: you, your Admins and your Booking Managers. The control does not appear for an allocated coach, and it comes off while you are acting for a different organisation, because the move is checked against the organisation on the way through.