Jira → ClickUp
Move Jira issues, epics, comments, attachments, and users into ClickUp with a Cloud backup zip, without treating the importer as a complete copy of priority, time logs, or private comments.
Should you make this move?
Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.
Jira
- Deep workflow, issue, permission, and reporting controls support complex organizations
- Structured ownership, status, and workflow views improve operational visibility
- Administration and process complexity can slow teams that need a lighter workflow
- Custom fields, automations, history, and reporting are difficult to reproduce exactly
ClickUp
- A wide feature set can replace several work-management tools
- Structured ownership, status, and workflow views improve operational visibility
- Density, configuration options, and performance can overwhelm teams seeking simplicity
- Custom fields, automations, history, and reporting are difficult to reproduce exactly
ClickUp: A wide feature set can replace several work-management tools. This removes a major source-side concern: Administration and process complexity can slow teams that need a lighter workflow.
What you lose: Deep workflow, issue, permission, and reporting controls support complex organizations. What you inherit: Density, configuration options, and performance can overwhelm teams seeking simplicity.
Jump to a section
Know the shape of the move.
This timeline assumes
- Up to 40 Jira projects, 50,000 in-scope issues, and 300 users
- The team chooses the new zip importer or the Cloud-only legacy API importer before any destination write.
- Users exist in ClickUp, or get an invite, inactive, or unmatched decision, before assignment mapping.
- A representative project is imported and signed off before the remaining workspace.
- The migration team records evidence for every blocking verification check.
What survives the move.
“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.
| Item | Outcome | Impact | What happens | Mitigation |
|---|---|---|---|---|
| Jira Cloud backup used as the ClickUp zip | partial | critical | ClickUp's new importer uploads an unaltered Jira zip. Atlassian documents a 25 GB data-size target for Cloud backups and a 48-hour wait between backups that include attachments. ClickUp rejects a zip that someone has edited, and it caps the upload at 50 GB. | Create the Cloud backup from Backup manager. Keep entities.xml at the zip root. Split large sites into project batches. |
| Issue keys and descriptions | partial | critical | ClickUp writes the Jira ID into a long-text Custom Field named Jira ID. Description attachments become comments. Links to other issues inside the description do not import. | Keep the Jira ID field visible. Rebuild issue links from a key ledger after the load. |
| Epics, stories, and other issue types | partial | critical | The importer asks you to put epics as parent tasks with stories as subtasks, or to put epics and stories in two Lists and link them. Items that are neither epic nor story go to a Non-Epics List in the first mode. Nested Subtasks turns on automatically. | Pick one hierarchy before you map statuses. Pilot an epic tree and a non-epic bug in the same run. |
| Priority, timestamps, and recurring work | lost | critical | ClickUp says the Priority field, timestamps, and recurring tasks do not import. | Export priority and due-time evidence from Jira. Recreate recurrence in ClickUp after intake moves. |
| Custom fields | partial | high | Built-in Jira fields of type Dropdown, Labels, Text, Number, Date, URL, and User can map. User-defined custom fields cannot. Dates must be mm/dd/yyyy. The mm-dd-yyyy form will not import. Built-in Label fields become Tags. Other label fields become Label Custom Fields. | List every field and mark built-in, user-defined, or exclude. Convert dates before you rely on the zip. |
| Comments, privacy, and attachments | partial | critical | Comments keep authors. Private comments become public in ClickUp. Attachment authors import. Each imported file has a 1 GB limit. Links to tasks inside comments do not import. | Inventory private comments before the zip leaves Jira. Open a sample of files as ordinary ClickUp users. |
| Time spent on issues | lost | high | ClickUp assigns all Jira time spent to the person who runs the import. It tells you to write the original author and hours on each issue first. | Export work logs. Paste the original author and hours into a Jira note or a ClickUp field before anyone trusts reports. |
| Assignees, reporters, and followers | partial | critical | You map each Jira user to an existing ClickUp user, an invite, or an inactive user. Reporters and Jira followers become ClickUp followers. Unmapped people lose assignment. | Finish the user sheet before import. Leave unmatched work unassigned and keep the Jira address on the task. |
| Boards, sprints, automation, and apps | lost | high | Atlassian can include board and sprint data in a Cloud backup. Those objects do not become ClickUp Sprints, Dashboards, or Automations. Automation flows and third-party app data cannot leave Jira Cloud in the backup. | Rebuild only the boards and rules people use weekly. Keep Jira read-only for historical sprint charts. |
| Cloud versus Data Center versus the legacy importer | manual | critical | The new importer accepts Jira Cloud or on-prem Jira Software through a zip. The legacy importer talks to Jira Cloud over an application link at https://clickup.com/jira and cannot import on-prem sites. | Confirm Cloud or Data Center, then pick one importer. Do not mix a zip load with a live API load on the same project. |
| Live Jira writers after ClickUp intake starts | partial | high | The zip is a point-in-time copy. ClickUp also offers Jira Sync if you want both tools to keep writing. A one-shot import and a live sync will diverge. | Choose one mode. If you import once, freeze Jira writers. If you keep sync, document which fields still flow. |
Where each thing goes.
| Source | Destination | Method | Notes |
|---|---|---|---|
| Jira project | ClickUp Space, Folder, and Lists from the hierarchy choice | transform | Import one or a few projects per batch. |
| Issue key | Jira ID Custom Field | automatic | Keep this field on every List view. |
| Summary and description | Task name and description | transform | Description files become comments. Rebuild issue links. |
| Epic and story | Parent task plus subtask, or two related Lists | transform | The choice also locks later status mapping. |
| Status | ClickUp status | transform | Map after you pick the epic layout. |
| Assignee, reporter, or follower | Assignee or follower | manual | Reporters become followers. Unmapped users stay blank. |
| Built-in custom field | Matching ClickUp Custom Field or Tag | transform | User-defined fields stay out. |
| Comment or attachment | ClickUp comment or file | transform | Private comments become public. |
| Priority, work log, or recurring issue | No destination | unsupported | Archive the Jira values. Recreate recurrence later. |
Make the move recoverable.
Create the source-of-truth backup
Preserve Jira work, comments, files, users, and configuration before any ClickUp write.
- Create a Jira Cloud backup from Backup manager. Include work items, comments, and media. Allow 48 hours between attachment backups.
- Export in-scope issues as CSV or JSONL with keys, statuses, users, links, priority, and work logs.
- Inventory projects, issue types, workflows, required fields, boards, sprints, automation, and apps.
- Hash every export and keep a user reconciliation sheet. Do not edit the zip you will upload.
Proof to capture: A signed manifest reconciles every scoped issue class, export file, count, and hash.
Hierarchy, field, and user map
Decide epic layout, field fate, and people before the zip lands.
- Choose epics-as-parents or epics-and-stories-as-related-Lists.
- Mark each field as built-in map, archive, or exclude.
- Match users by email, then name, then invite or inactive.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
Batched zip import
Load projects without a 50 GB failure or a silent priority drop.
- Upload an unaltered zip and confirm the scanned user, project, issue, and attachment counts.
- Import one or a few projects, then reconcile Jira IDs before the next batch.
- Write original work-log authors onto tasks before anyone reports on time.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
The things most likely to hurt.
These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.
Private comments become public
ClickUp imports private Jira comments as public comments.
- Consequence
- Restricted discussion becomes visible to people who should not see it.
- Mitigation
- Scan private comments in Jira first. Hold those issues out of the zip or strip them before you invite the wider team.
Stop if: A private thread is visible to an unauthorized ClickUp member.
The zip is too large or someone edited it
ClickUp stops if the file is over 50 GB or if the zip was altered.
- Consequence
- The load fails halfway and counts no longer match Jira.
- Mitigation
- Delete unused projects and oversized files before export. Import in batches. Keep entities.xml at the top of the zip.
Stop if: Destination counts cannot explain every in-scope Jira key.
Both tools keep writing
Jira automation and ClickUp Automations both act on the same work, or Jira Sync stays on after a one-shot import.
- Consequence
- Statuses diverge and comments duplicate.
- Mitigation
- Freeze Jira writers and disable source rules before ClickUp owns intake.
Stop if: An unapproved Jira writer remains active.
Do the work in this order.
- Days 1–4 · inventory
Inventory and mode choice
8–16 hours active3–4 days elapsedOwner review waiting- Inventory Jira projects, types, fields, users, rules, and apps.
- Choose the zip importer or the legacy API path, and approve what stays in Jira.
Depends on: Jira and ClickUp administrator access
Stop / go checkpointExport?
Go when: Every critical item has an owner and disposition.
Stop when: Cloud versus Data Center, private comments, or consent is unclear.
- Days 4–8 · backup
Backup and reconcile
6–14 hours active2–4 days elapsedBackup processing waiting- Create the Cloud backup and issue exports.
- Reconcile counts, hashes, work logs, and the user sheet.
Depends on: Approved inventory
Stop / go checkpointTransform?
Go when: Source totals and the unaltered zip agree.
Stop when: Any critical project, comment class, or attachment set is absent.
- Days 8–20 · pilot
Map and pilot
16–50 hours active6–12 days elapsedOwner review of the sample waiting- Load one project that includes an epic, a private comment, a former user, and a file.
- Compare keys, statuses, comments, and attachments.
Depends on: Verified backup
Stop / go checkpointScale?
Go when: Pilot mappings, access, and evidence pass.
Stop when: Any critical check fails or a count is unexplained.
- Days 18–32 · cutover
Final delta and switch
6–26 hours active2–6 days elapsedFinal import waiting- Freeze Jira writes and automation.
- Load the remaining projects, switch intake, and run blocking checks.
Depends on: Passed pilot and approved rollback
Stop / go checkpointOpen production?
Go when: Every in-scope key is accounted for and ClickUp owns intake.
Stop when: A Jira writer remains active or a blocking check fails.
- Days 22–45 · observe
Observe and close
4–18 hours active5–12 days elapsedOne planning cycle waiting- Watch one complete planning and delivery cycle.
- Sign the verification report before you close rollback.
Depends on: Verified cutover
Stop / go checkpointClose rollback?
Go when: No trigger occurs during the agreed observation period.
Stop when: Work, access, or reporting regresses.
Cut over with a way back.
Cutover
Make ClickUp the only intake system without losing the final Jira delta.
- Freeze Jira writes, automation, and new issue intake.
- Export and load the final changed issues, or a last project batch.
- Switch forms, email, and developer links to ClickUp.
- Run every blocking check and keep Jira readable.
- Keep the source intact through the rollback window.
Proof to capture: ClickUp owns intake, every in-scope Jira key is accounted for, and every blocking check has evidence.
Rollback
Return intake to Jira without losing ClickUp-era changes.
- Stop new writes and Automations in ClickUp.
- Restore Jira access, automation, and intake.
- Export the ClickUp post-cutover delta.
- Review and apply safe destination-era changes to Jira.
- Run the same blocking checks against Jira.
Proof to capture: Jira again owns intake with current work and no duplicate ClickUp action.
- Unexplained missing Jira keys
- A private comment visible to the wrong person
- Missing or exposed files
- Duplicate production action
- A critical workflow has no safe ClickUp replacement
Prove the migration worked.
Every blocking check must pass. Capture the evidence before cleanup begins.
| Pass | ID | Check | Method | Expected result | Evidence |
|---|---|---|---|---|---|
V-01Blocking | Issue reconciliation | Compare every in-scope Jira key to a ClickUp task, archive, or exclusion. | 100% of scoped keys are accounted for in the Jira ID field. | Key ledger. | |
V-02Blocking | Epics and children | Inspect representative epic trees in both importer layouts you considered. | Approved parent, subtask, or relationship links exist. | Hierarchy report. | |
V-03Blocking | Status mapping | Move sample tasks through every approved state. | ClickUp status matches the signed map. | Transition log. | |
V-04Blocking | Assignees and former staff | Test matched, invited, inactive, and departed users. | Assignments follow the sheet. Unmatched emails remain on the task. | User matrix. | |
V-05Blocking | Private comments | Open issues that had private Jira comments as an ordinary member. | Restricted threads are hidden, archived, or explicitly approved as public. | Privacy log. | |
V-06Blocking | Comments and files | Open decision-heavy issues and their attachments as ordinary users. | Required history and files work without a Jira login. | Context log. | |
V-07Blocking | Unsupported values | Sample priority, work logs, user-defined fields, and recurrence. | Each value is mapped, archived, or explicitly excluded. | Field exception list. | |
V-08Blocking | Single writer | Create and update a test issue after freeze. | Only ClickUp acts. Jira stays still. | Automation log. |
Remove the scaffolding safely.
Safe after: One complete sprint or planning cycle, at least seven stable days, and owner sign-off on every blocking check.
- Archive Jira backups, maps, and verification evidence.
- Revoke migration tokens and unused Jira application links to ClickUp.
- Remove obsolete Jira automation, webhooks, and apps.
- Keep Jira read-only through the approved retention window.
- Cancel paid Jira plans only after billing, legal, and recovery review.
- Schedule the next ClickUp backup, access, and playbook review.
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.
Gilad Navot wrote that Swimm tried GitHub Issues for six months, then Jira for three, then ClickUp. They ship weekly minors, ten minors in a major, and needed version folders plus a release-note list. Jira sprints felt like the wrong unit. They spent time moving issues between sprints instead of finishing work, and bulk delete was awkward. In ClickUp they put Engineering, Product, and Marketing in Spaces, used a Folder per major or minor version, and templated Bugs & Features, R&D Internal, and Product lists. The post explains the hierarchy they wanted. It does not describe a Jira zip import, comment privacy, or field mapping.
- Write the version and release-note hierarchy on paper before you import, because ClickUp Spaces and Folders are how Swimm replaced Jira sprints.
- Treat this post as a process choice. Still pilot ClickUp's zip importer on one project if you need historical Jira keys and comments.
- Swimm left Jira because sprint mechanics fought their milestone planning, not because a bulk importer failed.
- Templates for each version folder mattered more to them than matching Jira's issue types one for one.
Unito's Verivox case study quotes QA lead Martin Hoffmeister on moving 50,000 active Jira tickets across 40 projects into ClickUp for a 300-person Heidelberg company. The tickets still needed work every hour, so a freeze-and-export path was not acceptable. ClickUp pointed them at Unito after they judged a manual export too large. Hoffmeister says Zapier field matching was too coarse, and Unito could drop unmatched Jira fields into the ClickUp task footer for later cleanup. Unito publishes $104k cost savings and 1,200 hours saved. This is a vendor-published interview, not an independent import study, and the dollar and hour figures are Unito's.
- If issues stay live during the move, plan a sync or footer-field path instead of a one-shot zip, and label vendor time-saved claims as the vendor's.
- Map leftover Jira fields to a visible footer or Custom Field so unmatched values remain recoverable after cutover.
- The quoted reason for Unito was a soft migration of active tickets, not ClickUp's native zip importer.
- Unito's 50,000-ticket and 1,200-hour figures are the vendor's published results for Verivox.
Verify against the primary material.
Platform behavior changes. Check these sources and the review dates above before executing a production migration.
- ClickUp: import from JiraAccessed 2026-10-26
- Atlassian: export data from Jira CloudAccessed 2026-10-26
- ClickUp: import from Jira (legacy)Accessed 2026-10-26