Cloning a sponsorship

Edited

Overview

Cloning a sponsorship copies its name, price, inventory, benefits, and image into a new sponsorship on the same event. It is the fastest way to add another tier with similar structure or to spin up a variant.

Before you start

  • You need an org_manager or chamber_staff role

  • Identify the source sponsorship to clone

  • Decide what should change in the new sponsorship (price, name, benefits)

Step-by-step

  1. Open the parent event from Sidebar > Events

  2. Find the source sponsorship in the list

  3. Click the three-dot menu on its row and choose Clone sponsorship

  4. The new sponsorship is created with -Copy in its name and availability set to not_yet_available

  5. Click into the clone and update name, price, inventory, benefits as needed

  6. Flip availability to public when ready

What gets copied vs. not

  • Copied: name (with -Copy suffix), price, inventory, benefits, descriptions, image, exposure tier, display order

  • Not copied: orders, sponsors, first-rights holders, sales history

Tips & best practices

  • Clone when you want a sister tier (e.g., "Gold A" and "Gold B" with one minor difference)

  • Always rename the clone right away — the -Copy suffix is not customer-facing-friendly

  • If you want to clone into a different event, clone the parent event instead

  • Use cloning combined with bulk export/import for chambers running large catalogs

FAQ

Can I clone a sponsorship into another event?
Not directly. Clone the event, or use bulk export/import.

Does cloning copy first-rights holders?
No. First rights are tied to a specific sponsorship and must be re-added.

What status is the clone created in?
Always not_yet_available so you can review before publishing.

Related articles

  • Creating a sponsorship

  • Cloning an event

  • Bulk importing sponsorships from CSV

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.