Migrate from Planview ProjectPlace to Asana

ProjectPlace Workspaces map to Asana Teams as the organizational unit and Asana Projects as the project container. We map Workspace-level settings, description, and start date to the Project. Member lists migrate as Project members with the Asana Team as the parent grouping. Organizations with more than 50 active Workspaces may prefer to map each Workspace to a standalone Asana Project without Team grouping; we confirm the preferred structure during scoping.

ProjectPlace Activities map directly to Asana Tasks with assignees, due dates, status, and subtask hierarchy preserved. Subtasks in ProjectPlace map to Asana subtasks. Assignee resolution uses email matching against the Asana destination workspace. Any Activity without a matching Asana user is flagged in the reconciliation report for the customer's admin to provision before import.

ProjectPlace Kanban boards map to Asana's Board view within each Project. Board columns map to Asana Sections or custom columns if the customer uses an integration. Card-level metadata (card name, description, assignee, due date, labels) migrates as task fields. Card ordering within each column is preserved as section ordering in Asana. Note that Asana Board view is view-level only; there is no separate card object separate from Task.

ProjectPlace Gantt task dependencies (finish-to-start, start-to-start, finish-to-finish, start-to-finish) map to Asana dependencies using the Asana Tasks API dependency endpoints. We freeze the current calculated dependency chain before export because ProjectPlace's automatic date recalculation would otherwise replay the recalculation at the destination incorrectly. Start and end dates replay as static values in Asana's Timeline. Any circular dependency detected in ProjectPlace is flagged for manual resolution before migration.

ProjectPlace milestones map to Asana Milestones. We freeze milestone dates before export to prevent ProjectPlace's downstream recalculation logic from unanchoring fixed dates during the migration window. Milestone name, date, and associated tasks migrate. Tasks linked to milestones in ProjectPlace are associated with the corresponding Asana Milestone via the milestone association field.

ProjectPlace per-Workspace custom fields map to Asana custom fields. We enumerate the full custom field taxonomy during scoping, map each ProjectPlace field type (text, number, date, enum) to the matching Asana custom field type, and pre-create field definitions in the destination Asana workspace before any task values are written. OTB sync field limitations in ProjectPlace mean we must query the full API surface directly rather than relying on any standard export; any custom fields not exposed via API are flagged for supplemental manual export from Planview support.

ProjectPlace user accounts map to Asana workspace members by email address. User display name and email migrate. Role-based permissions in ProjectPlace may not have a direct Asana analog; we flag permission gaps and recommend a post-migration review of Asana project member roles and guest access settings.

ProjectPlace documents stored within Workspaces — including file name, uploader, upload date, and URL — migrate as Asana Attachments. Binary file blobs require a separate file transfer step; we catalog attachment references and filenames during the schema scan and orchestrate parallel file migration alongside the object migration. Project-level documents migrate to the Asana Project description or as pinned attachments.

ProjectPlace task-level time entries (hours logged, date, user attribution) migrate as Asana Task-level custom fields (time logged) or as structured subtasks with a note containing hours and date. Asana has no native time tracking object; the customer chooses the carry-forward strategy during scoping. Reporting aggregations from ProjectPlace time logs are not transferred and must be reconstructed in Asana's reporting module or via a time-tracking integration.

ProjectPlace task-level comments and board conversations migrate as Asana Comments on tasks. Author, timestamp, and comment text are preserved. Nested reply threads in ProjectPlace flatten into a linear comment sequence in Asana. @mention formatting is stripped during migration because Asana @mentions resolve against its own user table.

Task-level file attachments in ProjectPlace migrate as Asana Attachments on the corresponding task. We catalog attachment references and filenames during the schema scan, then orchestrate parallel file transfer alongside the object migration. Attachments larger than 100 MB are flagged for chunked upload via the Asana Attachments API.

ProjectPlace Agile boards with sprint cycles map to Asana Projects using Sections to represent sprints or using the Portfolio's sprint-tracking view. Sprint names, start and end dates, and backlog items migrate as tasks with section membership. Velocity and burndown data from ProjectPlace are not carried forward; Asana calculates its own velocity once the team begins using the sprint structure. The customer chooses whether to use Asana native portfolios or a lighter section-based approach during scoping.

ProjectPlace custom status values and color-coded labels per Workspace are enumerated during scoping and mapped to Asana Tags. Tag color is preserved where Asana supports it. Any status value without a direct Asana tag equivalent is flagged for the customer's admin to review and assign.

ProjectPlace's workload visualization aggregates task assignments per user across all Workspaces. We export the underlying task-assignee data so workload balance can be reconstructed at the destination using Asana's Portfolio view or a custom report. The aggregated workload percentages themselves are not transferable and must be recalculated in Asana's reporting layer.