Move a Notion database to GitHub Issues
Drop a Notion exportCSV, up to 1,000 issues
Export from Notion
- 1Open the database as a full page and select the ••• menu at the top right, then Export.
- 2Set Export format to Markdown & CSV. Turn on Include subpages only if you also want the page files; this page reads the CSV alone.
- 3Select Export. Notion downloads a ZIP; unzip it and open the .csv file named after your database (use the one ending in _all.csv if there are two).
- 4Notion's export has no comments (they only come out in the HTML format) and no attachment files.
Import into GitHub Issues
- 1Select Continue in importer above, or open the CSV to GitHub Issues importer and drop the downloaded CSV.
- 2Sign in with GitHub and pick the repository.
- 3Match Notion people to GitHub logins, then import.
Field mapping
| Notion | GitHub Issues | What changes |
|---|---|---|
| Name | Title | Unchanged. |
| Name | Dedupe marker | Converted by a rule specific to Notion. |
| Notes | Body | Unchanged. |
| Status | State | Done and closed states close the issue. Everything else stays open. |
| Assignee | Assignee | Converted by a rule specific to Notion. |
| Tags | Labels | Split into a list at ",". |
| Priority | Labels | Converted by a rule specific to Notion. |
| Created time | Created date | Converted by a rule specific to Notion. |
| Page bodies (they are in the ZIP's .md files, which this page does not read; long text in a property comes across) | Not moved | Stays in Notion. |
| Comments (Notion exports them only in the HTML format) | Not moved | Stays in Notion. |
| Attachment files and images hosted by Notion | Not moved | Stays in Notion. |
| Relations as links (a related page is written as its title and Notion URL) | Not moved | Stays in Notion. |
| Sub-items and sub-pages as structure (each row is its own issue) | Not moved | Stays in Notion. |
| Anyone after the first in a Person property, and the time of day on a due date | Not moved | Stays in Notion. |
| Change history | Not moved | Stays in Notion. |
FAQ
Does my Notion export leave my browser?
No. The file is read and converted in your browser, and nothing is uploaded. Only when you continue in the importer and sign in with GitHub do the converted issues go through Gitsu's server to GitHub, and Gitsu keeps no copy.
Are comments and attachments moved?
No. Notion exports comments only in its HTML format, so the Markdown & CSV export has none, and it does not include attachment files. Images hosted by Notion are not carried either.
What happens to sub-items and sub-pages?
Each row becomes its own GitHub issue. A sub-item or relation column is written at the end of the issue body as the related page's title and Notion link, so the connection stays readable. No GitHub sub-issue links are created.
What about page content inside each row?
This page reads the CSV, so it carries the database properties, including a long text property such as Notes. The text written inside a page itself sits in the .md files of the ZIP, which this page does not read yet.
How many Notion rows can I import?
The importer takes up to 1,000 issues at a time. Past that, split the CSV into parts and import them one after the other.
Where do statuses, tags and priorities go?
A Done or Complete status imports the issue closed, and every other status stays open. Tags become labels, Priority becomes a label such as "Priority: High", and the first person becomes the assignee. Due date, relations and every other property are written at the end of the issue body.
Run your new GitHub issues in Gitsu.
Try Gitsu free