Migrate from Project Central to Asana

Project Central Projects map directly to Asana Projects. We preserve the project name, description, start date, target end date, and status. The project-level owner maps to an Asana project member with Admin-level access. If the source project uses a specific methodology template (Agile or Waterfall), we note this in the handoff inventory so that the customer can apply an equivalent Asana template during setup.

Project Central Tasks map to Asana Tasks within the corresponding Project. Task name, description, start date, due date, and completion status migrate directly. The source Task status (based on the Project's configured Status workflow) maps to either an Asana Section membership or a single-select custom field in Asana, depending on whether the source workflow is a linear stage progression or a multi-branch state model.

Project Central child Tasks nested under a parent Task map to Asana Subtasks. We preserve the parent-child relationship by setting the Asana Subtask's parent field to the migrated parent Task's new Asana gid. Subtask assignees, due dates, and status fields migrate independently while remaining linked to their parent.

Project Central Task Owners map to Asana Users by email address. We extract the distinct owner email set from the source data and match against Asana Users in the destination workspace. Any owner without a matching Asana User goes to a reconciliation queue for the customer's admin to provision before record assignment migration. This step is blocking for assignee resolution and must complete before task import begins.

Project Central Tags migrate to Asana Tags. Tags are not project-scoped in Asana; they are workspace-level labels that can be applied across any project. We preserve the tag name and any tag color metadata from Project Central. If the source uses a hierarchical tag taxonomy, we flatten it to Asana's single-level tag model and note the original grouping in the handoff document.

Project Central custom fields migrate to Asana custom fields of equivalent type. Text fields map to Asana Text, date fields to Asana Date, numeric fields to Asana Number, and single-select fields to Asana Enum (dropdown). Multi-select fields map to Asana Multi-enum. Asana requires custom fields to be created at the portfolio or organization level before they can be added to specific projects; we pre-create the field schema in Asana during the configuration phase so that fields are available when tasks are imported.

Project Central Status workflows define task states within a project. Linear multi-stage workflows (e.g., To Do, In Progress, Review, Done) translate to Asana Sections within the project list. Non-linear or conditional workflows with branching states map to a single-select custom field that we create and populate with the source state values. The choice between Section-based and field-based mapping is made during scoping based on the source workflow structure.

Project Central stores no native file attachments; all document references are SharePoint Online links. We extract the SharePoint URLs and append them as formatted links at the bottom of the corresponding Asana Task description. File names and paths from the source are preserved as link text so that users can identify documents without opening SharePoint. If the destination Asana organization uses Google Drive or Box, we flag any SharePoint-only links in the handoff document for the admin to re-link post-migration.

Project Central's configurable Views (list, board, timeline) reflect how a project is organized. Asana natively supports List, Board, and Timeline views per project. We do not migrate Views as configuration; instead, we document the view preference for each source project and note the equivalent Asana view selection in the handoff inventory so that the customer's admin can apply the correct view layout when setting up each project in Asana.

Project Central supports task dependencies within projects. Asana supports dependencies via the Asana Deps integration (formerly Flow, now native in Advanced and Enterprise tiers) or third-party tools. Because dependency modeling in Asana requires the Asana Deps feature to be active and configured per project, we flag dependencies in the handoff inventory with the source dependency type (Finish-to-Start, Start-to-Start, etc.) so that the customer's admin can configure them manually in Asana. Dependencies are not automatically migrated due to the feature-availability constraint.

Project Central can store time entries against tasks. Asana does not have a native time-tracking object; time tracking requires an Asana native integration (Harvest, Toggl, or Timely) or a custom solution. We flag all time entry records in the handoff inventory with the source task association, hours logged, and date so that the customer's admin can recreate entries in their chosen time-tracking tool post-migration.

Project Central task-level comments and status update history migrate to Asana Task comments. We extract comments with author, timestamp, and body text and create corresponding Asana comment records attached to the migrated Task. The comment author is resolved to an Asana User where email matching is available; if no match exists, the comment is attributed to the Asana workspace Guest or a system note indicating the original author name.