Migrate from Planview ProjectPlace to Microsoft Project

Planview ProjectPlace Workspaces map 1:1 to Microsoft Project files (MPP or cloud Project Online Project). Each Workspace's name, description, member list, and workspace-level settings transfer as Project-level fields. We export workspace metadata via the ProjectPlace REST API, create a corresponding Project in the destination environment, and populate the Project Summary Task with the Workspace description. Workspace visibility and sharing settings require manual reconfiguration in Microsoft Project or SharePoint permissions since Project lacks a direct Workspace-permissions analog.

Planview Activities map directly to Microsoft Project Tasks. We transfer task name, start date, end date, duration, percent complete, priority, and assignee. Planview's sub-activities become subtasks in Microsoft Project's Outline hierarchy. Note that Planview's automatic date recalculation is frozen before export by snapshotting the current calculated date tree; we replay the frozen dates at the destination so that milestone and deliverable dates do not shift during migration. Task IDs are preserved in a custom column for reconciliation purposes.

Planview Kanban boards do not have a native Microsoft Project equivalent. We split each board into a set of summary tasks representing the board columns (e.g., Backlog, In Progress, Review, Done) and map individual cards to child tasks under the appropriate column summary. Card assignees, due dates, and status labels transfer as task fields. We flag the loss of visual Kanban layout in the migration report and note that Project Online with a Planner integration or a third-party Kanban add-in (such as from the Microsoft AppSource marketplace) can partially restore board-style visualization post-migration.

Planview Milestones map directly to Microsoft Project Milestones (tasks with zero duration). We preserve milestone names, scheduled dates, and associated task links. Milestone dates are frozen at export time to prevent the Planview date recalculation engine from shifting them after scoping. Any milestones linked to multiple upstream tasks carry those dependencies as predecessor links in the destination project.

Planview task-to-task dependency links map to Microsoft Project Finish-to-Start (FS) predecessors by default. If Planview dependencies use lead or lag time, we capture those values and apply them as Microsoft Project's Start-to-Start (SS), Finish-to-Finish (FF), or FS with positive or negative lag. Circular dependency detection runs on the source schema before export; any circular chains are flagged for the customer's PM to resolve before migration proceeds.

Planview Agile Sprints map to dated task groups in Microsoft Project. We create summary tasks named for each sprint, nest the sprint backlog items as child tasks, and apply StartNoEarlierThan constraints to match the sprint start date. Burndown data and velocity metrics are not carried forward; we export the raw sprint backlog as tasks and document the velocity baseline in a separate report for the customer to rebuild in Power BI if needed.

Planview workspace members map to Microsoft Project Resources. We extract user name, email address, and role from the workspace member list and create Generic Resources in Project. If the customer requires Resource allocation by person (rather than role), we populate the resource Initials, Max Units, and email in a custom field. Material resources and cost resources map from Planview cost or effort fields where available. Note that Microsoft Project Desktop does not have a built-in resource directory; resource assignment to tasks requires manual mapping in the Resource Sheet.

Planview time entries (hours logged per task per user) map to Microsoft Project Task Assignment Actual Work values. We export the Planview time log (task, user, date, hours) and populate the Assignment row in the destination project with actual work values and the logging date. Note that Microsoft Project Desktop does not include a built-in timesheet interface; time log reporting requires Project Online with a timesheet solution or a third-party PSA tool. We deliver time entry data in a format compatible with Microsoft Dynamics 365 Project Service Automation or any standard timesheet add-in the customer configures.

Planview documents stored within a Workspace map to hyperlinks attached to the corresponding Microsoft Project task. We export document metadata (filename, uploader, upload date, Planview URL) and create a task hyperlink pointing to the document's original Planview URL or a migrated SharePoint document library URL if the customer has set up a SharePoint migration alongside this project. Binary file blobs require a separate file transfer step orchestrated alongside the data migration. Document versioning is not preserved in the task-level hyperlink approach.

Planview Workspace-level custom fields export via the API if the customer's Planview plan includes API access for that workspace. We map each custom field to a Microsoft Project custom field (Text, Number, Date, or Flag type depending on the source data). Note that the out-of-the-box Planview-to-Portfolios sync exports only a very small default field set; we bypass that sync entirely and query the full API surface directly. Any custom fields requiring supplemental manual export from Planview support are flagged during scoping and coordinated before migration begins.