Migration guide
Migrate from Teamwork to Planoda
Teamwork is built for agencies and client services — time tracking, billing, and milestones — but it stops short of a real engineering tracker. This guide moves your projects and task lists into Planoda so client work stays organized while software teams gain cycles, estimates, and code links.
Updated
Migration in short
- Migrating from Teamwork to Planoda is a 7-step path: export, map, import, verify, then cut over.
- Start by exporting from Teamwork — Export from Teamwork, then map every field to its Planoda equivalent.
- 9 Teamwork 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 Teamwork
Export from Teamwork
Export each project's tasks to CSV from the project (Project → Tasks → Export → CSV), which pulls tasks with their list, assignees, due dates, and priorities. The Teamwork API is the richer path when you want time-log and dependency data scripted across.
Map projects, task lists, and milestones
A Teamwork project maps to a Planoda team (or one team per client), task lists become workflow states or board columns, and tasks become issues. Milestones map to cycles for time-boxed work or to projects/initiatives for larger deliverables.
Carry assignees, tags, and time
Teamwork assignees map to Planoda assignees, tags map to labels, and priorities carry straight across. Logged time and estimates import alongside Planoda estimates so client billing context isn't lost.
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 Teamwork concepts map onto Planoda.
| Teamwork | Planoda |
|---|---|
| Project | Team / Project |
| Task list | Workflow state / Board column |
| Task | Issue |
| Subtask | Sub-issue |
| Milestone | Cycle / Project |
| Estimated time | Estimate |
| Priority | Priority |
| Tag | Label |
| Assignee | Assignee |
Pro tips
Make the move smoother
Use the Teamwork API when time logs and task dependencies matter for billing; CSV is fine for straightforward task lists.
Map each client to its own team so cross-client reporting and access control stay clean.
Decide which task lists are real workflow stages versus simple groupings before mapping them to states.
FAQ
Migrating from Teamwork — 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 Teamwork behind this weekend.
Bring your Teamwork export — we'll match every workflow, field by field.