> For the complete documentation index, see [llms.txt](https://docs.helpyousponsor.com/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helpyousponsor.com/guides/core-features/program-management/trips/trip-cloning.md).

# Trip Cloning

### Overview

Trip Cloning allows you to duplicate an existing trip to quickly set up recurring events like annual mission trips. Instead of recreating everything from scratch, you can clone a trip and selectively carry over budget items, tasks, documents, and settings.

### How to Clone a Trip

{% stepper %}
{% step %}
Navigate to the **Trips Table** from the sidebar.
{% endstep %}

{% step %}
Locate the trip you want to clone.
{% endstep %}

{% step %}
Click the **Clone** button (copy icon) in the Actions column.
{% endstep %}

{% step %}
A dialog will appear with cloning options.
{% endstep %}
{% endstepper %}

### Clone Options

When cloning a trip, you can select which elements to carry over:

| Option              | Default         | Description                                                             |
| ------------------- | --------------- | ----------------------------------------------------------------------- |
| **Basic trip info** | Always included | Trip name (appended with "Copy"), description, destination              |
| **Budget items**    | Included        | All budget line items with categories and amounts                       |
| **Tasks**           | Included        | Task definitions including targeting rules, reminders, and dependencies |
| **Documents**       | Not included    | Shared documents uploaded to the original trip                          |
| **Settings**        | Included        | Trip-level settings such as privacy and leader permissions              |

### What Is Never Cloned

<details>

<summary>Click to expand</summary>

* Participants and their enrollment data
* Donations and fundraising progress
* Task completions and approval history
* Messages and communication history
* Analytics data

</details>

### Date Shifting

If the original trip has start and end dates, you can optionally set new dates for the cloned trip. When you provide new dates, task due dates are automatically shifted by the same offset (the number of days between the old and new trip start dates).

**Example:** If the original trip started June 15 and had a task due May 1 (45 days before), and you set the new trip to start August 15, that task's due date will automatically become July 1 (still 45 days before).

### After Cloning

The cloned trip is created in **Draft** status. You can then:

* Edit the trip name, slug, and other details
* Add participants
* Review and adjust any cloned tasks or budget items
* Set the status to **Active** when ready