> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/events/duplicating-and-archiving.md). # Duplicating and archiving As you run more events, you'll want ways to reuse your setup and keep your workspace organized. Duplicating saves you from starting over each time, and archiving keeps completed events out of your way without losing any data. *** ## Duplicating an Event If you run recurring events -- like a monthly market or an annual festival -- duplicating lets you create a new event based on an existing one in just a few clicks. ### How to Duplicate 1. Open the event you want to copy 2. Click the **Duplicate** button 3. A new event is created in **Draft** status with the details copied over 4. Update the event name, dates, and any other details for the new occurrence 5. Set up the event as needed and publish when ready ### What Gets Copied * Event name, description, location, and type * Products (booth types, add-ons, and sponsorship packages) with their pricing * Event settings (categories, approval mode, vendor cap, refund policy) ### What Does Not Get Copied * **Vendor assignments** -- You start fresh with no vendors attached. This lets you manage each event's vendor list independently. * **Form submissions** -- Any applications or registrations from the original event stay with that event. * **Payment history** -- Transactions belong to the original event and are not carried over. > **Tip:** After duplicating, take a moment to review the copied products and settings. Pricing, booth availability, and vendor categories may need adjusting for the new event. *** ## Archiving an Event When an event is over and you're done managing it, archiving moves it out of your active workspace while keeping all the data intact. ### How to Archive 1. Open the event you want to archive 2. Click the **Archive** button 3. Confirm the action when prompted The event's status changes to **Archived** and it moves out of your main event list. ### What Happens When You Archive * **No new registrations.** Vendors can no longer apply or register for the event. * **All data is preserved.** Vendor lists, payment records, form submissions, booth assignments, and everything else stays exactly as it was. You can view it anytime. * **The event is still accessible.** Archived events can be found in your event list by filtering for archived events. Nothing is hidden or deleted. * **You can still duplicate it.** Archived events can be duplicated to create new events, which is perfect for bringing back a recurring event next season. > **Tip:** Make a habit of archiving events once they're fully wrapped up. It keeps your dashboard focused on what's active and makes it easier to find the events that need your attention. *** ## A Common Workflow for Recurring Events If you run the same event on a regular schedule, here's a simple workflow that keeps things efficient: 1. **Run your event** and manage vendors, payments, and check-in as usual 2. **Archive the event** once everything is settled and the event is complete 3. **Duplicate the archived event** when it's time to start planning the next one 4. **Update the new draft** with fresh dates, any pricing changes, and new details 5. **Publish** and start accepting vendors for the new event This way, you build on your previous setup each time instead of starting from scratch, and your historical data stays neatly organized in the archived events. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://vendorspace.gitbook.io/docs/events/duplicating-and-archiving.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.