Migrate from workspace.pm to monday Work Management

workspace.pm Projects map 1:1 to monday.com Boards. Each Project's name, status, start date, end date, owner, and cost fields migrate to the Board's name, top-level group, and column values. We create one Board per Project during migration. The monday.com board type (Team, Personal, or Shareable) is set based on the Project's visibility scope from workspace.pm. Workspace setup in monday.com maps to workspace.pm's portfolio grouping if the customer maintains a multi-board structure.

workspace.pm Tasks map directly to monday.com Items within their corresponding Board. Task title, description (rich text), status, assignee, due date, priority, and creation/modification timestamps migrate to the Item's name, description column, status column, person column, date column, priority column, and system timestamps respectively. The destination column types are configured during the pre-migration schema mapping phase.

workspace.pm Subtasks under Tasks map to monday.com Subitems (a native sub-item column type available on Pro and above). The parent Task-Item relationship is preserved by linking each Subitem to its parent Item. For accounts on monday.com Standard (which lacks Subitems), we flatten Subtasks into Items with a parent-reference column or a Group header. The ordering of Subtasks relative to the parent Task is preserved via the Item's position field.

workspace.pm Milestones (date-keyed project markers) have no direct monday.com equivalent. We map Milestone name and target date to a monday.com Date column with a label indicator, or we create a dedicated Group per milestone with the milestone name as the Group header. The customer chooses the approach during scoping. If workspace.pm milestones span multiple tasks, we add the milestone date as a mirrored date column on each affected Item.

workspace.pm predecessor-successor dependency pairs migrate to monday.com's native Dependency column, which is available on Pro ($19/seat) and Enterprise plans. We extract the dependency pairs from workspace.pm's export, then write the source Item ID and target Item ID into monday.com's dependency_column during the Item import phase. Cross-board dependencies require Enterprise; for Standard and below, we document the cross-board dependencies in a separate reference table for manual reconstruction.

workspace.pm custom fields at the project and task level map to the nearest monday.com column type: text fields to Text columns, picklists to Dropdown or Tags columns, numbers to Number columns, dates to Date columns, and checkboxes to Checkbox columns. We extract the full custom field schema (field names, data types, picklist options) from workspace.pm during the pre-migration audit before building the column mapping. The schema definition must be captured from workspace.pm's admin console because schema definitions are often absent from raw data exports.

workspace.pm's resource allocation records (user, role, allocation percentage, dates) map to monday.com's Person column. We export the resource assignment records and map the workspace.pm user reference to a monday.com email address. Any workspace.pm user without a monday.com account is held in the reconciliation queue for the customer's admin to provision before the migration proceeds. Allocation percentage from workspace.pm is stored in a Number column if the customer requires it; otherwise only the assignee assignment migrates.

workspace.pm time entries (user, date, hours, description) migrate to monday.com's Time Tracking column if the destination plan is Pro or above. On Standard, we migrate time entries as a Number column with hours and as a Text column with the description. The mapping preserves the user attribution and date so that time reporting can be reconstructed in monday.com's Workload view (Pro and above) after migration. Time entries that span multiple tasks in workspace.pm are migrated as separate Time Tracking entries against the corresponding Items.

workspace.pm discussion threads on Tasks (comment text, author, timestamp) migrate to monday.com Updates on the corresponding Item (Pro and above) or as a separate Note Item with the comment text and author attribution. Updates preserve the author and timestamp; Note Items store author and body as text. We migrate in chronological order and preserve threading where workspace.pm exposes parent-comment relationships. If workspace.pm comments include @mentions, these are stored as plain text in monday.com since the destination does not support @mention notifications from imported comments.

workspace.pm file attachments (filename, URL/reference, uploader, upload date) migrate to monday.com's File column (Pro and above) if the attachment is accessible via URL, or we store the file reference in a Text column with the filename and upload date for manual re-attachment. We do not download and re-upload binary files; the attachment metadata migrates so that the customer's admin can re-attach the actual files post-migration if monday.com does not support the original file host.

workspace.pm portfolios aggregate multiple projects under executive dashboards. monday.com has no native portfolio object. We export the portfolio-to-project membership from workspace.pm and reconstruct it in monday.com using one of three strategies chosen during scoping: (1) monday.com Folders containing the relevant Boards, (2) Tags applied across Boards representing portfolio membership, or (3) a master Board with Items representing each project in the portfolio and a Group structure representing the portfolio hierarchy. Strategy choice depends on how the customer uses portfolio dashboards in workspace.pm.

workspace.pm project-level status values (Active, On Hold, Completed, Archived) map to monday.com Status column values, which we configure during the pre-migration phase. Status color coding is preserved where workspace.pm exposes it. If workspace.pm uses custom status labels beyond the standard set, we add them as custom Status column values in monday.com to match the source terminology exactly.

workspace.pm cost and budget fields on Projects map to monday.com Number columns. If the destination plan is Pro and supports formula columns, we create a budget-vs-actual formula column that references the Number column and a spent column (populated from time entry hours times an hourly rate if the customer provides the rate). Budget reporting in monday.com is rebuilt as dashboard widgets post-migration; we document the recommended widget configuration during the handoff.

workspace.pm risk registers (risk name, probability, impact, mitigation, owner, status) migrate as a separate Board with Items representing each risk. We map probability and impact to Number or Dropdown columns, mitigation to a Text column, owner to a Person column, and status to a Status column. The customer chooses whether risks live as a standalone board or as Items within the project Board during scoping. Risk reporting is reconstructed as monday.com chart widgets post-migration.

workspace.pm meeting records (title, date, attendees, agenda, notes) associated with Projects migrate as monday.com Items with Date columns for meeting date/time, Person columns for attendees, and Text columns for agenda and notes. If the customer uses workspace.pm's calendar integration for meeting scheduling, we document the meeting-object migration separately and recommend using monday.com's Calendar view or a third-party calendar integration for ongoing scheduling post-migration.