Task · Event settings

Run the same event again next year

Copy a whole event with every date moved forward, as a draft you publish when it's ready.

8 steps · About 4 minutes

1. From Events, open the row menu beside the event and select Duplicate…

2. Give the copy a Name and a Web address

   Both are suggestions. A name or address ending in a year gets the next one, so "Frontend Conf 2026" becomes "Frontend Conf 2027".

   go.tito.io/acme/summer-fete/admin/duplicate

3. Set the Start date and End date

   The suggestion is the same weekdays a year on, so a Friday workshop stays on a Friday.

4. Choose how everything else with a date moves

   Move them with the event shifts every other date by the same whole number of weeks, so weekdays and times of day stay put. Copy them exactly as they are leaves every other date where it is.

5. Change any date you like, in the table

   Every row is editable. The date shown is where the shift would put it, and you can type a different one.

   A row you change stays where you put it.

   A row you leave alone keeps following the shift.

   A date that has already gone is marked In the past.

   A callout above the table says how many there are. Sales for those tickets would be closed the moment you publish.

6. Turn off anything you don't want to bring across

   Five switches control what comes across: coupons and promo codes, portals, invitation lists, saved reports, and documents and downloads. All five start on, and a switch only appears when the event has that thing.

7. Select Duplicate event

   Coupon codes come across unchanged.

   A code printed on last year's program will work again the moment you publish. The summary the copy opens with names the codes, so you can change any that were printed.

   Portal share links are never copied.

   Every copied portal gets a brand-new link with sharing switched off.

   Invitation lists come across empty.

   Last year's guests stay where they are, and you can't bring them across.

   What always comes, and what never does Always: ticket types, sessions and their times, items and donations, questions and where they're asked, check-in lists, taxes, widget setup, design and theme, request forms, and every setting. Never: orders, attendees, tickets, check-ins, messages sent, ticket requests, and the activity trail.

8. Read the summary, then publish when you're happy

   The copy opens with a summary of what came across and what needs your attention.

   Publishing only ends the draft.

   It doesn't put anything on sale. Every ticket type in the copy arrives off sale, whatever the original was.

   Copying one thing instead of a whole event A ticket type, a session, an item, a coupon, a portal, a saved report and a check-in list each have a Duplicate item in their own row menu.