Migrate from Notion to Jira

Each Notion database maps to a Jira project. We extract the database name, description, and property schema as the project configuration baseline. The Jira project must be created before any issue import so that the project key is available for issue key generation. Notion databases that contain purely informational content (not actionable work items) may be better migrated as Confluence spaces or kept as reference pages outside Jira; we flag these during scoping.

Notion database rows map to Jira issues. The row title becomes the issue Summary field. We ask the customer during scoping to designate an issue type mapping per database (e.g., a Bug-tracking database becomes Jira Bug issues; a Task database becomes Jira Story or Task issues). Pages that are children of a parent page in Notion map to Jira sub-tasks under their parent issue.

Notion rich_text, title, and url property types map to Jira custom text fields. Short text properties become single-line text fields; long-form descriptions become Jira description or a multi-line custom field. We preserve the original property name as the custom field name and note any Notion property name that exceeds Jira's 255-character field name limit.

Notion select and multi_select properties map to Jira custom fields of equivalent type. We extract all Notion option labels (including color metadata) and create Jira custom field options in the destination. Jira's picker layout for options must be configured manually post-import if the customer wants grouped or reordered options.

Notion date properties map to Jira date picker or date-time custom fields. We preserve the original date value and timezone. Notion date properties with an end date component map to a Jira date-time range using two custom fields or a Jira due date plus a custom start date field.

Notion people properties map to Jira user picker fields. We resolve each Notion workspace user by email match against the Jira destination's user directory. Any Notion user without a matching Jira account goes to a reconciliation queue for the customer's admin to provision before record import resumes. Notion guest users may not have Jira accounts if the destination uses an external user management policy.

Notion number properties map to Jira number custom fields. Notion currency properties map to Jira currency custom fields if the Jira product edition supports them, or to number fields with a customer-specified currency label. We note the original currency symbol from Notion for reconciliation.

Notion checkbox properties map to Jira checkbox custom fields. A checked Notion checkbox becomes a checked Jira checkbox; unchecked maps to unchecked.

Notion relations link records across databases. Jira has no cross-project rollup aggregation, so we translate Notion relations into Jira issue links (blocks, is blocked by, relates to, clone). We extract the relation source and target record IDs, look up the corresponding Jira issue keys post-import, and create issue link records in Jira. Rollup fields that aggregated related record values have no direct Jira equivalent; we flag them for manual rebuild as Jira calculated fields or as part of a reporting layer.

Notion databases support table, board, gallery, list, timeline, calendar, and gantt views with independent filter, sort, and group configurations. Jira uses saved filters and board configurations (Scrum or Kanban) for equivalent functionality. We extract every Notion view definition with its filter logic and column configuration, and deliver a written inventory mapping each view to the recommended Jira filter JQL and board setup. The customer or Jira admin rebuilds filters manually because Jira's filter DSL differs from Notion's view builder.

Notion page body blocks (paragraphs, headings, lists, callouts, quotes, code blocks, toggles, dividers) are extracted and converted to Jira description content. Jira accepts HTML-formatted or Atlassian Document Format (ADF) content. We convert Notion block types to their nearest Jira ADF equivalents and flag any block type that cannot be represented (e.g., Notion toggles map to HTML details/summary with limited Jira renderer support). Image blocks are uploaded to Jira as attachments linked in the description.

Notion-hosted file and image blocks are extracted by URL from the block JSON, downloaded, and re-uploaded as Jira issue attachments. Notion imposes a 5 MB file upload limit on the Free tier and unlimited on paid tiers. Jira's default attachment limit is 10 MB per file on most plans. Files exceeding Jira's limit are flagged for the customer's admin to store externally and link.