Bookitive
Events

Duplicating an event

Copy last year's setup into a fresh event — what carries over, what deliberately doesn't, and how dates shift.

Not verified yet

Annual events shouldn't be rebuilt from scratch. Duplicate event copies the complete setup of an existing event into a new draft while leaving all of the old event's data behind — so last year's ball becomes this year's in one dialog.

What carries over

  • Event settings — delivery mode, transfer policy, payment methods, protections, booster settings, and the rest.
  • Ticket types — with prices, capacities, limits, and descriptions.
  • Scheduled price phases and promo codes.
  • The seating plan — the full chart, with every seat freed: the new event starts at zero sold.
  • Zone mappings from the applied arrangement.

What deliberately doesn't

Orders, tickets, scans, customers' attendance, waitlist entries, refunds, sponsor deals, staff invitations, chart history, and fee records all stay with the original event. The duplicate also resets:

  • status to draft (never auto-published),
  • the sales-pause switch,
  • sold counters used by quantity-triggered price phases.

In short: configuration travels, history doesn't.

Dates shift together

In the duplicate dialog you pick the new start. Every other date in the copy — the end time, ticket sale windows, price-phase windows — shifts by the same delta as the start. If last year's early-bird phase ended 30 days before the event, this year's ends 30 days before the new date. You only review, not recompute.

Review the shifted dates anyway, especially price phases and sale windows — calendars drift (a weekend last year may be a weekday now), and a shifted "end of early bird" might land somewhere you don't want. The Dynamic pricing view shows them all on one screen.

Duplicating vs. arrangements

Duplication copies one event wholesale. If what you actually want to reuse is only the room layout, that's what venue arrangements are for — design the hall once, apply it to any event, and map zones to that event's own ticket types. Many organizers use both: an arrangement for the geometry, duplication for everything else.

On this page