Importing your data

Where

Administration, Imports, New import. Only system administrators import. Each import is a session you can leave and reopen from the list.

Sources and what they need

• Jira Cloud: site address, account e-mail and API token
• Jira Server / Data Center: site address and a personal access token (Jira 8.14 and later) or username and password
• ClickUp: a personal API token
• Asana: a personal access token
• monday.com: a personal API token
• Microsoft Planner: an application registered in your Entra ID (tenant, client ID and client secret)
• OpenProject: site address and an API key, on premises or cloud
• Redmine: site address and an API key
• CSV: the file itself, up to 50 MB and 100,000 rows; one file becomes one project. A template file can be downloaded on the screen

The token's account must see everything you want to bring over; use an administrator's account where you can. Tokens are stored sealed and never shown again. A site address is refused if it is a loopback, private or link-local address, or if its name leads to one; names ending in .local or .internal are refused as well, and so is any port other than 80, 443 or one above 1023. This decides whether a Jira Server / Data Center, OpenProject or Redmine you run yourself can be read: one that answers only on such an internal address cannot be imported.

The steps

1. Connection: tested before anything is saved
2. Projects and space: pick the source projects (or boards, plans, lists) and a new or existing space
3. Preview: what the source holds, every custom field and where it lands, and what is not carried over. Nothing is written before this
4. People: each person is matched to an account with the same e-mail, created without product access, or left out (their name stays on the work as text)
5. Matching: types, statuses and fields, matched to existing ones by name or created new
6. Write configuration: the space, projects, types, statuses, fields with options, versions, components and link types. Undo the configuration is available until the first work item comes over
7. Run: work items move in the background with progress, and can be stopped after a page
8. Access: the accounts this import created have no product access yet; they are listed, ticked up to the free licence seats, and given access in one go

What moves

• Jira: summaries, descriptions, comments, attachments, work logs, watchers, sprints, epics with colours, parents, links, custom field values, story points, start and due dates, versions and components; workflows, roles and boards; for service projects, request types, customers and organisations. Jira Server does not expose workflow arrows, so its workflows arrive with every status leading to every other
• ClickUp: tasks with subtasks, statuses, priorities, assignees and watchers, tags, dates, estimates, tracked time as work logs, attachments, comments with replies, dependencies; board views become boards
• Asana: tasks with subtasks of any depth, sections as statuses, assignee, collaborators, tags, dates, actual time, attachments, comments and dependencies
• monday.com: items with sub-items, status labels as statuses, groups as components, people, dates, timeline, tags, files, updates as comments and dependencies
• Microsoft Planner: tasks, buckets as statuses, progress, priority, assignees, labels, dates, and notes, checklist and references in the description
• OpenProject and Redmine: work packages or issues with types or trackers, statuses, priorities, people, categories as components, versions as releases, dates, estimates, time entries as work logs, attachments, comments, relations, watchers and parents
• CSV: columns place themselves by name (a Jira, ClickUp, Asana or Excel export works as it is): key, summary, description, type, status, priority, people, dates, labels, components, version, parent, estimate, time spent, story points, watchers and comments

Not carried over

Dashboards, automation rules, saved filters, notification schemes, the quick filters and JQL swimlanes of boards, and SLA policies, which are set up again on the Help Desk's SLA page. Each source's preview lists its own exceptions, such as wikis, forms or whiteboards. A CSV carries no history, attachments, workflow arrows or sprints.

Running again

Run the same import again to bring over what changed since the last run. A run that was stopped by hand or cut short does not resume by itself; run the import again and it carries on from where it ended. Importing the same project in a new session makes a second copy, so reuse the session instead.