Migration guide
Migrate from Todoist to Planoda
Todoist is a fast, friendly task manager for personal and small-team to-dos, but it isn't built for shipping software as a team. This guide moves your projects and tasks into Planoda so quick capture stays quick while you gain cycles, estimates, dependencies, and code links.
Updated
Migration in short
- Migrating from Todoist to Planoda is a 7-step path: export, map, import, verify, then cut over.
- Start by exporting from Todoist — Export from Todoist, then map every field to its Planoda equivalent.
- 9 Todoist concepts map onto Planoda fields (issues, workflow states, cycles, estimates, labels, and more), previewed before anything is written.
- Run both tools in parallel for a short overlap, reconcile the counts, then make Planoda the system of record — no work is left behind.
Step by step
How to move from Todoist
Export from Todoist
Export each project from its ••• menu → Export as a template → CSV, which pulls tasks with their section, priority, due date, and labels. The Todoist API is the richer path for many projects or for pulling completed-task history.
Map projects, sections, and priorities
A Todoist project maps to a Planoda team or project, sections become board columns or workflow states, and tasks become issues. Todoist's P1–P4 priorities map directly onto the Planoda priority scale.
Translate labels, sub-tasks, and recurring rules
Todoist labels map to Planoda labels, sub-tasks map to sub-issues, and due dates carry across. Recurring tasks are rebuilt as Planoda no-code automations — most teams find they need only a handful.
Import into Planoda
Drop your cleaned export into the CSV importer, or push records through the public REST API for large or incremental loads. The importer previews the mapping and flags any rows that need attention before anything is written.
Verify the imported data
Spot-check a sample of issues against the source: titles, assignees, states, priorities, comments, and links. Run a count reconciliation so the totals match before you trust the new workspace.
Run both tools in parallel
Keep the old tool read-only for a short overlap window while your team learns the new workflows. Route all new work into Planoda so nothing is created in two places.
Cut over and archive the source
Once the team is comfortable and open work is in sync, freeze the source tool, export a final backup, and make Planoda the system of record. Update bookmarks, integrations, and team docs.
Field mapping
What maps to what
How Todoist concepts map onto Planoda.
| Todoist | Planoda |
|---|---|
| Project | Team / Project |
| Section | Board column / Workflow state |
| Task | Issue |
| Sub-task | Sub-issue |
| Priority (P1–P4) | Priority (Urgent–Low) |
| Label | Label |
| Due date | Due date |
| Assignee (shared project) | Assignee |
| Recurring task | Automation |
Pro tips
Make the move smoother
The template CSV export captures the active task tree; use the API if you also want completed-task history.
Map P1–P4 to the Planoda priority scale up front so urgency reads consistently after the move.
Treat recurring tasks as a chance to consolidate — rebuild them as a few automations rather than dozens of repeating to-dos.
FAQ
Migrating from Todoist — FAQ
A note from the founder
“I'm building Planoda in the open and putting my name on it. No borrowed logos, no invented stats — just the work, shipped and auditable. If it doesn't earn your trust, tell me.”
Dmitrii Selikhov is the founder of Planoda and a lead full-stack engineer with 15+ years building developer tools and leading teams as a technical lead, software architect, and CTO.
Still deciding?
Make the switch
Leave Todoist behind this weekend.
Bring your Todoist export — we'll match every workflow, field by field.