Importing & migrating

The fastest way to get a team to adopt a new tracker is to land their real work in it on day one. Planoda supports importing from the common tools — there are dedicated migration guides for Linear, Jira, Trello, Asana, monday.com, Notion, ClickUp, GitHub Projects, Shortcut, and Basecamp on the marketing site.

What comes across

A migration brings titles, descriptions, states, assignees, priorities, labels, and comments. Where the source tool exposes them, it preserves created/updated timestamps and maps the source workflow onto your Planoda workflow states. Mapping is reviewed before the import runs so nothing lands in the wrong column.

CSV as a universal path

If your source is not on the dedicated list, export to CSV and import that. You map columns to fields once; large imports run server-side so a big backlog does not tie up the browser.

Pick the right import path

Start with the per-tool migration guide for your source — it covers the gotchas specific to that tool's data model. Fall back to CSV only when there is no dedicated path. After import, run the onboarding checklist to get the team into a first cycle.