Switching to kumo
Bring the work with you, at your own pace. Here is where each tool's job lives in kumo, and what stays different.
Tool by tool
Atlassian kumo and Jira Plan & produce · Bugs & QA Codecks GmbH kumo and Codecks Plan & produce · Bugs & QA · Wiki & docs HacknPlan kumo and HacknPlan Plan & produce · Wiki & docs Autodesk kumo and Flow Production Tracking (ShotGrid) Plan & produce · Review ftrack kumo and ftrack Plan & produce · Review Notion Labs kumo and Notion Wiki & docs · Plan & produce Atlassian kumo and Confluence Wiki & docs Miro kumo and Miro Wiki & docs Adobe kumo and Frame.io Review · Wiki & docs Functional Software kumo and Sentry Bugs & QA
Tasks
Synced both ways
kumo imports from these and stays in sync with them, comments included, so the team can move one group at a time.
- Jira
- Asana
- ClickUp
- Codecks
- HacknPlan
- Linear
- monday.com
- Taiga
- Trello
- YouTrack
Documents
Imported into the wiki
Pages, documents and Notion databases come in as concepts. A second import of the same source changes nothing, so you can run it until the day you switch.
- Notion
- Confluence
- Google Drive
- SharePoint
- Word
- Markdown
What kumo does not do
Some tools stay
kumo is not a chat: your team keeps Discord, and kumo reaches people there. It is not version control: keep yours, and pull and merge requests show on their tasks. It is not a crash service at scale: keep Sentry, Backtrace or BugSplat, and kumo turns their crash groups into bugs. And it is not your engine or your DCC tools: it works beside them.