Migrate from Planview PPM Pro to Asana

Planview PPM Pro Portfolios map to Asana Portfolios (available from Asana Business tier). We preserve the portfolio name, description, and strategic alignment scores as custom fields on the portfolio record. Portfolio-level financial summaries (aggregate budget totals) are documented separately as Asana does not support rollup financial fields. If the customer is on Asana Premium, Portfolios are not available and we map to a top-level Project tagged with a portfolio identifier custom field.

Programs in PPM Pro sit between Portfolios and Projects. Asana has no native Program object. We map Programs to Asana Projects within the target Portfolio, or to top-level Sections within a Projects-within-Projects structure depending on the destination workspace configuration. Program-level budgets and owner assignments become custom fields on the mapped Asana Project.

Planview PPM Pro Projects map directly to Asana Projects. The Project name, description, start and end dates, status (Draft/Active/On Hold/Completed), priority, and owner map to standard Asana Project fields or custom fields. Gantt-style timeline data migrates as the Asana Project timeline (start date and due date fields). Milestones in PPM Pro map to Milestones in Asana.

Planview PPM Pro Tasks map to Asana Tasks with WBS hierarchy preserved as parent-task and subtask relationships. Task fields including start date, due date, percent complete, and effort hours migrate to Asana fields. Dependencies (Finish-to-Start, Start-to-Start) reconstruct using Asana's dependency API (dependencies add endpoint). Task assignees resolve by email match to Asana workspace members.

Planview PPM Pro Resources (people and roles with capacity, skills, and availability calendars) have no native Asana equivalent. Asana organizes work by team membership, not a structured resource pool. We map Resources to Asana workspace members and store capacity, skills, and department as custom fields on each user's profile. Utilization heatmaps do not migrate; we deliver a written specification for rebuilding utilization views in Asana Business custom reporting.

Time entries in PPM Pro record hours logged against Projects and Tasks with dates, hours, and cost codes. Asana has no time-entry object. We export the full timesheet history as a CSV manifest and provide a mapping to Asana custom numeric fields (hours_logged, cost_code) on Tasks if the customer wants to re-enter data manually. We do not programmatically import time entries into Asana as no supported object or API endpoint exists.

PPM Pro Demand Requests capture project intake before formal approval with requester, estimated effort, priority, and status. Asana has no demand-management object. We map Demand Requests to Asana tasks in a dedicated intake project, preserving requester, priority, estimated hours, and approval status as custom fields. The structured scoring and workflow gates of PPM Pro's demand module do not migrate; we document them for the customer to rebuild using Asana Forms and Rules.

PPM Pro User-Defined Fields of type Text, Number, and Date map to Asana custom fields of equivalent type. We handle attribute-level data type mapping during the transform step. Custom field definitions are created in Asana before data import using the Asana custom fields API.

PPM Pro Dropdown User-Defined Fields map to Asana Enum (single-value or multi-value) custom fields. Asana requires dropdown options to be predefined before data import; we extract all distinct PPM Pro dropdown values during scoping, pre-create the Asana enum options, then import records with the matching enum key. Active dropdown values that are created after migration in PPM Pro will require manual option creation in Asana if both systems remain live during cutover.

PPM Pro project-level budget records include planned cost, actual cost, labor cost, and expense line items. Asana has no financial fields. We export budget data as a structured CSV and provide a mapping to Asana custom numeric and currency fields on Projects if the customer wants to re-enter the data manually. Multi-level budget hierarchies and rollup totals do not migrate. Currency mismatches are flagged during scoping with the customer's base currency noted.

PPM Pro stores file attachments against Projects and Tasks but does not expose a public attachment download API. We cannot programmatically retrieve attachment binary content. We produce a detailed manifest listing all attachment-bearing records with file names, file sizes, and record references so the customer's team can manually download from PPM Pro and re-upload to the corresponding Asana Task. We do not automate this step.

Planview PPM Pro User records (name, email, role, active/inactive status) map to Asana Workspace Members. We resolve users by email match. Active/inactive status maps to Asana member active status. Role-to-permission translation is scoped to Workspace-level roles; Asana does not have a granular role permission model comparable to PPM Pro's project-level role assignments.