Migrate from Planview ProjectPlace to monday Work Management

ProjectPlace Workspaces map directly to monday.com Workspaces. We preserve workspace names, descriptions, and member lists. monday.com Workspaces are the top-level access boundary, so member lists determine Workspace-level permissions. Role-based permissions (Workspace Admin vs Member) from ProjectPlace map to monday.com Workspace roles during user provisioning.

ProjectPlace Kanban boards map to monday.com Boards. We map board name, column names, card assignments, and card-level metadata. ProjectPlace column status values (To Do, In Progress, Done) map to monday.com column Status options. Any custom ProjectPlace columns (labels, priority) map to monday.com Dropdown, Numbers, or Tags column types depending on data type. Board-level Integrations do not migrate; we flag them for manual reconnection post-migration.

ProjectPlace Tasks and Activities map to monday.com Items. We preserve assignees (mapped via User lookup by email), due dates, start dates, status, priority, and description. Sub-tasks in ProjectPlace map to monday.com Subitems attached to the parent Item. WBS codes from ProjectPlace migrate as a Text column for reference. Any task attachments are cataloged for the separate file migration step.

ProjectPlace Milestones are standalone schedule markers that can link to multiple tasks. We create Items in monday.com with a Milestone label column or a dedicated Status value (Milestone) to preserve the milestone distinction. Milestone dates migrate to the Timeline column. If a ProjectPlace milestone is linked to multiple tasks, we create one Item and note the linked task Items in a Connected Boards column or related items link for reference. The customer chooses milestone representation during scoping.

ProjectPlace Gantt views derive from task start/end dates and dependencies. We replay the full dependency tree as monday.com Items with a Timeline column for date rendering and a Dependencies column linking upstream-to-downstream relationships. The dependency type (Finish-to-Start, Start-to-Start, etc.) is stored as a Text field on each Item since monday.com Dependencies assume Finish-to-Start by default. Critical path annotations from ProjectPlace are noted in an Info column; the path itself must be recomputed in monday.com's Workload or Dashboard view.

ProjectPlace Agile boards with sprint cycles map to monday.com Boards with Groups representing sprint iterations or with a Timeline column filtered by sprint date range. Sprint names, start/end dates, and backlog items migrate. Burndown data is not carried forward as monday.com does not store calculated velocity metrics; we flag sprint velocity recalculation as a post-migration admin step.

ProjectPlace Workload View aggregates task assignments per user across all Workspaces. We export the underlying task-assignee data (Item ID, User, allocation percentage, date range) and map it to monday.com's People view configuration. The People view must be enabled per board in monday.com; we document the required board-level enablement as part of the handoff. Workload balance percentage from ProjectPlace migrates as a Numbers column on each Item.

ProjectPlace user accounts map to monday.com User records by email match. We preserve names, email addresses, and workspace membership. Role-based permissions (Admin, Member, Guest) from ProjectPlace map to monday.com Workspace roles. Guests with read-only access in ProjectPlace map to monday.com Guest accounts, which require a separate license on some monday.com tiers.

ProjectPlace custom fields per Workspace map to monday.com custom columns per Board. The column type is determined during scoping: text properties map to Text columns, numeric properties to Numbers, date properties to Date, and multi-select options to Dropdown or Tags. Because monday.com does not have a global field schema, custom columns are created per destination Board. We document the complete custom field taxonomy across all source Workspaces so the customer can configure destination columns consistently.

ProjectPlace time tracking per task (hours logged, date, user attribution) migrates to monday.com's native Time Tracking column on the corresponding Item. We map hours logged and date; user attribution resolves via the User email lookup. Reporting aggregations (weekly summaries, project totals) are not exported and must be rebuilt in monday.com using the Chart view or an integration to an external reporting tool.

ProjectPlace documents and files within Workspaces are cataloged by metadata (name, uploader, upload date, URL). Binary file blobs require a separate file transfer step orchestrated alongside the record migration. monday.com's File column type stores file references within Items; alternatively, we document the SharePoint, Google Drive, or Box integration setup for each board post-migration. File URL preservation is not guaranteed if the source URL structure changes.

ProjectPlace task comments and board discussions migrate to monday.com Item Updates. We preserve comment text, author (via User email lookup), and timestamp. Nested reply threads flatten to a single chronological update stream in monday.com. @mention formatting does not auto-link to monday.com User mentions; these are migrated as plain text and the customer manually notifies mentioned users post-migration.

File attachments on Tasks and Documents are cataloged during schema scan. Attachment references (filename, uploader, upload date) migrate as a Text column entry pointing to the original URL if accessible. Binary blob transfer is orchestrated as a parallel step using a separate file-migration protocol. We flag any attachment URL schemes (internal vs. external) that may break post-migration and recommend re-attaching from the destination file storage if the source system is decommissioned.