> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/guides/migration/jira-to-clickup-migration.md).

# Jira to ClickUp Migration

Migrating tasks and project data from ClickUp to Jira is a critical step for organizations consolidating platforms or transitioning development and support workflows. With Getint, this migration process becomes straightforward, accurate, and reliable.

Getint ensures that all essential data, including task types, custom fields, statuses, comments, and attachments, are transferred while preserving the integrity of your records. Whether you're moving an entire ClickUp Space or selectively migrating specific tasks, this guide walks you through the process step-by-step.

### Requirements for Migrating Historical Data <a href="#requirements-for-migrating-historical-data" id="requirements-for-migrating-historical-data"></a>

#### Migration License <a href="#migration-license" id="migration-license"></a>

Migrating historical data requires a migration license, as integration licenses alone do not support this functionality. Migration licenses are billed separately.

To purchase a license, visit our [Pricing Page](https://www.getint.io/pricing) and select the **Migration** tab. You can also contact our team via the [Help Center](https://getint.io/help-center) for assistance.

Before purchasing, we encourage you to test the process using our trial version, which allows:

* Up to 20 migration runs
* A maximum of 5 items per run

To begin your trial, visit: [ClickUp Integration for Jira (2-way ClickUp Connector)](https://marketplace.atlassian.com/apps/1231636/clickup-integration-for-jira-2-way-clickup-connector?hosting=cloud\&tab=overview)

For best practices and advanced tips, see: [Getint Migration Guide – Best Practices & Preparation](https://docs.getint.io/guides/migration/getint-migration-guide-best-practices-and-preparation).

#### Preparing Your Environment Before Migration <a href="#preparing-your-environment-before-migration" id="preparing-your-environment-before-migration"></a>

Keep the following points in mind when planning your ClickUp to Jira migration:

* **Issue Types**: The integration supports ClickUp tasks as the only issue type. Plan your Jira type mapping accordingly (for example, ClickUp Task to Jira Task or Story).
* **Item Hierarchy**: Sub-items are not currently supported in Jira–ClickUp synchronization.
* **Synchronization Scope**: In ClickUp, you can specify a Space and a Folder, but not an individual List, which means all lists in a folder are synced. If you only want to migrate part of a folder, use filtering.
* **Text Formatting**: Formatting is not fully preserved during synchronization; bullet points may not convert correctly in Jira, and embedded links can be removed. Inline images aren't supported for the Description field.
* **Change History**: Getint cannot migrate the history of changes.
* **Comments**: Comments created by Getint will appear under the user account used for the connection. Consider creating a dedicated Service Account for the migration. The original author's name will appear in the comment footer.

For the full list of supported fields and limitations, see the [ClickUp Connector page](https://docs.getint.io/getting-started-with-the-platform/apps-connectors/clickup).

#### Handling Fields That Cannot Be Mapped <a href="#handling-fields-that-cannot-be-mapped" id="handling-fields-that-cannot-be-mapped"></a>

Before starting your migration, ensure that custom fields used in ClickUp also exist in Jira. If the destination field is missing, it must be created manually to enable proper mapping. Getint supports ClickUp custom fields of type **Dropdown, Labels, Number, People, and Text**.

For steps to create fields in both tools, refer to: [How to Create Custom Fields](https://docs.getint.io/getintio-platform/workflows/how-to-create-a-custom-field-in-all-supported-software).

#### Migrating Values Without 1:1 Mapping <a href="#migrating-values-without-1-1-mapping" id="migrating-values-without-1-1-mapping"></a>

If a field in ClickUp doesn't have a direct counterpart in Jira or you want to avoid the 1:1 mapping, you can use the **Use label from the other side** option to inject its value into a custom text field.

**Steps:**

* Create a text custom field in Jira.
* In the Getint field mapping screen, map the source ClickUp field to the Jira text field.
* Enable **Use label from the other side** to insert the original value.

This approach will insert the label/value of the original field into the destination field. Especially helpful for migrating the Assignees. You probably don't want to recreate the accounts of people no longer in the company in Jira. This way, no mapping is required; we will inject the value into a text field.

You can also migrate values from **multiple source fields into one** text field. You can read more about how to set up this option [here](https://docs.getint.io/getintio-platform/workflows/how-to-map-fields).

### Setting Up Your ClickUp to Jira Migration <a href="#setting-up-your-clickup-to-jira-migration" id="setting-up-your-clickup-to-jira-migration"></a>

#### 1. Set Up the Integration <a href="#id-1.-set-up-the-integration" id="id-1.-set-up-the-integration"></a>

Before migrating, you must set up a working integration between Jira and ClickUp. Follow our full integration guide, [Jira ClickUp Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-clickup-integration), to configure your connection properly. In short:

* Install the **ClickUp Integration for Jira** app from the Atlassian Marketplace and open it under **Apps** in Jira.
* Connect Jira using your instance URL and an API token generated in your Atlassian Account Settings (Security section). The token acts as your password.
* Generate a **ClickUp API Token**, create the ClickUp connection, and choose the Space and Folder you wish to migrate.
* Map ClickUp task types to Jira issue types, then map fields like **Title**, **Description**, **Assignee**, **Status**, and **Custom Fields**. Consider using the **Quick Build** beta feature for automated type and field mapping.
* Enable comments and attachments synchronization if you want them included in the migration.

After setup, we recommend disabling the integration or pausing activity in both tools during migration to avoid sync conflicts.

{% hint style="info" %}
**Pro tip**: Ensure you're logged in as an admin user to avoid permission issues during setup.
{% endhint %}

#### 2. Access the Migration Feature <a href="#id-2.-access-the-migration-feature" id="id-2.-access-the-migration-feature"></a>

Once your integration is set:

* Click **Migrate Data** from the left-side menu. If you're on a trial version, a warning will appear regarding your migration limits (5 items per run, 20 runs).
* Enable **Migration on Next Run** to proceed.

#### 3. Configure Migration Settings <a href="#id-3.-configure-migration-settings" id="id-3.-configure-migration-settings"></a>

* **Migration Direction**: Choose **ClickUp to Jira** so data flows from your ClickUp Space into the selected Jira project.
* **Handling Previously Migrated Items**: Choose how to handle items that were already migrated:
  * **Replace** (overwrite existing items).
  * **Update** (sync only new changes).
  * **Skip** (ignore already migrated items).
* **Selective Resync (Optional)**: If a previous migration was incomplete, choose specific fields to **resync**, such as **Assignee, Status, and Description**.
  * To resync **all fields**, enter ***ALL**.*
* **Selective Item Migration (Optional)**:
  * Enter specific **item IDs** to migrate **only selected tasks**.
  * Use **UI filtering** on the ClickUp side to refine which tasks are included, since JQL applies only to the Jira side.
* **Time Range Filtering:**
  * Select a **creation date range** in the **UTC timezone**.
  * Only tasks created or updated **within the selected period** will be migrated.

#### 4. Schedule and Run the Migration <a href="#id-4.-schedule-and-run-the-migration" id="id-4.-schedule-and-run-the-migration"></a>

When your settings are complete, click **Schedule Migration** at the bottom of the screen.

* Click **Schedule Migration** to queue the process.
* The system will begin migration during the next synchronization run.
* Monitor progress in the **Reporting section** or the **Latest Runs tab**.

{% hint style="info" %}
Migration runs appear under the **Mode** column as **MIGRATION** instead of **SYNC**.
{% endhint %}

#### 5. Enable Continuous Sync After Migration (Optional) <a href="#id-5.-enable-continuous-sync-after-migration-optional" id="id-5.-enable-continuous-sync-after-migration-optional"></a>

If you want to keep the items in sync after migration:

* Open the **Integration Settings**.
* Click **More** > **Enable Continuous Sync**.

You can also uncheck the box below when you are setting up the migration.

This ensures that **newly created** tasks, issues, and updates flow **between ClickUp and Jira** moving forward.

### Why Choose Getint Migration Over CSV Import? <a href="#why-choose-getint-migration-over-csv-import" id="why-choose-getint-migration-over-csv-import"></a>

Traditional CSV imports require manual data manipulation and lack automation, often leading to data loss and inconsistency. Getint eliminates these issues by providing:

#### 1. Smart Field Mapping <a href="#id-1.-smart-field-mapping" id="id-1.-smart-field-mapping"></a>

✔ Getint enables precise **manual field mapping**, ensuring correct **data alignment**\
❌ CSV imports require **manual restructuring** after import

#### 2. Selective Migration <a href="#id-2.-selective-migration" id="id-2.-selective-migration"></a>

✔ Getint supports **UI filtering, item ID selection, and date-based migration**\
❌ CSV imports transfer **all data**, requiring **manual clean-up**

#### 3. Real-Time Monitoring <a href="#id-3.-real-time-monitoring" id="id-3.-real-time-monitoring"></a>

✔ Getint provides **sync logs, error tracking, and live migration updates**\
❌ CSV imports offer **no real-time feedback**

#### 4. Post-Migration Sync <a href="#id-4.-post-migration-sync" id="id-4.-post-migration-sync"></a>

✔ Getint **automatically syncs** data post-migration\
❌ CSV imports require **additional steps** to align projects and workflows

### Need Help? <a href="#need-help" id="need-help"></a>

For additional **assistance or troubleshooting**, visit our [**Help Center**](https://getint.io/help-center).

Considering migration? [**Schedule a Demo**](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team) with our **experts** to explore how **Getint** can support your **ClickUp to Jira** migration.

<figure><img src="/files/JdO0qTCtnIyTE6wW4cet" alt=""><figcaption><p><a href="https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team">Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!</a></p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.getint.io/guides/migration/jira-to-clickup-migration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.