Migration guide
Migrate from Shortcut to Planoda
Shortcut (formerly Clubhouse) is a solid engineering tracker, and its model maps closely to Planoda. This guide moves your Stories, Epics, and Iterations across so estimates, states, and planning history land intact.
Updated
Migration in short
- Migrating from Shortcut to Planoda is a 7-step path: export, map, import, verify, then cut over.
- Start by exporting from Shortcut — Export from Shortcut, then map every field to its Planoda equivalent.
- 9 Shortcut 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 Shortcut
Export from Shortcut
Use Shortcut's CSV export (Settings → Workspace → Export) or the Shortcut REST API to pull Stories with their states, estimates, labels, epics, and iterations. The API gives the fullest fidelity on relationships and comments.
Map Stories, Epics, and Iterations
Shortcut Stories become Planoda issues, Epics map to parent issues or projects, and Iterations map directly to cycles. Workflow states and estimate scales line up closely, so most rows need little transformation.
Reconcile members and labels
Match Shortcut members to Planoda members by email, and map Shortcut labels straight to Planoda labels. Story types (feature/bug/chore) can become labels or properties.
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 Shortcut concepts map onto Planoda.
| Shortcut | Planoda |
|---|---|
| Story | Issue |
| Subtask | Sub-issue |
| Epic | Parent issue / Project |
| Workflow state | Workflow state |
| Estimate (points) | Estimate |
| Iteration | Cycle |
| Label | Label |
| Story type | Label / Property |
| Owner | Assignee |
Pro tips
Make the move smoother
Prefer the API export to capture comments, relationships, and iteration history fully.
Map Iterations to cycles first — it's the cleanest one-to-one and unlocks velocity reporting immediately.
Decide whether Story types become labels or properties before importing so the choice is consistent.
FAQ
Migrating from Shortcut — 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 Shortcut behind this weekend.
Bring your Shortcut export — we'll match every workflow, field by field.