Asana Import
This page controls migrating data from your previous Asana account into SELLERLOGIC Commerce Services. You connect Asana via a personal access token, read projects and tasks into a staging area, and then materialize them into the native Tasks system.
What can I do here?
- Set up and test the connection to Asana via a Personal Access Token
- Start a full import or a delta import (only changes since the last run)
- View past import runs with status and metrics
- Materialize imported Asana data into the native task system
- View past materialize runs
Step by step
Set up the connection
- In Asana, generate a Personal Access Token under "Settings → Apps → Developer Console".
- Enter it in the Personal Access Token (PAT) field and optionally provide the Workspace GID if you only want to import a specific Asana workspace.
- Decide whether archived projects should be included, and click Save.
- Click Test Connection to check whether access works.
Import data
- Click Run Full Import to re-read all objects from Asana, or Delta Import to transfer only tasks changed since the last run.
- Track progress in the Import Runs list, with mode, status, number of new/updated tasks, and errors.
Materialize into Tasks
- Check the preview to see how many projects, tasks, subtasks, and comments have already been imported, and how many Asana staff could already be matched.
- Click Materialize into Tasks to move the imported data into the native task system. The operation is repeatable — running it again doesn't create duplicates.
- The materialized projects and tasks then appear under Tasks.
/tasks/asana| Mode | Status | Created | Updated | Errors |
|---|---|---|---|---|
| Delta import | ✓Completed | 12 | 48 | 0 |
| Start full import | ✓Completed | 640 | 0 | 2 |
| Delta import | iRunning | 3 | 9 | 0 |
/tasks/asanaImport flow
flowchart LR A[Connect Asana] --> B[Full import or\ndelta import] B --> C[Data in staging layer] C --> D[Materialize into Tasks] D --> E[Appears under Tasks]
Fields explained
| Field | Meaning | Notes/Effect |
|---|---|---|
| Personal Access Token (PAT) | Access key for the Asana API | Stored encrypted; leave blank to keep the saved token |
| Workspace GID | Optional ID of a specific Asana workspace | Without it, all accessible workspaces are considered |
| Include archived projects | Whether already-archived Asana projects are imported too | — |
| Mode | Type of import run (full or delta) | Delta runs are faster since only changes are transferred |
| Tasks / New / Updated / Errors | Metrics of an import run | For checking whether the import was complete |
| Projects / Tasks / Subtasks / Comments (preview) | Number of imported objects ready to be materialized | — |
| Matched Asana staff | How many Asana users could already be matched to a SCS person | Unmatched staff are flagged accordingly during materialization |
Values & Status
Import run status
| Label | Meaning |
|---|---|
| Running | The import is currently in progress |
| Completed | The import finished successfully |
| Failed | The import aborted with an error |
Frequently asked questions
What's the difference between a full import and a delta import?
A full import re-reads all objects from Asana completely. A delta import only transfers tasks that changed since the last run, and is correspondingly faster.
Are imported items immediately visible in "Tasks"?
No, the import first stores the data only in a staging layer. Only the "Materialize into Tasks" step moves it into the visible task system.
What happens if I run "Materialize into Tasks" more than once?
The operation is idempotent — already-materialized projects and tasks aren't created again.
Where do I manage confirmed matches of Asana projects/tasks to customers?
That's handled separately on the Asana Matches page.