ResytechResytech Docs
Activities

Clone an Activity

How to duplicate an existing activity to quickly create a similar offering in Resytech.

Use this guide when you want to create a new activity that shares most of its settings with an existing one. Cloning copies all configuration -- scheduling, pricing, manifest, custom fields, facilitator roles, and more -- so you only need to adjust what is different.

When to Clone

Cloning is useful when:

  • You offer the same activity at different durations or price points (e.g., a 1-hour and 2-hour version of a kayak tour).
  • You have seasonal variants of the same activity.
  • You are expanding to a new location with similar offerings.
  • You want to test a new pricing structure without modifying the original.

Steps

  1. Go to Activities in the left sidebar.
  2. Find the activity you want to clone.
  3. Click the Clone button (or open the activity and use the clone option from there).
  4. Enter a Name for the new activity. This is the only required field -- choose a name that distinguishes it from the original (e.g., "Sunset Kayak Tour" if the original is "Morning Kayak Tour").
  5. Click Clone.

The new activity is created immediately and you are taken to its settings page.

What Gets Cloned

The clone copies all settings from the source activity, including:

  • General information (description, tagline, details, cancellation policy, color)
  • Scheduling configuration (date type, time type, durations, cutoffs)
  • Pricing (pricing type, per-group guest allowance and extra-guest rate, and all pricing modifiers including their demand-utilization windows)
  • Tour options (private tours allowed, private-tours-only, internal equipment, per-slot participant limit)
  • The preselected default duration, pointed at the cloned copy of that duration
  • Manifest settings (guest limits, age restrictions, demographics)
  • Equipment assignments and settings
  • Check-in stages, requirements, waiver signature options, automatic advancement, and equipment-assignment visibility
  • Custom fields
  • Facilitator roles
  • Special events
  • Agreements
  • Communication settings
  • Payment settings (downpayment configuration)
  • Blackout dates, including any that are limited to specific equipment
  • Trip protection settings
  • Dynamic duration settings (if applicable)

What Does NOT Get Cloned

  • Media (photos) -- You need to upload images separately for the new activity.
  • Booking history -- The clone starts with zero bookings, with no copied check-in progress, arrival marks, or stage history.
  • Published state -- The clone is always created in an unpublished state, regardless of whether the source was published. The clone does keep the source's hidden setting, so an activity that was hidden from the activity list stays hidden once you publish the copy.
  • Category membership -- The clone is not added to any activity category. Add it from the category page once it is published.
  • Calendar sync connections -- External calendar integrations are not carried over.

Copy Only the Check-In Settings

To reuse a flow on an existing activity, use Copy from Activity in that activity's Settings → Check-in. Review the preview, copy the settings into the draft, then save. See Set Up a Multi-Stage Check-In.

Cloned and copied stages are independent of the source stages. Their waiver requirements still use the same location waivers; the waiver forms and submissions are not duplicated.

After Cloning

  1. Review the cloned activity's settings and update anything that should differ from the original.
  2. Upload media for the new activity.
  3. Publish the activity when you are ready.

Tips

  • Cloning is the fastest way to create a new activity when you already have a similar one configured. It avoids re-entering scheduling, pricing, and all other settings manually.
  • Always give the clone a distinct name. Having two activities with the same name creates confusion in the calendar, reports, and checkout.
  • The activity settings are independent after cloning. Shared resources, such as a waiver used by both activities, still affect both when edited.

On this page