Migrate from Asana without losing history
Export your Asana CSV, drop it into our importer, and we map sections to statuses, custom fields to custom fields and subtasks to subtasks.
Switching from a paid tool? We credit your first three months of Pro against what is left on your Asana contract — up to $500. Send the invoice, we apply the credit.
Before you start
- Export from Asana. CSV works for tasks; use the JSON or API export if you want comments and attachments.
- Create a free workspace here. You do not need a paid plan to import — the plan limits apply after the import, and we do not lock imported data behind a paywall.
- Decide your structure. One project per Asana board or list is the default and is almost always right. Agencies usually add one workspace per client on top.
- Import into a throwaway project first. Look at 20 tasks, confirm the mapping, then delete it and run the real import.
What maps to what
| Asana | ManageYourProject |
|---|---|
| Sections | Statuses |
| Custom fields | Custom fields (type preserved) |
| Subtasks | Subtasks, nested to any depth |
| Tags | Tags |
| Attachments | Attachments, re-uploaded |
| Comments | Comments with author and timestamp |
| Dependencies | Finish-to-start dependencies |
| Portfolios | Portfolios |
What does not carry over
Being straight with you saves a support ticket later:
- Automations and integrations have to be rebuilt. The concepts map cleanly — trigger, conditions, actions — but no vendor exports automation logic in a portable format. Most teams rebuild three or four rules and quietly drop the rest, because they were never firing anyway.
- Per-object permissions reset to your new role model. Re-apply project-level overrides after the import rather than trying to translate them.
- Rich text edge cases — embedded widgets, vendor-specific mentions and some table layouts — land as plain HTML. Headings, lists, links, code blocks and images survive.
- Historical activity comes across as an import note, not a synthetic per-field history. New changes get full field-level history from day one.
A realistic timeline
For a team of 15 with about 2,000 open tasks: 20 minutes to export and import, an hour to fix statuses and custom field types, and one week running both tools in parallel before you cancel. Do not cancel on day one — read-only access to the old tool for a month is cheap insurance.
Why teams leave Asana
- No native time tracking — you need Harvest, Everhour or Toggl on top.
- Timeline and Portfolios are locked behind the $24.99 Advanced tier.
- No built-in invoicing, so agencies bolt on a second tool.
- Guests count toward your seat count on some plans.
- Automations ("Rules") are limited on lower tiers.
Where Asana is still better
A calm, familiar task list and strong mobile apps. If that describes your core workflow, staying put is the right call and we would rather you knew now than after a migration.
Get help
On Pro and above, we will run the import with you on a call and stay on until your team can find their work. There is no charge for that. Ask for a migration session.