Imports

Bringing tickets, requests, pages, time and a CRM in from Jira, GitHub, GitLab, Trello, Asana, Linear, Zendesk, Confluence, other documentation tools, other time trackers, other CRMs and CSV files.

Everything that was tracked elsewhere can be brought in, under Administration, Imports. Each import keeps the original record of every row it reads, so nothing from the old system is lost, and running the same file again changes nothing. The steps for each are linked below, in the order of the modules. Moving a whole workspace between installations is Export and import.

Projects

Jira

Analyse and import a Jira Server, Data Center or Cloud backup: projects, tickets with their history, comments, attachments, custom fields, workflows, boards and sprints, and a Jira Service Desk's request types, queues and SLAs. See Importing from Jira.

GitHub and GitLab issues

Bring a repository's issues into a project, with their comments, labels, milestones and history. See Importing issues from GitHub or GitLab.

Trello, Asana and Linear

Bring a Trello board's cards, an Asana project's tasks or a Linear team's issues into a project as tickets from each tool's CSV export, with lists and sections as statuses and identifiers kept. See Importing from Trello, Importing from Asana and Importing from Linear.

A CSV file

Bring tickets in from a spreadsheet or any other tracker's export, one file into one project, with the columns mapped on screen. See Importing from a CSV file.

Helpdesk

Zendesk

Bring Zendesk tickets into a helpdesk project, keeping their numbers, requesters, statuses and dates. See Importing from Zendesk. A Jira Service Desk comes across with its Jira import.

Knowledge base

Confluence

Bring Confluence spaces into the knowledge base from a space or site export, from Confluence Cloud, Server or Data Center: pages in every version, folders, blog posts, comments, files, labels, restrictions and the addresses pages had, verified against the export. See Moving from Confluence.

Documentation from other tools

Bring documentation from Notion, Obsidian, GitBook, Outline, MkDocs, Docusaurus or any folder of Markdown or HTML into a knowledge base space, from a ZIP, in the tree the tool showed it in and with its links and images working. See Moving documentation in. A space can also be read from a Git repository instead of imported; see Docs from Git.

Time

Activities from a CSV file

Bring time in from another tracker's CSV export: Clockify, Harvest, Timely or any CSV file with the columns. Each row becomes an entry of the person it names, in the time zone chosen on the form. See Importing time from a CSV file.

Toggl Track

Bring Toggl Track's exported files across, one per year, with nothing to map. See Moving from Toggl Track.

Elastic Time

Bring an Elastic Time account across whole from its JSON export: its people, its clients as customers with their contracts, label categories, projects and team members, its phases, every activity, and its invoice details. See Moving from Elastic Time.

CRM

HubSpot, Pipedrive and Salesforce

Bring companies, contacts, deals and their interactions from another CRM's CSV export, matched to the companies and contacts already here. See Importing from another CRM.