GitsuGitHub-native issue tracking for you and your agents.Try Gitsu free

Move ClickUp tasks to GitHub Issues

  1. 1Drop file
  2. 2Map fields
  3. 3Continue in importer
Your export never leaves your browser.
Drop a ClickUp exportCSV, up to 1,000 tasks per import

Export from ClickUp

  1. 1In ClickUp, open your avatar, then Settings, then Imports / Exports, and choose Export Items.
  2. 2Select the Spaces, Folders or Lists to export, then Start Export. Download the CSV from the page or from the email ClickUp sends.
  3. 3Drop the file into the converter above. A List or Table view export (Customize, Export, All columns, CSV, Date Format ISO, Subtasks on) also works and adds your custom fields.

Import into GitHub Issues

  1. 1Select Continue in importer above, or open the CSV to GitHub Issues importer and drop the downloaded CSV.
  2. 2Sign in with GitHub and pick the repository.
  3. 3Match ClickUp people to GitHub logins, then import.

Field mapping

ClickUpGitHub IssuesWhat changes
Task NameTitleUnchanged.
Task Content, Checklists, Attachments, Subtask IDs, Assignees, Due date, Start date, Date created Text, Due date Text, Start date Text, Time Estimated, Time Spent, Rolled Up Time, Rolled Up Time Text, Assigned CommentsBodyConverted by a rule specific to ClickUp.
StatusStateDone and closed states close the issue. Everything else stays open.
TagsLabelsSurrounding brackets are removed.
PriorityLabelsConverted by a rule specific to ClickUp.
AssigneesAssigneeSurrounding brackets are removed.
Date createdCreated dateConverted by a rule specific to ClickUp.
CommentsCommentsConverted by a rule specific to ClickUp.
Task IDDedupe markerUnchanged.
Task LinkSource linkUnchanged.
Attachment files (links are kept in the body)Not movedStays in ClickUp.
Sub-tasks as linked issues (ids are listed in the parent)Not movedStays in ClickUp.
Checklists as live checkboxes beyond the textNot movedStays in ClickUp.
Status names other than done or not doneNot movedStays in ClickUp.
Closed date and last-updated dateNot movedStays in ClickUp.
Time tracking, rolled-up time and dependenciesNot movedStays in ClickUp.

FAQ

Does my ClickUp export leave my browser?
No. The file is read and converted in your browser, and nothing is uploaded. It leaves your browser only when you choose to import into a repository, and then only the rows you confirm go to GitHub through Gitsu's server. We keep no copy.
Are comments and attachments moved?
Comments are moved as GitHub issue comments, with the author's name and the original date, when your export has a Comments column. Attachment files are not moved. Each attachment's name and link are listed in the issue body, and those links only work for people who can still open them in ClickUp.
What happens to sub-tasks?
GitHub Issues has no sub-task field in a CSV import, so each sub-task becomes its own issue. The parent's issue lists its sub-task ids, and each sub-task's footer has a "Parent ID" line. Export the List or Table view with Subtasks switched on if your Workspace export leaves them out.
What if I have more than 1,000 tasks?
The importer takes 1,000 issues at a time. The converter reads a bigger file and warns you with the row count. Export one Space, Folder or List at a time, or split the file, and import the parts one after the other.
Which ClickUp export should I use?
Use Export Items from Settings, Imports / Exports. It includes comments, checklists and every task in the places you pick. The List or Table view export also works and adds your custom fields. Custom fields and anything else the converter does not know are written at the end of the issue body.

Run your new GitHub issues in Gitsu.

Try Gitsu free