> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-console/clone-existing-campaign.md).
# Clone Existing Campaign
## Overview
The **Clone Campaign** feature allows administrators to create a new campaign by copying the configuration of an existing one.
This helps reduce setup time by reusing previously defined settings such as:
* Campaign boundaries
* Delivery strategies
* Mobile app configurations
* Other setup details
When cloning, you only need to update the **campaign name** and **campaign duration** before proceeding.
## Steps
### Step 1: Select Clone Campaign
1. From the dashboard or Campaign Home Page, click **Clone an Existing Campaign**.
2. You will be redirected to the **My Campaigns** screen.
### Step 2: Choose the Campaign to Clone
1. On the **My Campaigns** screen, review the list of available campaigns.
2. Locate the campaign you want to copy.
3. Click the **Clone Campaign** button next to it.
### Step 3: Enter New Campaign Details
1. Enter a unique **Campaign Name** for the new campaign.
2. Select the **Start Date** and **End Date** for the campaign duration.
Ensure the campaign name is unique, and the dates align with your program plan.
Click **Submit** to create the cloned campaign.
The system will generate a new campaign with the copied configurations.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digit.org/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-console/clone-existing-campaign.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
