Migrate from ClickUp to Jira

ClickUp Workspace maps to the Jira Cloud Site as the top-level organizational container. 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.

ClickUp Space maps to a Jira Project as the primary work container. 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.

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). 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.

ClickUp Lists map to Jira Issue Types (Story, Task, Bug, or Epic) based on the List's intended work type. 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.

ClickUp Tasks map directly to Jira Issues with the Issue Type determined by the parent List mapping. 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).

ClickUp Subtasks map to Jira Sub-Task issues linked to their parent Jira Issue. 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.

ClickUp Custom Fields (dropdown, date, number, person, rating, relationship, and other types) map to Jira Custom Fields of equivalent type. Field type conversion is required: ClickUp person fields become Jira User Picker, date fields become Date Picker, and dropdowns become Select Lists. Location-dependent scoping (List-level vs Space-level fields) is resolved by recreating fields at the Jira Project level. Multi-select dropdowns map to Jira Multi-Select Field. Fields scoped at ClickUp Workspace level require project-level recreation in Jira since no workspace-scoped field equivalent exists.

ClickUp Goals with measurable targets linked to tasks map to Jira Goals (available on Jira Software Premium and Enterprise) or are reconstructed as a custom tracking approach using Jira Issues linked to a parent Goal Epic with target dates and progress fields. Goal metrics and key results migrate as custom fields on the Goal issue. Teams on Jira Standard recreate Goal tracking as Epics with linked child issues and progress calculated manually.

ClickUp Docs attached to tasks migrate as issue description content (plain text with available formatting preserved). The Docs API does not fully preserve rich formatting, embeds, and styling, so complex Docs may require manual post-migration review to restore visual fidelity. Standalone Docs that are not task-attached should move to Confluence as a separate setup and are documented separately for the customer's admin to configure post-migration.

ClickUp Time Entries map to Jira Work Logs on the corresponding Issue. We preserve duration (in seconds), the tracking user, and the billable flag where available. Work Log timestamps preserve the original ClickUp tracking date. Jira Premium enables time tracking reports and capacity planning directly; Standard supports Work Logs without native reporting, requiring a data export for analysis.

ClickUp Tags, which are workspace-level labels applied to tasks across all Lists, map to Jira Labels on Issues. Labels in Jira are project-scoped by default but can be configured org-wide. We preserve the tag vocabulary and all task-to-tag associations as Jira Labels during import.

File attachments on ClickUp tasks migrate as Jira Issue Attachments. Attachment metadata (filename, author, upload timestamp) is preserved. ClickUp's 1GB per-attachment limit on import is noted; Jira Cloud supports larger attachments but we flag any attachment that approaches or exceeds this threshold during scoping.