migrating toBrowse playbooks
← All playbooks
Project management migration

ClickUp → Jira

Move ClickUp Lists into a new Jira space with Atlassian's ClickUp importer. The importer takes up to 10 Lists, always creates a new space, and cannot merge into a board you already built. Custom fields and statuses in Jira are shared, so a ClickUp-shaped workspace will not land as-is.

Typical timeline8–18 business days30–60 hours active work
Statusneeds review
Source profileClickUp documentation reviewed 2026-10-30
Destination profileJira documentation reviewed 2026-10-30
Documentation date
Review window
Evidence4 sources
This route needs review.Use it as a planning baseline, then verify the dated sources and test with representative data before production.
Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

ClickUp

Reasons to stay
  • A wide feature set can replace several work-management tools
  • Structured ownership, status, and workflow views improve operational visibility
Reasons to leave
  • Density, configuration options, and performance can overwhelm teams seeking simplicity
  • Custom fields, automations, history, and reporting are difficult to reproduce exactly
New platform

Jira

What gets better
  • Deep workflow, issue, permission, and reporting controls support complex organizations
  • Structured ownership, status, and workflow views improve operational visibility
What gets worse
  • Administration and process complexity can slow teams that need a lighter workflow
  • Custom fields, automations, history, and reporting are difficult to reproduce exactly
Best of the move

Jira: Deep workflow, issue, permission, and reporting controls support complex organizations. This removes a major source-side concern: Density, configuration options, and performance can overwhelm teams seeking simplicity.

Worst of the move

What you lose: A wide feature set can replace several work-management tools. What you inherit: Administration and process complexity can slow teams that need a lighter workflow.

Connected catalog

3 destinations are documented from ClickUp. Compare nearby routes before committing.

Also from ClickUp
Jump to a section
01At a glance

Know the shape of the move.

Transfer outcome12 features audited
Transfer outcome distributionClean transfer: 0, Partial transfer: 8, Manual rebuild: 2, Not transferred: 2.
Clean0
Partial8
Manual2
Lost2
Mapping route8 of 9 fields have a destination path

This timeline assumes

  • Up to 20,000 active tasks across Lists you can import in batches of 10
  • A Jira admin can create spaces. Non-admins cannot move users into the new space.
  • Users already exist on the Jira site, or an org admin will invite them before import.
  • You accept a new Jira space per import. Software spaces land on a Kanban template.
  • ClickUp stays readable until one full sprint or intake week on Jira.
02What transfers

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

ItemOutcomeImpactWhat happensMitigation
Lists per importpartialcriticalAtlassian says the ClickUp importer can bring up to 10 Lists at once. You pick Workspace, Space, then Lists. A new Jira space is created for that run.Batch Lists by team. Record which Lists are in each run.
New space onlymanualcriticalThe importer creates a new space. It will not load into an existing Jira project you already configured.Do not pre-build the destination board if you plan to use the importer. Merge later only with a signed plan.
Work items, assignees, and mentionspartialcriticalYou can import user data such as assignees, mentions, and people. App admins can only move users who already exist on the site. New users need an org-admin invite first. Imported members get no notification.Invite users first. Pilot one List with every assignee class.
StatusespartialhighThe Review details screen shows how ClickUp statuses map to Jira. Jira statuses are tied to work types and are often shared. Per-list ClickUp statuses will not stay private.Approve a status map. Do not recreate every ClickUp status as a global Jira status.
Custom fieldspartialhighStandard and custom ClickUp fields can be mapped. In Jira those fields are often visible beyond the imported space.Map only fields you are willing to share. Use labels for the rest.
Hierarchy: Spaces, Folders, Lists, tasks, subtaskspartialcriticalClickUp hierarchy is not Jira hierarchy. The importer summarizes structure on Review details. Folders and multi-list tasks need a rule.Pick one List as the source of truth for tasks that appear in several Lists.
AttachmentspartialhighThe importer can include attachments. Failures show in the error log Atlassian emails at the end of a partial import.Turn attachments on for the pilot. Download the error log if the bar is not 100%.
Comments, docs, whiteboards, and automationspartialhighTask comments may move with the importer. ClickUp Docs, Whiteboards, Dashboards, Goals, and Automations do not become Jira configuration.Export Docs separately. Rebuild automations as Jira rules after intake works.
Time tracking, priorities, and viewslostmediumClickUp time estimates, custom views, and many priorities will not become Jira time remaining or saved filters.Export time reports from ClickUp if billing depends on them.
CSV fallbackpartialhighA raw ClickUp CSV into Jira often breaks subtask links and status mapping. That is why Atlassian ships a direct importer.Use the ClickUp importer first. Treat CSV as a last resort with a parent-then-subtask load.
Permissions and private ListsmanualcriticalJira space access is not ClickUp sharing. Private Lists can become visible to the new space's members.Set space access before import. Use issue security if private work must stay private.
History and activitylostmediumClickUp activity charts and assigned-comment history do not become Jira history.Keep ClickUp as the archive.
03Field and feature mapping

Where each thing goes.

SourceDestinationMethodNotes
ClickUp ListWork items in a new Jira spaceautomaticAt most 10 Lists per run.
Task nameJira SummaryautomaticSummary cannot be empty.
Task descriptionJira DescriptiontransformCheck mentions and embedded tasks.
StatusJira status on the Kanban templatetransformApprove the map on Review details.
Assignee and people fieldsJira assignee and people fieldsmanualUsers must already exist on the site.
SubtaskJira subtasktransformPilot parent and child in the same batch.
Custom fieldJira field or labeltransformAvoid creating global fields you will regret.
AttachmentJira attachmentautomaticDownload the error log if any fail.
ClickUp Doc, Dashboard, or AutomationNo destinationunsupportedRebuild after the space works.
04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Keep a ClickUp workspace export and a List inventory before Jira writes.

  1. Export the Workspace from ClickUp.
  2. Record List, task, assignee, and attachment counts.
  3. Screenshot private Lists and automations.
  4. Invite required Jira users before import.
  5. Store the export with a checksum.

Proof to capture: Dated export hash, List inventory, and user invite list.

Transformation · Jira Spaces → Create space → Import data → ClickUp

Direct ClickUp import

Create a new Jira space from up to 10 Lists.

  1. Connect the ClickUp workspace.
  2. Select Space and up to 10 Lists.
  3. Create the new Jira space and review field, status, member, and attachment maps.
  4. Let the import run in the background. Refresh the space when it finishes.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · Jira space access plus a field ledger

Exception and private-work handling

Keep private Lists and unmapped fields from leaking.

  1. Set space access before people start working.
  2. Move leftover Lists in later batches of 10.
  3. Record every field that became a label or was dropped.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Import

You import into a space you already built

criticalpossible likelihood

The team configured workflows first, then learned the importer needs a new space.

Consequence
Two incomplete projects and a merge you did not plan.
Mitigation
Import first, then adjust the new space.

Stop if: The only acceptable destination is an existing production project.

Users

Assignees come through as unassigned

highpossible likelihood

A non-admin ran the import, or users were not invited.

Consequence
Every user field is empty and mentions become plain text.
Mitigation
Invite users first. Use an admin for member import.

Stop if: A pilot List loses assignees you still need.

Setup

ClickUp statuses become global clutter

highpossible likelihood

Someone recreates every per-list status in Jira.

Consequence
Other Jira teams see statuses they never asked for.
Mitigation
Reuse existing statuses. Put extra states in labels.

Stop if: The status map would change unrelated projects.

Access

Private Lists become team-visible

criticalpossible likelihood

The new space is open and a private HR or exec List was in the batch.

Consequence
Restricted work is visible to the wrong people.
Mitigation
Exclude private Lists until issue security exists.

Stop if: A restricted List is in the selected batch.

06Precise timeline

Do the work in this order.

Estimate forUp to 20,000 tasks, imported in batches of 10 Lists
Total elapsed8–18 business days
Active work30–60 hours
BufferAdd time if you must merge into an existing Jira project, or if Docs and automations are in scope.
01
Days 1–3Inventory Lists and users2–3 days
02
Days 3–5Export ClickUp1–2 days
03
Days 5–10Import one representative batch3–5 days
04
Days 10–15Import remaining Lists and switch intake2–4 days
05
Days 15–18Observe one cycle3–5 days
  1. Days 1–3 · inventory

    Inventory Lists and users

    6–10 hours active2–3 days elapsedOwner review waiting
    • List Spaces, Folders, Lists, and private areas.
    • Invite Jira users.
    • Decide batch order.
    Stop / go checkpoint

    Import the first batch?

    Go when: Every in-scope List has a batch and an access rule.

    Stop when: A private List has no security plan.

  2. Days 3–5 · backup

    Export ClickUp

    3–6 hours active1–2 days elapsedWorkspace export waiting
    • Export the Workspace.
    • Record counts.
    • Screenshot automations and Docs.

    Depends on: inventory

    Stop / go checkpoint

    Pilot?

    Go when: The export hash and counts exist.

    Stop when: The export is incomplete.

  3. Days 5–10 · pilot

    Import one representative batch

    8–20 hours active3–5 days elapsedImporter waiting
    • Import up to 10 Lists into a new space.
    • Check assignees, subtasks, attachments, and privacy.
    • Download the error log if needed.

    Depends on: backup

    Stop / go checkpoint

    Continue batches?

    Go when: Pilot mappings and access pass.

    Stop when: Assignees, hierarchy, or privacy fail.

  4. Days 10–15 · cutover

    Import remaining Lists and switch intake

    8–16 hours active2–4 days elapsedLater batches waiting
    • Freeze ClickUp intake on moved Lists.
    • Run remaining batches.
    • Point forms and Slack at Jira.

    Depends on: pilot

    Stop / go checkpoint

    Jira owns new work?

    Go when: Counts reconcile and one tracker owns intake.

    Stop when: A source List is still taking production work.

  5. Days 15–18 · observe

    Observe one cycle

    5–8 hours active3–5 days elapsedOne sprint or intake week waiting
    • Watch workflow, permissions, and automations.
    • Keep ClickUp read-only.

    Depends on: cutover

    Stop / go checkpoint

    Close rollback?

    Go when: No trigger fires through one cycle.

    Stop when: Access or intake regresses.

07The point of change

Cut over with a way back.

Go live

Cutover

Make Jira the only intake system for the moved Lists.

Recommended window: A weekend or sprint boundary with a Jira admin present.

  1. Freeze new tasks on in-scope ClickUp Lists.
  2. Import the final delta batch.
  3. Reconcile task counts, assignees, and attachments.
  4. Switch forms, Slack, and Git links to Jira.
  5. Keep ClickUp read-only.

Proof to capture: Jira owns intake. Counts match. Private Lists stay private.

Return to safety

Rollback

Return intake to ClickUp without losing Jira-era work you still want.

Deadline: Before you delete the ClickUp Workspace or the export.

  1. Stop Jira intake.
  2. Reopen the ClickUp Lists.
  3. Export Jira items created after cutover.
  4. Apply only reviewed items back to ClickUp.
  5. Run the same access checks on ClickUp.

Proof to capture: ClickUp owns intake. Jira is not receiving new production work.

Rollback immediately when
  • Assignees missing on a critical List
  • Private work visible to the wrong people
  • Subtask hierarchy broken on active delivery
  • Importer error log unexplained
  • A blocking check cannot be fixed in one business day
08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

0%
Interactive report preview0 / 8 checks passed
PassIDCheckMethodExpected resultEvidence
V-01BlockingList coverageCompare the List inventory with Jira spaces.Every in-scope List is in a finished batch or a signed exception.Batch ledger.
V-02BlockingTask countsCompare ClickUp open tasks with Jira work items.Counts match or variances are signed.Count sheet.
V-03BlockingAssigneesSample tasks that had ClickUp assignees.Users exist and are assigned.Assignee sample.
V-04BlockingSubtasksOpen parent tasks that had subtasks.Children remain linked.Hierarchy sample.
V-05BlockingPrivate ListsOpen a private List as an unauthorized user.No leak.Access test.
V-06BlockingAttachmentsOpen a sample of files from the error log and from successes.Required files open.Attachment sample.
V-07Status mapMove a pilot item through the new board.Statuses match the signed map.Workflow notes.
V-08BlockingSingle intakeCreate a new request in each old form.Only Jira receives it.Intake test.
09Post-migration cleanup

Remove the scaffolding safely.

Safe after: One complete intake cycle, seven stable days, and a signed report.

  1. Archive the ClickUp export and importer error logs.
  2. Revoke the ClickUp OAuth grant used for import.
  3. Turn remaining ClickUp Lists to read-only.
  4. Keep ClickUp through the retention window.
  5. Rebuild only the automations you still need.
  6. Schedule the next Jira permission review.
10Experiences from the field

When the plan met reality.

First-hand accounts are preferred. Vendor case studies are labeled, and every note below is an editorial paraphrase—follow the link for the full context.

First-person accountWill Helliwell · The Productive Dad

I Spent Two Months Migrating to Jira2026

Will Helliwell spent two months moving a ClickUp workspace to Jira for his day job, not for The Productive Dad. The native importer required Jira admin rights and a brand-new project, so he could not land work in an existing board. Custom fields and statuses are workspace-global, so he skipped recreating ClickUp fields and used labels such as status-to_do. A plain CSV import broke subtask links and flattened statuses. He wrote Python to export parents, import them, re-export Jira keys, then import matched subtasks, and stuffed custom-field values and comments into descriptions.

What they recommend
  • Treat the native importer as a new-space-only path. Plan the merge into an existing Jira project as a second job.
  • Do not trust a one-shot CSV for subtasks. Import parents first, capture Jira keys, then attach children.
Worth noticing
  • Shared Jira fields and statuses can block a literal ClickUp rebuild in a large site.
  • Putting custom fields and comments into the description kept history readable when fields could not be created.
Sources and evidence

Verify against the primary material.

Platform behavior changes. Check these sources and the review dates above before executing a production migration.

  1. Jira: import data directly from ClickUpAccessed 2026-10-30
  2. Jira: import data into JiraAccessed 2026-10-30
  3. ClickUp: export Workspace dataAccessed 2026-10-30
  4. Jira: fix errors in a space importAccessed 2026-10-30