Kodavara Guide
Migrate From Jira to ClickUp: Projects, Statuses and What Happens to Sprints
ClickUp has a native Jira importer for Cloud and on-premises Jira. It maps statuses, custom fields and users, but sprint data does not come across and some details need care. This guide covers what carries over, what does not, and how to plan a developer-friendly move.
Last reviewed October 2026. ClickUp changes often, so check ClickUp's help center for the latest. Written by Kodavara, an independent ClickUp Partner. Not published or endorsed by ClickUp.
What ClickUp Does Today
What You Can Do Natively
Start with the features available on your ClickUp plan.
The Native Importer
It supports Jira Cloud and on-premises Jira. You choose which Jira projects to import and set up the hierarchy, and you can map statuses, custom fields and users.
What Comes Across
The Jira ID in a new text field, descriptions, subtasks, assignees, followers, dependencies and relationships, comments with their authors, and attachments with their authors.
Custom Field Types
Dropdown, labels, text, number, date, URL, user and status fields can transfer.
Size Limits Apply
There are limits on attachment size, and very large data sets may need ClickUp's help. Check ClickUp's current help page for the figures.
Where It Falls Short
The Gaps People Run Into
If these are your problem, keep reading.
- Sprint information does not come across on imported tasks.
- Private comments become public, so review them first.
- Time tracked is credited to whoever runs the import, so record who tracked what before you start.
- Attachments in descriptions become task comments.
- Workflows, automations, boards and permissions may not come across, so plan to rebuild them.
Worked Example
How Jira Concepts Map to ClickUp
Developers care about the details here, so the mapping is worth agreeing before the import.
| In Jira | In ClickUp | Note |
|---|---|---|
| Project | A Space, Folder or List, your choice | You set the hierarchy during import |
| Issue and sub-task | Task and subtask | Comments and attachments come with them |
| Issue key | A "Jira ID" text field | Keeps the old reference searchable |
| Epic | Decide: a task, or ClickUp's epic approach | Agree this before importing |
| Sprint | Not carried over | Rebuild in ClickUp Sprints |
| Status and custom field | Mapped during import | Supported field types only |
| Private comment | Becomes public | Review before importing |
| Time spent | Credited to the importer | Record who tracked what first |
Sample data for illustration.
The Configuration
How We Run a Jira Migration
Jira setups are often deeply customized. These are the phases we follow, and what you get at each one.
| Phase | What We Do | What You Get |
|---|---|---|
| 1. Discover | We inventory your Jira setup: projects, issue types, workflows, custom fields, epics and sprints, and your users. | A migration scope and a risk list |
| 2. Design | We design the ClickUp structure and write down how every source field, status and person maps. | A written mapping everyone agrees to |
| 3. Prepare | We tidy the source, then build the Spaces, fields and statuses in ClickUp. | A target that is ready to receive data |
| 4. Pilot | We import one or two real projects and check them task by task. | Fixes found before the full move |
| 5. Move | We run the full import and bring across anything the importer does not. | Your data in ClickUp |
| 6. Rebuild | We recreate your workflows, boards, automations and sprint practice in ClickUp, including how epics are handled in ClickUp. | Working processes, not just data |
| 7. Cut Over | We freeze the old tool, check for last-minute changes and switch the team on an agreed date. | A clean switch date |
| 8. Support | We train the team and fix what turns up in the first weeks. | A stable workspace |
How Kodavara Consulting Does It
Set It Up Once
We map your Jira configuration, run the import, rebuild sprints and workflows and look after your developers' habits.
Audit Your Jira Setup
List projects, issue types, workflows, custom fields, epics and what your team really uses.
Design the Mapping
Decide the hierarchy, map statuses, fields and users, and agree how epics and sprints are handled.
Handle the Sensitive Items
Review private comments, and record who tracked time before the import credits it all to one person.
Pilot, Then Import
Import one project, check every field, then run the full import and verify counts.
Rebuild Sprints and Workflows, Then Cut Over
Recreate sprint practice, workflows and automations, train the team and switch on an agreed date.
FAQ
Common Questions
Not here? Ask us.
Does ClickUp import from Jira?
Yes. There is a native importer for Jira Cloud and on-premises Jira, with mapping for statuses, custom fields and users.
Do sprints come across?
No. Sprint information does not come across on imported tasks, so sprint practice is rebuilt in ClickUp.
What happens to private comments?
They become public, so review them before you import.
Who gets credit for time tracked?
Time spent is credited to whoever performs the import, so record who tracked what in advance.
Can I keep the Jira issue keys?
Yes. The Jira ID is imported into a text field, so the old reference stays searchable.
Can you manage the migration?
Yes. We audit your Jira setup, design the mapping, pilot, import, rebuild sprints and workflows and support the cutover.
Keep Reading
Related Guides
Migrate From Asana
How to migrate from Asana to ClickUp: the native importer, what comes across, what does not, and a step-by-step plan for a clean switch.
Read the Guide →GuideHierarchy Design
How to design a ClickUp hierarchy that stays tidy: the levels, ClickUp's own guidance, why subtasks cannot have their own statuses, and agency setups.
Read the Guide →GuideWorkspace Migration
ClickUp cannot move tasks or Spaces between Workspaces natively.
Read the Guide →ServiceKodavara Consulting
The Kodavara service behind this guide: what we assess, configure and hand over.
Learn More →Want Help Setting This Up?
Tell us what you are trying to get done and we will point you at the fastest route.