Recipes

Cloning and Groups

When you run the same event repeatedly or manage a family of related events, cloning and event groups save hours of setup time. Cloning copies an existing event's configuration — tickets, form, page design, sessions — into a new event. Event groups let you link multiple events for unified reporting and attendee discovery.

The Clone event wizard — select which elements to copy forward into the new event.
The Clone event wizard — select which elements to copy forward into the new event.

Before you start

  • Identify the source event you want to clone. It can be in any Status (Active, Closed, Draft).
  • Know which elements you want to include in the clone: tickets, form questions, page design, sessions, speakers, sponsors.
  • If you plan to group events, decide on a group name — the group will appear as a parent record in Salesforce.

Steps — Cloning an Event

  1. Go to **Events** in the sidebar and find the event you want to clone. Click the **⋯** menu on the event card and select **Clone**, or open the event workspace and choose **Clone** from the event action menu.
  2. The Clone wizard opens. Enter a new name for the cloned event and update the start and end dates.
  3. Select which elements to copy: Tickets & Items (checked by default), Form and questions, Page Designer settings, Sessions, Speakers, Sponsors. Uncheck anything that should not carry forward.
  4. Click **Create Clone**. Forge creates a new `conference360__Event__c` in Salesforce with all selected elements duplicated. The clone starts in Draft status so you can review before activating.
  5. Open the cloned event and review each section. Update anything that differs from the original: venue address, speaker lineup, ticket prices, or form questions.
  6. Set the clone's Status to *Active* when ready to open registration.

Steps — Creating an Event Group

  1. Create or open an event. On the **Event Info** tab, find the **Event Group** field.
  2. Either select an existing group from the lookup or create a new group name. Forge creates the `conference360__Event_Group__c` record in Salesforce if it does not exist.
  3. Repeat for each event in the family — assign them all to the same Event Group.
  4. To view all events in a group, use the **Events** list view and filter by Event Group, or open the Event Group record directly in Salesforce to see the full list.

What cloning does not copy

Cloning does not carry over attendee registrations, transaction history, actual check-in data, or communications send history. Only the structural configuration (tickets, form, design) is duplicated. Discount codes are also not cloned — create new ones on the cloned event if needed.

Events grouped under a common Event Group — useful for conference series and roadshows.
Events grouped under a common Event Group — useful for conference series and roadshows.

What this creates in Salesforce

Salesforce Field Mapping
ForgeSF ObjectSF Field
Cloned eventconference360__Event__cName / conference360__Status__c = Draft
Cloned ticketsconference360__Event_Item__clinked to new event
Cloned formconference360__Form__clinked to new event
Cloned sessionsconference360__Session__clinked to new event
Event groupconference360__Event__cconference360__Event_Group__c

Verify

  • The cloned event appears in the Events list with the new name and Status = Draft.
  • All selected elements (tickets, form, page design) are present in the clone.
  • The clone's start and end dates are the new dates you specified, not the original's dates.
  • No attendee records are carried over from the source event.
  • Events in the same group all show the same `conference360__Event_Group__c` value in Salesforce.
  • A Salesforce report filtering on the Event Group returns all events in the series.