Migration guide
From Asana to Kovarro
Asana projects map 1:1 to Kovarro projects. Sections become custom statuses, tasks and subtasks come across cleanly.
Imports cleanly
- Projects + sections (sections → custom statuses)
- Tasks + subtasks with titles, descriptions, due dates, assignees
- Custom fields (single-select, multi-select, text, number)
- Followers (mapped to watchers)
- Members + email addresses
Needs manual work
- Workflow Rules - need to be recreated with Kovarro's webhooks + recurring tasks
- Goals + Portfolios - no direct equivalent; the dashboard surface covers most of the use case
- Asana Inbox - Kovarro uses notification preferences + the bell instead
Doesn't migrate
- Asana Forms (planned for Kovarro v2.1)
- Asana Reporting dashboards (rebuild with Kovarro's KPI block)
Step by step
The migration playbook
Roughly 10-person team, 5-10 active projects: half a day. Larger orgs with Workflow Rules: 1-2 days, depending on rule complexity.
- 1
Export each Asana project to CSV
Asana → Project → ... menu → Export → CSV. Each project exports separately. Asana's CSV is well-structured so the importer handles it directly.
- 2
Decide on Kovarro project structure
Asana projects map to Kovarro projects 1:1 most of the time. If you have very small Asana projects (< 20 tasks), consider merging into one Kovarro project with sections as labels.
- 3
Pre-create projects with custom statuses
Match Asana sections to Kovarro custom statuses up-front. The importer matches by name.
- 4
Run the importer
Settings → Import → Upload CSV. Map columns. Preview. Import.
- 5
Rebuild Workflow Rules
For each Asana Workflow Rule, map to either a Kovarro recurring task (if time-based) or a webhook + role automation (if event-based).
- 6
Cut-over
Pick a Friday. Re-run the import for the last 24 hours of changes. Switch chat channels and email signatures to point at Kovarro.
Ready to leave Asana?
Start free in under a minute. Book a demo if you'd like us to walk through your specific setup before you switch.