Import Projects and Tasks from Asana
Connect Asana and import projects, tasks, and users into Agiled.
Asana connects through OAuth and supports import-only runs for projects, tasks, and users.
Use the Asana import when the source of truth for project work is currently in Asana and your team wants to move project records into Agiled.
Connect Asana
- Open Settings > Apps.
- Choose Asana.
- Start the OAuth connection.
- Approve access to the Asana workspace you want to import.
- If the account has more than one workspace, choose the workspace to import.
- Return to Agiled and confirm Asana is connected and configured.
Run the Import
- Open the installed Asana app detail panel.
- Review the connected account and object scope.
- Select Import.
- Wait for the run to start.
- Review recent runs for completion or errors.
Run imports during a period when project owners can review the results. Imported projects and tasks usually need owner, status, due-date, and description cleanup before the team should work from them.
What Imports
- Projects
- Tasks
- Users
Archived projects are excluded. Active and completed tasks inside included projects are imported. Asana users are linked only when an existing Agiled teammate has the same email address; unmatched users are skipped and their tasks remain unassigned in Agiled.
Decide The Migration Boundary
Before importing, decide whether Agiled will replace Asana for the imported work or whether Asana will remain active. If both tools stay active, define which one owns status, assignee, due date, and comments after the import.
Before Importing
- Confirm you connected the correct Asana workspace.
- Review which projects should move into Agiled.
- Archive test projects in Asana if you do not want them imported.
- Confirm task names, assignees, due dates, and descriptions are usable.
- Decide who will review imported projects in Agiled after the run.
Use a small controlled Asana workspace for the first run when possible. Include an active project, active and completed tasks, assigned and unassigned tasks, and tasks with due dates so you can see how the data lands before importing a production workspace.
After Import
- Open Productivity > Projects.
- Spot-check important projects and tasks.
- Confirm imported users map to the expected teammates.
- Review due dates, statuses, descriptions, and project membership.
- Keep Asana read-only during the transition if you want to avoid split updates.
After the first review, decide whether Agiled or Asana is the source of truth for each project. If both tools stay editable, assign an owner to reconcile updates so teams do not work from two different task lists.
Tell the team when the imported projects are ready to use. Until cleanup is done, keep imported projects in review so teammates do not update incomplete or duplicated work.
Common Import Issues
- Tasks without clear owners may need reassignment in Agiled.
- Custom Asana fields may not map one-to-one with Agiled task fields.
- Completed tasks remain completed after import; archived projects are not imported.
- Re-running the same connection updates records linked to the same Asana IDs. Review the run summary before assuming every source change mapped cleanly.
If the first import creates unexpected records, stop and clean the mapping or source data before rerunning. Repeated imports update linked records and can make incorrect mappings harder to unwind.
Post-Import Cleanup
After import, create a saved view or tag for imported projects if available. Review project owners, task statuses, due dates, dependencies, and descriptions before asking the team to work from the imported list.
Close or archive imported test projects quickly. Leaving test data beside active projects can distort productivity reports and confuse task assignments.
Disconnect Asana
Disconnecting revokes the Asana authorization and removes the saved access from Agiled. It does not delete projects, tasks, or user mappings already imported into Agiled.