Migration guide
Migrate from Azure DevOps to Planoda
Azure DevOps Boards is powerful but heavy, with work-item hierarchies and process templates that slow teams down. This guide moves your work items into Planoda so you keep the structure that matters and shed the configuration overhead.
Updated
Migration in short
- Migrating from Azure DevOps to Planoda is a 7-step path: export, map, import, verify, then cut over.
- Start by exporting from Azure DevOps — Export from Azure DevOps, then map every field to its Planoda equivalent.
- 9 Azure DevOps 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 Azure DevOps
Export from Azure DevOps
Export work items from a query in Boards (Queries → Export to CSV) including titles, states, assignees, iterations, area paths, and tags. For full hierarchy and history, the Azure DevOps REST API streams work items with their links.
Map work-item types and states
Map Epics/Features to projects or parent issues, User Stories/Tasks/Bugs to issues and sub-issues, and your process-template states (New/Active/Resolved/Closed) to Planoda workflow states.
Translate iterations, areas, and tags
Iteration paths map to cycles, area paths map to teams or projects, and tags map to labels. Effort/story-point fields map to estimates so planning data carries over.
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 Azure DevOps concepts map onto Planoda.
| Azure DevOps | Planoda |
|---|---|
| Epic / Feature | Project / Parent issue |
| User Story / Task / Bug | Issue |
| Child work item | Sub-issue |
| State (process template) | Workflow state |
| Iteration path | Cycle |
| Area path | Team / Project |
| Story points / Effort | Estimate |
| Tag | Label |
| Assigned To | Assignee |
Pro tips
Make the move smoother
Use a saved Boards query to scope each export cleanly to one team or area at a time.
Migration is the moment to collapse an over-engineered process template down to a few real states.
Reach for the REST API when hierarchy and links matter; CSV is fine for flat work-item lists.
FAQ
Migrating from Azure DevOps — 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.
Make the switch
Leave Azure DevOps behind this weekend.
Bring your Azure DevOps export — we'll match every workflow, field by field.