Agiled Docs

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.
Return to Agiled and confirm Asana is connected.

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

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.
Clean up archived or 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.

Import a small representative set first when possible. Include one active project, one completed or archived example, assigned tasks, unassigned tasks, and tasks with due dates so you can see how the data lands before importing everything.

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.
Archived or completed work may still need cleanup after import.
Re-running an import can create confusing duplicates if the integration does not update existing records in the way you expect.

If the first import creates unexpected records, stop and clean the mapping or source data before rerunning. Repeated imports can multiply cleanup work.

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.

Import Projects and Tasks from Asana