> For the complete documentation index, see [llms.txt](https://help.donary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.donary.com/cloud-drm/getting-started/pre-start-checklist/import-campaigns.md).

# Import Campaigns

## How to import existing campaigns 

To get started, you can import all your current campaigns into the system.

**Here's how:**

1. In the left sidebar, go to the **“Lists”** category.
2. Click on the **“campaigns”** tab.
3. Click the **three-dot icon** in the upper right corner.
4. Select **“Import ”**
5. Download the **“Campaign Template”** Excel file.
6. Fill in the template with your existing campaign information.
   1. Campaign Number - Enter a unique number that does not already exist in the campaign list.
   2. Campaign Name - This name is used internally.
   3. Friendly Name - This name is used externally and is visible to the donor on receipts and invoices.
   4. Parent name - Enter the broader title for these types of campaigns. You can create nested sub-campaigns up to 5 levels deep, with each child campaign able to have its own sub-campaigns.
7. Save and close the file.
8. Drag the file into the upload area or click to **choose file**.
9. Click **“Upload.”**

Your campaigns are now imported and will appear in the campaigns list.

{% embed url="<https://drive.google.com/file/d/1Jh5yx1gkXw6IyByz3tzpv2WzUMjDBWnZ/view?usp=sharing>" %}

{% hint style="warning" %}
**IMPORTANT:**

* Make sure to fill in the template exactly according to the column titles to ensure a smooth import.
* Some columns include instructions on acceptable values—follow these carefully.
  {% endhint %}


---

# 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://help.donary.com/cloud-drm/getting-started/pre-start-checklist/import-campaigns.md?ask=<question>&goal=<user_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.