Migrate from Microsoft Project to Asana

Microsoft Project plan files (.mpp) and Project Online projects map directly to Asana Projects. The project name, description, start date, and finish date become the Asana Project name, notes, and timeline start/end. Multi-project portfolios are flattened into separate Asana projects with a Portfolio for rollup.

Standard Microsoft Project tasks map to Asana Tasks. Task name, start date, due date, % complete, and notes transfer directly. Subtasks in Project become subtasks under the parent task in Asana, preserving the WBS hierarchy. Tasks with no children are flat tasks in Asana.

Summary tasks in Project (rolled-up parent rows) become parent tasks in Asana. The summary task name becomes the task name; child tasks migrate as Asana subtasks. The Project summary row's start/finish dates do not map to Asana fields but can be stored in custom fields if needed.

Project milestones (zero-duration tasks marked as milestones) migrate directly to Asana Milestones. The milestone name and target date map one-to-one. Milestone color coding and visual styling available in Project are not available in Asana — we document this as a rebuild item for the admin to address post-migration using Asana's milestone customization options.

Microsoft Project Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF) predecessor types map to Asana dependencies. Asana supports FS and SS natively; FF and SF become FS with adjusted dates handled manually post-migration. Dependency lag time is stored as a note on the Asana dependency.

Project Resources (people and equipment) map to Asana workspace members. FlitStack resolves resources by email address against the Asana workspace member list. Unmatched resources are flagged for admin review — Asana requires users to exist before assignment. Generic resources (equipment pools) do not have an Asana equivalent and are stored as custom field values.

Resource assignments in Project (hours allocated per task) map to task assignees in Asana. Project's assignment units (percentage) map to Asana's assignee system. Actual work hours logged in Project are stored as custom fields on the Asana task since Asana lacks a native work-logging field.

Project baseline start and finish dates have no Asana equivalent. We create custom date fields on each task to store the baseline values for post-migration variance analysis. Multiple baselines (Baseline 1-10) cannot all transfer — we migrate the most recent baseline by default.

Project's resource calendars (working time, exceptions, holidays) do not exist in Asana. Task start and due dates migrate as-is. Teams that rely on calendar-based scheduling must review due dates post-migration and adjust for non-working days manually or via Asana's Working Days feature (available on Advanced plan).

Microsoft Project custom task fields (Text 1-30, Number 1-20, Flag 1-20, Date 1-10) map to Asana custom fields. Text fields become Asana text or enum fields depending on value patterns; numbers map directly; date fields map to Asana date fields; flag fields become Asana checkboxes.

Microsoft Project calculates the critical path automatically as part of its scheduling engine. Asana has no critical-path calculation or visualization feature. We identify critical-path tasks from the Project calculation and store them in a custom field (Is_Critical_Path__c) as a checkbox so project managers can manually re-create critical-path tracking in Asana using filters or custom views.

Task notes in Microsoft Project map directly to the Notes field on Asana Tasks. HTML formatting present in Project notes is stripped and converted to plain text with bullet points and basic list formatting preserved where possible. Hyperlinks embedded in notes are stored as plain text URLs to maintain reference accessibility.

File attachments on Project tasks (linked documents, drawings) are downloaded and re-uploaded as Asana attachments. File size limits apply (Asana supports up to 100MB per attachment on Advanced plan). Links to SharePoint or external URLs are preserved as task-level URLs.

Project master and subproject structure has no direct Asana equivalent. Each subproject becomes a standalone Asana project. We tag subprojects with a custom field (Parent_Project__c) referencing the master project name so administrators can manually group them under an Asana Portfolio for cross-project visibility post-migration.