I have recently sold a portion of my company to another owner. I want to export everything associated with that Asana team so that the new owners can re-create the history, users, forms, etc. I see some posts from 2017/2019 on this topic, but I imagine there are better ways to accomplish this now.
The data migration option does not work because I am exporting only one team within my organization.
** There are too many projects to realistically export one at a time.
I get why you’d want a clean, one-click export for a single team. Short answer: there isn’t a native “export this team and everything in it” today. You can either export the whole org as an admin, or export per project, which doesn’t fit your case.
Here’s what I’ve seen work when you need to hand off one team at scale:
If the goal is pure continuity, invite the new owners into that team in your current org so they get full history, comments, attachments, and forms as-is. You can later remove your access. Easiest and most complete fidelity.
If they must take the data to a separate org, use the API to automate exports:
List all projects in the team
For each project, pull tasks, subtasks, custom fields, sections, assignees, due dates, and stories (comments). You can also fetch attachment metadata and download files.
Recreate on the destination using the API or CSV imports for tasks, then map custom fields.
Note: forms don’t have a simple cross-org export. I usually duplicate a project within the same org to keep the form structure, or capture the form settings and rebuild on the destination.
CSV-only route if you can’t use the API: still project-by-project. To batch-identify projects, put all team projects in a Portfolio, export the portfolio list for inventory, then export each project’s CSV. It’s more manual but helps you track progress.
Is this something you (or someone else you can recommend) would be able to assist with as a consultant?
See my reply here, and the caveats, for two apps that help with this. Coding with the API is a lot of work, and CSV misses far too much content for a request like this.
Thanks,
Larry