Migrate from Dart to Asana

Dart Workspaces map to Asana Workspaces as the top-level container, but Asana introduces a Teams layer inside the Workspace that Dart does not have. We create a default Team (using the Workspace name) during migration so that every migrated Project has a valid Team assignment. If the customer's Dart workspace contains distinct functional areas, we create multiple Asana Teams and map Projects accordingly during scoping.

Dart Projects map 1:1 to Asana Projects. We preserve the project name, description, start date, and target end date where available in Dart's API response. Project membership and visibility settings map to Asana's project team and privacy settings. Project-level settings in Dart that have no Asana equivalent (e.g., Flutter-specific integrations) are noted in the handoff inventory.

Dart Tasks map directly to Asana Tasks. Standard fields (title, description, due date, assignee, status) migrate 1:1. Task-level custom field values migrate by first resolving the custom field definition in the destination project, then writing the typed value to Asana's custom_field_value entries. We flag any Dart task-level custom field values that reference workspace-level field definitions not yet created in the target project.

Dart Subtasks nest under parent Tasks with a clear parent_id reference. We preserve nesting depth up to Asana's subtask limit (15 levels) and reconstruct the full subtask tree in Asana using the parent task GID. Each subtask inherits the project membership of its root parent task.

Dart workspace-level custom field definitions are the highest-risk migration object because they must be created in Asana before any task record is loaded. We extract every distinct field definition (name, type, options for picklists, format for numbers and dates) during the discovery phase, then create each field definition in the destination Asana project(s) before task records are imported. Field type mapping: Dart text maps to Asana Text, Dart number maps to Asana Number, Dart date maps to Asana Date, Dart picklist maps to Asana Enum.

Dart attachments are stored as separate linked resources rather than embedded on task records. We perform a separate discovery pass to enumerate every attachment, retrieve its URL and metadata from Dart, download the file content to temporary storage, upload it to Asana's file storage (creating a ContentDocument), then create a ContentDocumentLink connecting the ContentDocument to the target Task or Project. For migrations with thousands of attachments, this is the longest phase. We batch uploads in groups of 20 to stay within Asana's API rate limits.

Dart assignee references use user IDs. We extract every distinct assignee email from Dart Tasks and match against Asana's user directory by email. Users without an existing Asana account are held in an assignee reconciliation queue for the customer's admin to provision before task import resumes. We do not create Asana users via API without admin authorization.

Dart workspace membership and permission roles migrate to Asana Workspace members. Role name mapping depends on Asana workspace permission levels (Member, Guest, Admin). We extract the Dart role per user and map to the nearest Asana role; custom Dart roles that have no Asana equivalent are escalated during scoping.

Dart time entries linked to tasks migrate to Asana as custom numeric fields (hours logged) on the parent Task. Asana does not have a native time-tracking entry object in the same way Dart does; time data is represented as a custom field value rather than a separate record. The user association from the Dart time entry resolves via the same user lookup pass used for assignees.

Dart task status values (e.g., Open, In Progress, Complete) map to Asana task completion status (completed = true/false). Dart's granular status states map to the nearest Asana completion state. We preserve any custom Dart status labels in a custom field for audit.

Dart task comments migrate to Asana Stories with story_type = comment. We preserve the comment body, author (resolved via email lookup), and timestamp. Comment threading in Dart does not have a direct Asana equivalent; flat comments migrate as a chronological story feed on the task.

Dart tags migrate to Asana Tags. We preserve the tag name and apply it to the corresponding task via the Tag resource. Tags in Dart that serve as categorization (rather than assignment or priority) map most directly. If tags are used extensively, we recommend the customer review tag consolidation during scoping.