Skip to content
Get a quote

ClickUp to Jira migration

We migrate Tasks, Subtasks, Custom Fields, Time Entries, and Attachments from ClickUp into Jira with the List-to-Issue-Type mapping resolved upfront, nested subtask hierarchy flattened into Jira Subtasks, and every ClickUp Custom Field mapped to a typed Jira field before any data moves.

Short answer

FlitStack AI migrates jira cloud sites, projects, component or epics, issue types and issues from ClickUp to Jira, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

By

Source ClickUp
DestinationJira
Jira Cloud SiteProjectComponent or EpicIssue TypeIssue
Mapped field by field · sample run · one-click rollback

What moves from ClickUp to Jira?

Moving from ClickUp to Jira is a structural migration, not a record copy.

Read the full summary

ClickUp organizes work as Workspace > Space > Folder > List > Task > Subtask with Lists as the primary work container. Jira organizes work as Project > Issue Type > Issue > Subtask with Issue Types (Story, Task, Bug, Epic) replacing Lists as the work container. We resolve the hierarchy mapping during scoping, define which ClickUp Lists map to which Jira Issue Types, and preserve the parent-subtask relationship through Jira's native Subtask issue type. ClickUp Docs content migrates as plain text into Jira issue descriptions due to API formatting limitations; standalone Docs should move to Confluence as a separate setup. ClickUp Automations do not migrate as code and are delivered as a written inventory for rebuild in Jira Automation. We sequence the migration in dependency order starting with Jira Projects and Components, followed by Issues, Subtasks, Work Logs, Comments, Attachments, and Labels, with row-count reconciliation at each phase.

1:1

Workspace → Jira Cloud Site (Organization)

ClickUp Workspace maps to the Jira Cloud Site as the top-level organizational container.

How it maps

Members, billing, and site-level settings transfer conceptually. We extract workspace-level Custom Fields during scoping and note their placement for recreation at the equivalent Jira project level since Jira does not have a workspace-scoped field model.

1:1

Space → Project

ClickUp Space maps to a Jira Project as the primary work container.

How it maps

We preserve Space-level configurations including access permissions and Custom Fields by recreating them as project-level fields in Jira. Each Jira Project requires an Issue Type Scheme, which we configure during schema design to match the Space's intended work types.

configuration

Folder → Component or Epic

ClickUp Folders are an optional middle organizational layer that map to either Jira Components (if used as task containers) or Jira Epic issues (if used as high-level work groupings).

How it maps

We determine the appropriate mapping during scoping based on how Folders are used in the source workspace. Components are simpler containers within a Project; Epics create a parent-child hierarchy with linked Stories and Tasks.

1:N split

List → Issue Type

ClickUp Lists map to Jira Issue Types (Story, Task, Bug, or Epic) based on the List's intended work type.

How it maps

A single List becomes a Jira Issue Type, and all tasks within that List become Jira Issues of that type. Jira's native importer allows mapping one List to one Issue Type. We pre-configure the Issue Type Scheme before migration to ensure the List-to-Type mapping is validated and consistent across all Lists.

1:1

Task → Issue

ClickUp Tasks map directly to Jira Issues with the Issue Type determined by the parent List mapping.

How it maps

Standard task properties migrate: summary becomes issue summary, description becomes issue description (with formatting limitations), status maps to a Jira Status, priority maps to Priority, assignees map to Assignee, due dates migrate, and tags become Labels. Dependencies between tasks migrate as Jira Issue Links (Blocks and Is Blocked By types).

1:1

Subtask → Subtask

ClickUp Subtasks map to Jira Sub-Task issues linked to their parent Jira Issue.

How it maps

Jira Subtask is a distinct Issue Type with a fixed set of fields (summary, assignee, status, priority, description) that differs from ClickUp where subtasks inherit fewer properties than their parent. We flatten the ClickUp subtask hierarchy into Jira Sub-Tasks, noting that any ClickUp subtask-specific Custom Fields require Jira custom field recreation on the Subtask issue type separately.

What moves12 objects
ClickUpJira
  • WorkspaceJira Cloud Site1:1
  • SpaceProject1:1
  • FolderComponent or Epictransformed
  • ListIssue Typesplit
  • TaskIssue1:1
  • SubtaskSubtask1:1

+ 6 more in the mapping below

How ClickUp and Jira differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionClickUpJira
Work hierarchyWorkspace > Space > Folder > List > Task > Subtask with Lists as the primary work containerProject > Issue Type > Issue > Subtask with Issue Types (Story, Task, Bug, Epic) as the work container
Custom fieldsScopable at List, Folder, Space, or Workspace level with location-dependent inheritanceProject-scoped with no inheritance model; all custom fields are explicitly assigned per project
Subtask architectureSubtasks are independent task records with reduced property inheritance from parentSubtasks are always nested under parent issues with a fixed field set (summary, assignee, status, priority, description)
Time trackingNative time tracking with timer and manual entry; reporting capabilities are limited without external toolsWork Logs tied to issues with native sprint velocity and capacity reporting; billable tracking available in Premium
FilteringVisual filtering with limited cross-list aggregation; subtasks treated as separate recordsJira Query Language (JQL) for complex cross-project queries with full Boolean and date-based filtering
AI add-on costClickUp Brain AI is a separate add-on at $9 per member per month on top of base subscriptionAtlassian Intelligence is included in Jira Premium ($14.54/user/month) and Enterprise tiers
Developer integrations1,000+ integrations via Zapier, Make, and webhooks; no native Git integrationNative GitHub, Bitbucket, GitLab, and CI/CD integrations with commit and PR linking from issue context

What to watch for in a ClickUp to Jira migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Jira's native importer limits Lists to 10 per import operation

Jira's built-in ClickUp importer processes up to 10 Lists per import operation and requires OAuth connectivity to the ClickUp workspace throughout the import.

How we handle it

For workspaces with dozens of Lists across multiple Spaces, this requires batched import runs with OAuth re-authentication between batches. FlitStack AI sequences imports by Jira Project, authenticating once per batch and handling partial failures with retry logic that Jira's native importer does not provide. We also handle the 50GB file upload limit in the native importer by chunking large workspace exports.

high

Custom Fields frequently cause Jira import failures

Multiple teams performing ClickUp to Jira migrations via the native importer have reported errors caused by Custom Fields.

How we handle it

A documented workaround involves creating a copy of the List, removing all Custom Fields from the copy, running the import, then re-adding Custom Fields to Jira after migration. We follow this staged approach by default: we export the full Custom Field schema separately, run the task import without Custom Fields first, then recreate Custom Fields in Jira and backfill values via the Jira Bulk API. This avoids the import failures that stall native importer runs and gives us a clean field type audit.

medium

ClickUp subtask hierarchy does not map cleanly to Jira Sub-Tasks

ClickUp subtasks are second-class records that do not inherit all parent task properties and are harder to aggregate across views.

How we handle it

Reddit reviewers describe ClickUp's subtask behavior as 'wonky' and a 'joke.' Jira Sub-Tasks have a fixed field set (summary, assignee, status, priority, description) and cannot carry custom fields without explicit configuration on the Subtask issue type. We flatten ClickUp subtasks into Jira Sub-Tasks, flag any ClickUp subtask-specific Custom Fields for manual Jira Sub-Task field configuration, and note that subtask visibility in Jira sprint boards requires explicit board configuration.

medium

ClickUp Docs API does not preserve rich formatting

The ClickUp Docs API does not fully preserve rich formatting available in the product UI, including certain blocks, embeds, and styling.

How we handle it

We export Docs content as structured text with available formatting preserved, but complex Docs may require manual post-migration review to restore full visual fidelity. Standalone Docs that are not attached to tasks are delivered as a separate export for the customer's admin to review and recreate in Confluence if Confluence is in scope.

low

ClickUp Automations do not migrate to Jira Automation as code

ClickUp Automations trigger on task events such as status changes or due date approaches and are scoped per List or Space.

How we handle it

Jira Automation is a separate rules engine with different triggers, conditions, and actions. We do not migrate Automations as executable code. We deliver a written inventory of every ClickUp Automation with its trigger, conditions, actions, and a recommended Jira Automation equivalent for the customer's admin to rebuild post-migration. Business plan includes 5,000 automations per month in ClickUp; Jira Automation has its own action limits that vary by tier.

How the migration runs

  1. Discovery and workspace audit

    We audit the source ClickUp workspace across all Spaces, counting Lists, Tasks, Subtasks, Custom Fields (with scope metadata for List vs Space-level fields), Tags, Goals, time entries, Docs, and active Automations.

    What this step covers

    We extract the full API schema including field types, valid values for picklists, and dependency relationships. We note the ClickUp plan tier to determine API rate limits (100 req/min on Free, Unlimited, and Business plans) which affect extraction timeline. The discovery output is a written scope document with a proposed Jira Project structure, Issue Type Scheme mapping, and a Custom Field migration plan.

  2. Jira schema design and configuration

    We configure the Jira destination environment before any data moves.

    What this step covers

    This includes creating Jira Projects (one per ClickUp Space or consolidated based on scoping), configuring Issue Type Schemes to match ClickUp List-to-Type mappings, setting up status categories, creating Custom Fields with equivalent types, enabling Subtask issue types, and adding Components if Folder mapping requires it. We also configure the Jira Bulk API permissions for the migration user and document all ClickUp Automations requiring a Jira Automation rebuild for handoff post-migration. Schema is deployed to a Jira Sandbox for validation before production.

  3. Data extraction and transformation

    We extract the full ClickUp dataset via the REST API using paginated fetches and exponential backoff to respect rate limits.

    What this step covers

    Extraction preserves original timestamps, assignees, tags, and relationship data. Transformation converts task hierarchy into Jira Issue Types, maps ClickUp statuses to Jira Status values, converts Custom Field types for Jira compatibility, translates task dependencies into Jira Issue Links (Blocks and Is Blocked By), converts time entries to Work Logs, and prepares Docs content for Jira descriptions. We run transformation logic in a staging environment against a representative data sample before full production extraction.

  4. Sandbox migration and reconciliation

    We run a full migration into a Jira Sandbox using production-equivalent data volume.

    What this step covers

    The customer's project manager and Jira admin reconcile record counts (Issues in, Subtasks in, Work Logs in), spot-check 25-50 randomly selected issues against ClickUp source records, verify status and Custom Field mapping accuracy, and validate subtask hierarchy. Sign-off on the sandbox migration is required before production migration begins. Any mapping corrections are made in the staging environment, not in production.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Jira Projects and Components first, then Issues by type (Epics before Stories, Stories before Tasks), followed by Subtasks, Work Logs, Comments, Attachments, Labels, and Goals.

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. Parent record references (Issue ID, Project ID, Component ID) are resolved during import so that linked records attach to the correct parent. We use the Jira Bulk API with chunking and exponential backoff for large datasets.

  6. Cutover, validation, and automation rebuild handoff

    We freeze ClickUp writes during the cutover window, run a final delta migration of any records modified during the migration, then enable Jira as the system of record.

    What this step covers

    We deliver the Automation inventory document to the customer's admin team with Jira Automation equivalents documented for each rule. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild ClickUp Automations as Jira Automation rules inside the migration scope; that work is handled by the customer's admin or a separate automation scoping engagement.

ClickUp Jira
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · JiraRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
8-12 weeksLarge or heavily customised accounts

A quote scales with task volume, custom field count, and hierarchy complexity. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for ClickUp to Jira →

Why teams move from ClickUp to Jira

  • ClickUp's time tracking reporting is inadequate for software teams. Reviewers on Reddit and G2 describe ClickUp's native time reporting as 'HORRENDOUS,' noting that meaningful analysis requires spinning up a separate data warehouse and ingesting data via APIs. Jira's native Work Logs feed directly into sprint velocity reports, capacity planning, and billing reports without additional tooling, making the move worthwhile for engineering teams that track time against issues.
  • JQL gives engineering teams query power that ClickUp's visual filters cannot match. Jira's Jira Query Language supports Boolean logic, date comparisons, custom field filtering, and cross-project aggregation that software teams rely on for sprint reports, backlog grooming, and release tracking. ClickUp's filtering is described as 'fairly limited' by teams migrating back to Jira, particularly around subtask aggregation where ClickUp treats subtasks as separate disconnected records.
  • ClickUp's all-in-one feature density creates adoption friction that Jira's purpose-built interface avoids. A Reddit reviewer leading a 60-person software division described ClickUp's feature overload as 'lipstick on a pig,' noting that the sheer number of views, tools, and integrations felt overwhelming and counterproductive compared to Jira's structured, opinionated workflow model. Engineering teams with formal Agile processes prefer Jira's sprint ceremony support and developer toolchain integration.
  • ClickUp's performance degrades in large workspaces with complex hierarchies and hundreds of tasks. Multiple reviewers report sluggish load times and platform responsiveness issues when workspaces accumulate complexity, disrupting productivity for active engineering teams. Jira is architected to handle instances with hundreds of projects and tens of thousands of issues without comparable performance friction.
  • ClickUp Brain AI pricing at $9 per member per month is a separate add-on that inflates the true cost of entry significantly. For a 20-user engineering team, this adds $2,160 annually on top of base subscription costs. Atlassian Intelligence, which covers similar AI-assisted summarization and search capabilities, is bundled into Jira Premium at $14.54 per user per month without a separate add-on charge, making the effective AI cost lower at comparable tiers.

Questions, answered

ClickUp to Jira migration questions

How long does a ClickUp to Jira migration take?

Straightforward migrations with under 5,000 tasks and a single-level List structure typically complete in three to five weeks. Migrations with 20,000+ tasks, deeply nested subtask hierarchies, numerous Custom Fields across multiple Spaces, and legacy Docs content requiring manual review extend to eight to twelve weeks. The Jira importer rate limits (enforced per ClickUp plan tier) and the need to batch imports by List are the primary timeline drivers for large workspaces.

Do ClickUp Automations and Docs migrate to Jira?

ClickUp Automations do not migrate as executable code. Jira Automation is a separate rules engine with different triggers, conditions, and action types that cannot be directly translated from ClickUp Automations. We deliver a written inventory of every ClickUp Automation with its trigger, conditions, actions, and a recommended Jira Automation equivalent for your admin to rebuild post-migration. ClickUp Docs migrate as issue descriptions in plain text, but rich formatting, embeds, and styling may not fully preserve due to Docs API limitations. Standalone Docs should move to Confluence as a separate configuration task.

Can we migrate only specific Spaces or Lists rather than the entire workspace?

Yes. We scope migrations to specific Spaces and Lists during discovery. This is common when teams want to pilot Jira with one team's work before committing to a full workspace migration. We extract only the specified Lists, resolve parent-record dependencies (Spaces, Folders) for the selected scope, and migrate in priority order. Jira Projects can be created incrementally, so a pilot migration of two or three Lists can proceed while the rest of the workspace remains active in ClickUp.

How do we handle ClickUp Custom Fields that are scoped at different hierarchy levels?

ClickUp Custom Fields can be scoped at List, Folder, Space, or Workspace level with different inheritance behaviors. Jira has no equivalent workspace or Space-level scoping model; all Custom Fields are project-scoped. We export the full Custom Field schema including scope metadata, recreate fields at the Jira Project level, and map List-scoped fields to the appropriate Jira Project. Field type conversion (ClickUp person to Jira User Picker, date to Date Picker, dropdown to Select List) is performed during schema design. Fields without a Jira equivalent are documented for manual review.

Do we lose historical time tracking data during the migration?

No. We migrate ClickUp Time Entries as Jira Work Logs, preserving duration, tracking user, and billable flags where available. Work Log timestamps are set to the original ClickUp tracking date. Jira Premium enables native time tracking reports and capacity planning; Jira Standard supports Work Logs but requires data export for reporting analysis. We include a Work Log reconciliation phase in the migration to verify that all billable hours are accounted for.

How does the Jira issue type mapping work for ClickUp Lists?

ClickUp Lists are the primary work container in ClickUp and map to Jira Issue Types (Story, Task, Bug, Epic). During scoping, we review each List and determine the appropriate Issue Type based on the List's intended work type. Jira Projects require an Issue Type Scheme that defines which Issue Types are available. We pre-configure the Issue Type Scheme before migration so that all tasks from a given List land as the correct Jira Issue Type. One List maps to one Issue Type; Lists with mixed work types may require pre-migration reorganization in ClickUp.

What happens to ClickUp subtasks in Jira?

ClickUp subtasks become Jira Sub-Task issues linked to their parent Jira Issue. Jira Sub-Tasks have a fixed field set (summary, assignee, status, priority, description) and are displayed as collapsible children on the parent issue. ClickUp subtask-specific Custom Fields require separate Jira Sub-Task field configuration since Jira Sub-Tasks do not inherit parent Custom Fields by default. We document any subtask Custom Fields during scoping and configure them on the Sub-Task issue type during schema design. Subtasks appear in Jira sprint boards only if the board configuration explicitly includes the Sub-Task issue type.

Get a quote

Moving from ClickUp to Jira?

Tell us roughly how many records and objects you have. We scope the mapping and the Jira setup with you, then send a quote.

Get a quote