> ## Documentation Index
> Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Copying and renewing events

> Create a new event by copying an existing one, or renew a past event to carry over its historical performance data.

When you click **Add event** in your organizer dashboard and choose **Copy an event**, you can start a new event using an existing one as a template. There are two distinct flows — **Copy** and **Renew** — and choosing the right one matters because they behave differently.

<CardGroup cols={2}>
  <Card title="Copy an event" icon="copy">
    Creates an independent new event with no historical link to the original.
    Use this for a genuinely separate new event that happens to share a similar
    setup.
  </Card>

  <Card title="Renew an event" icon="rotate">
    Creates the next annual or periodic edition of the same event. Historical
    reporting data, marketplace performance, and participant reviews carry over.
    Use this for recurring events like a yearly race.
  </Card>
</CardGroup>

## Copying an event

Use **Copy** when you are setting up a brand new event — one that is separate from the original and should not inherit its history.

<Steps>
  <Step title="Open the copy flow">
    From your dashboard, click **Add event** → **Copy an event** → **Continue**.

    You can also copy from the event card's menu (the **⋯** icon) → **Make a copy**.
  </Step>

  <Step title="Select an event to copy from">
    Choose any event from your account — past or upcoming — to use as the template. All your events are available here.
  </Step>

  <Step title="Set the new event name and start date">
    * **New event name** — the title of the new event (required).
    * **New start date** — must be a date in the future (required).
  </Step>

  <Step title="Confirm">
    Review the warning about what is and isn't carried over, then click **Confirm**.

    **What is copied:**

    * Event listing content (descriptions, images, FAQ)
    * Tickets and their configurations
    * Registration forms and booking form fields

    **What is not copied:**

    * Reporting and registration data
    * Historic startlist entries
    * Event page reviews
    * Ticket capacities, waitlists, and price changes
    * Transactional emails
    * Discount codes
    * Credits
    * Participant settings (withdrawals, deferrals)
  </Step>
</Steps>

Your new event is created as unlisted — not visible to the public. Review and update the setup, then contact your account manager when you're ready to go live.

<Info>
  A copied event is not historically linked to the original. Registration
  numbers, reviews, and performance data start fresh. If you want to carry that
  history over, use **Renew** instead.
</Info>

## Renewing an event

Use **Renew** when you are preparing the next edition of an ongoing event — for example, next year's race. The renewed event carries forward your historical marketplace performance, reporting, and participant reviews, which helps with discoverability and year-over-year tracking.

<Steps>
  <Step title="Open the renew flow">
    From your dashboard, click **Add event** → **Copy an event** → **Continue**, then select **Renew** in the following modal.

    You can also open this directly from the event card's **⋯** menu if that option is available.
  </Step>

  <Step title="Select the past event to renew">
    Choose from your past events. Only completed events are available in the renew flow.
  </Step>

  <Step title="Set the next event name and start date">
    * **Next event name** — the title of the new edition (required).
    * **New start date** — must be a date in the future (required).
  </Step>

  <Step title="Confirm">
    Review the callout explaining what will and won't carry over, then click **Renew**.

    **What is carried over:**

    * Existing event setup and listing content
    * Historic reporting data
    * Participant reviews

    **What is not carried over:**

    * Limited capacities
    * Discount codes
    * Credits
    * Participant settings (withdrawals, deferrals)
    * Ticket price changes
  </Step>
</Steps>

Your renewed event is created as unlisted. Make any edits you need — updated dates, new pricing, refreshed content — then contact your account manager to publish it.

<Info>
  A renewed event is linked historically to its predecessor, so your marketplace
  performance and reviews transfer to the new edition. If you want a completely
  clean break, use **Copy** instead.
</Info>

## Choosing between copy and renew

|                     | Copy                   | Renew                                |
| ------------------- | ---------------------- | ------------------------------------ |
| Use for             | A new, unrelated event | The next edition of an ongoing event |
| Historical data     | Not carried over       | Carried over                         |
| Participant reviews | Not carried over       | Carried over                         |
| Reporting           | Fresh start            | Continues from previous event        |
| Event URL           | New URL                | May change — update any shared links |