Import from Asana
The Asana importer migrates tasks, sections, assignees, priorities, tags, and comments from an Asana project into SetGet. Asana sections map to SetGet workflow states, giving you a clean transition from Asana's board-based workflow to SetGet's state-driven model.
What gets imported
| Asana field | SetGet field | Notes |
|---|---|---|
| Task name | Work item title | Direct mapping |
| Task description | Work item description | Rich text converted |
| Section | State | Mapped via section-to-state table |
| Priority (custom field) | Priority | Mapped if Asana project uses a priority field |
| Assignee | Assignee | Matched by email |
| Tags | Labels | Created if they do not exist |
| Comments | Comments | Imported with author attribution |
| Subtasks | Sub-work-items | Imported as child items |
| Due date | Due date | Direct mapping |
| Completed status | State | Completed tasks map to the Completed state group |
Prerequisites
- An Asana account with access to the project you want to import.
- Admin or Owner role in your SetGet workspace.
Setup steps
Step 1 -- Connect to Asana
- Go to Settings > Import.
- Select Asana.
- Click Authorize with Asana.
- Asana's OAuth consent screen appears. Click Allow.
- You are redirected back to SetGet.
Step 2 -- Select the Asana workspace and project
- Select your Asana workspace from the dropdown.
- Select the project to import.
- SetGet scans the project and shows a summary: task count, section count, tag count.
Step 3 -- Choose the target project
- Create new project -- uses the Asana project name.
- Import into existing project -- select an existing SetGet project.
Step 4 -- Map sections to states
Asana sections serve as board columns. Map each section to a SetGet state:
| Asana section (example) | Suggested SetGet state |
|---|---|
| Backlog | Backlog |
| To Do | Todo |
| In Progress | In Progress |
| Review | In Review |
| Done | Done |
If the Asana project has sections that do not match any existing SetGet state, create new states from the mapping interface.
TIP
Completed tasks in Asana (regardless of section) are automatically mapped to the Completed state group unless you override this behavior.
Step 5 -- Map priorities
If your Asana project uses a custom field for priority:
| Asana priority value | SetGet priority |
|---|---|
| Critical | Urgent |
| High | High |
| Medium | Medium |
| Low | Low |
| (no value) | None |
If no priority field exists in Asana, all imported items default to None.
Step 6 -- Configure options
| Option | Description | Default |
|---|---|---|
| Import comments | Import task comments | On |
| Import subtasks | Import subtasks as child work items | On |
| Import completed tasks | Include tasks marked complete | On |
| Import tags as labels | Convert Asana tags to SetGet labels | On |
| Import attachments | Re-upload attachments | On |
Step 7 -- Start import
Click Start Import and monitor progress on the real-time progress screen.
Post-import validation
| Check | How |
|---|---|
| Total count | Compare work item count to Asana task count |
| State distribution | Review board view column counts |
| Priorities | Filter by priority in list view |
| Assignees | Filter by assignee to verify mapping |
| Comments | Open several items and check comment threads |
| Subtasks | Expand parent items to verify children |
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| Connection fails | OAuth token expired | Re-authorize from Settings > Import |
| Sections not detected | Asana project uses list view without sections | Add sections in Asana before importing |
| Priority not imported | No custom priority field in Asana | Assign priorities manually after import |
| Assignees unmatched | Email mismatch | Invite members with matching emails |
| Rich text formatting lost | Unsupported Asana markup | Edit descriptions manually |
WARNING
Asana personal access tokens have rate limits. For large projects (5,000+ tasks), the import may take several minutes. Do not interrupt the process.
Asana concept mapping
Asana and SetGet use different terminology. This table helps translate between the two:
| Asana concept | SetGet concept | Notes |
|---|---|---|
| Workspace | Workspace | Direct equivalent |
| Project | Project | Direct equivalent |
| Task | Work item | Core trackable unit |
| Subtask | Sub-work-item | Child of a work item |
| Section | State | Sections become states via mapping |
| Tag | Label | One-to-one mapping |
| Custom field | No direct equivalent | Values appended to description |
| Portfolio | No direct equivalent | Use workspace-level views |
| Goal | No direct equivalent | Track via modules or labels |
| Status update | No direct equivalent | Use comments or pages |
| Form | Intake form | SetGet has its own form system |
Handling custom fields
Asana projects often use custom fields beyond priority (e.g., "Team", "Quarter", "Effort"). These fields do not have direct SetGet equivalents. The importer handles them as follows:
- Custom fields with a select type are listed in the mapping interface.
- You can choose to map them to labels (each option becomes a label).
- Alternatively, they are appended to the work item description as a formatted key-value list.
TIP
If an Asana custom field represents a concept that maps to SetGet labels (e.g., "Component"), map it as labels during import. This preserves the ability to filter by that dimension.
Multi-project tasks
Asana allows a single task to belong to multiple projects. During import, multi-project tasks are:
- Imported into the target SetGet project once.
- A note is added to the description listing the other Asana projects the task belonged to.
- If you import multiple Asana projects, the task may appear as a duplicate. Use the duplicate detection step in post-import validation to identify and merge these.