Migrate from Project Drive to Asana

Project Drive Projects map directly to Asana Projects. We extract project name, description, status, start date, and creation timestamp from the source export and create the corresponding Asana Project. Project Drive's project-level budget and cost fields migrate to Asana custom numeric fields (see Budget and Cost Fields row). Teams in Project Drive map to Asana Teams that we configure before project import.

Project Drive Tasks map to Asana Tasks with name, description, assignee, start date, due date, and status preserved. We map Project Drive status values to Asana task completion state (completed tasks become Asana tasks marked complete). The Asana Task's parent Project is resolved before insert to satisfy the Project-Task relationship. Subtasks under each Task are processed as child tasks (see Subtask mapping).

Project Drive Subtasks are child records under Tasks. In Asana, subtasks are modeled as Tasks with a parent_task field set to the containing Task's Asana gid. We flatten the Project Drive Subtask hierarchy into Asana Tasks, preserving the child relationship via the parent reference. If Project Drive subtasks have their own assignees, start dates, or due dates, those migrate as fields on the child Task. Sections from Asana are used to group related tasks if the customer's Project Drive workspace used section-style grouping.

Project Drive Milestones are date-flagged markers within the Gantt view. Asana has a native Milestone feature that marks a Task as a milestone with a milestone boolean flag and a due date. We export Project Drive milestones as standalone Tasks with the milestone flag set, and the original milestone name and target date preserved. Milestones are inserted after all regular Tasks in the migration phase so their target dates can reference a valid project context.

Project Drive user accounts and task assignee relationships map to Asana Users. We extract distinct users from all assignment fields, then match by email against the destination Asana workspace. Any Assignee without a matching Asana User goes to a reconciliation queue for the customer's admin to provision before the task import phase begins. Task assignment migrates as the Asana assignee field on each Task. Project Drive's cross-functional team assignment concept migrates to Asana Teams membership, with tasks assigned to individual team members.

Project Drive stores budget and cost data as native project and task fields. Asana has no built-in financial tracking schema. We create custom numeric fields on the Project or Task level during schema setup (e.g., Total_Budget__c, Actual_Cost__c, Estimated_Cost__c) with appropriate precision matching the source data. The customer decides during scoping whether cost fields belong at the project level or task level. We flag any null or zero-value budget fields to ensure clean numeric imports without type errors.

Project Drive displays task dependencies visually in Gantt view, but exported CSV data may flatten these relationships into ordering sequences. We reconstruct explicit Finish-to-Start dependency declarations from the Gantt visual layout, mapping each predecessor-successor pair to an Asana Dependency record. Dependencies are the last objects inserted in the migration phase to ensure both the source and dependent tasks exist in Asana before the link is created. Start-to-Start and Finish-to-Finish dependency types are preserved if the source data supports them.

Project Drive attachments on tasks or projects are exported as binary file blobs with original filename and content type preserved. We re-upload each file to the corresponding Asana Task or Project using the Asana file upload endpoint, maintaining the original filename so that document context is not lost. Link integrity depends on Asana's file storage, which retains files associated with the workspace. Large attachments (over 100 MB per file) may require chunked upload handling.

Project Drive assigns tasks to cross-functional teams with explicit team-task ownership. Asana's Team feature groups members and projects but does not assign tasks directly to teams—tasks are assigned to individual users. We map Project Drive team assignments to Asana Teams and create Team memberships for each team member. Task-level team assignment is represented by assigning the task to the team's primary contact or project lead, with the team name recorded in a custom field (e.g., Team_Name__c) for reference.

Project Drive integrates with external calendars but does not expose calendar event objects in its export. We do not migrate calendar entries. Teams re-establish calendar sync post-migration by connecting their calendar (Google Calendar or Outlook) to Asana via the native integration. Task due dates and start dates migrated from Project Drive appear as upcoming work in Asana's Calendar view without requiring separate calendar event migration.

Any custom fields defined in Project Drive beyond the standard name, description, assignee, start date, due date, and status migrate to Asana Custom Fields. We create the equivalent Asana custom field (text, number, date, enum, or checkbox depending on content type) during schema setup, then populate values during task and project import. Multi-select or enum-style custom fields from Project Drive map to Asana enum custom fields with the same option values.

Project Drive's Gantt view establishes task ordering within a project. Asana uses a position index for list ordering and sections for grouping. We capture the Gantt sequence order from the export and apply it as task position values in Asana's List view, using section boundaries where the source data indicates grouping. Tasks retain their position within the list so that the original sequencing is visible without requiring Gantt reconstruction.