Importing from other tools
Bring your existing project state into Taskachu without re-typing anything. Two paths today: boards/cards for tickets-style data, and documents for long-form pages.
Two import paths
Taskachu separates the importers because the underlying data is shaped differently. You can mix and match — most teams run the cards import once and pipe docs in as they go.
| Path | What it brings in | Where to start |
|---|---|---|
| Boards & cards | Tickets, sprint structure, statuses | Workspace Settings → Imports |
| Documents | Wiki pages, specs, runbooks, READMEs | Documents tab → Import |
Jira (XML)
Export from Jira via Issues → Export → Export XML (legacy export — the new CSV export doesn’t carry enough structure). The file you get back contains every issue, status, assignee email, label, and comment.
- Open Workspace Settings → Imports → Jira.
- Upload the XML file. Taskachu runs an analyse pass and shows you a preview: number of issues, detected statuses, label inventory.
- Pick the target board (existing or new). Click Execute.
- Columns are created from Jira statuses (To Do / In Progress / Done). Cards land with title, description, labels, and assignee email matched against workspace members.
Every importer runs analyse first so you see exactly what’s going to be created before anything writes. You can cancel without side-effects at this stage.
Confluence (ZIP)
From Confluence: Space settings → Content tools → Export → HTML. You get a ZIP with one HTML file per page plus an images/ folder.
- Workspace Settings → Imports → Confluence.
- Upload the ZIP. Taskachu reads the breadcrumb structure and rebuilds the parent-child page tree.
- Choose which pages to import (or all). Each becomes a Markdown document in the workspace’s Documents tree, indexed for RAG.
- Embedded images are extracted and re-uploaded to Taskachu’s S3 — links rewritten automatically.
- Confluence-specific markup (info / warning / tip macros) maps to Taskachu callouts.
ClickUp (CSV / ZIP)
Two ClickUp paths supported:
- Tasks → CSV: tickets, statuses, due dates, custom fields. Lands as a board.
- Docs → ZIP: ClickUp Docs export. Lands in Documents.
Both go through Workspace Settings → Imports → ClickUp. The analyser auto-detects which kind of export you uploaded.
Taskachu workspace ZIP
Already using Taskachu and want to clone the workspace, or move it to a different team? The Exports → Download ZIP feature creates an archive with every document as a Markdown file + a _taskachu.json manifest that preserves the parent-child tree.
- In the source workspace: Settings → Exports → Download ZIP.
- In the destination workspace: Documents → Import → upload the ZIP.
- The importer detects the manifest and rebuilds the tree losslessly — slugified folder names, special characters, everything.
The Taskachu manifest sidesteps the slug/unslug problem that affects every other importer — re-importing a Taskachu ZIP produces the exact same document tree, character-for-character.
Single document import
Don’t need a bulk migration? Drop a single file via Documents → Import → choose a file. Accepted formats:
.md— Markdown, mapped 1:1 to BlockNote blocks..html/.htm— HTML, cleaned and converted..docx— Word documents, formatting preserved best-effort..pdf— PDFs, text extracted (no images).
Tips & edge cases
- Assignees by email — Jira / ClickUp ship assignee email. If that email matches a workspace member, the card gets assigned automatically; otherwise the field is left empty (no invite is sent).
- Large ZIPs — 50 MB cap per upload today. For bigger exports, split the source archive or contact support.
- Custom fields — Jira / ClickUp custom fields land as plain Markdown in the card description for now. Native custom-field mapping is on the roadmap.
- Re-running an import — re-running an import creates duplicates (it doesn’t diff). To replace, use Delete all documents from Workspace Settings first, then re-import.