Migrate from ProjectManager to monday Work Management

ProjectManager Workspaces map directly to monday.com Workspaces as the top-level container. Each Workspace in ProjectManager becomes a separate Workspace in monday.com, preserving the organizational boundary. Workspace-level settings (visibility, member list) migrate as Workspace settings in monday.

ProjectManager Projects map to monday.com Boards. The Project name, description, start date, end date, and status map to Board name, description, and status column. Project custom fields (ProjectFields) map to monday Column types selected during Board creation. If the customer's Projects use multiple status values, we configure a Status column with matching options.

ProjectManager Tasks map to monday.com Items within the target Board. Task name, description, start date, end date, priority, and TaskStatus migrate to Item name, description, and typed columns. Parent-child task hierarchies (WBS structure) map to monday's subitem relationship where the parent Item contains the child Item as a subitem, preserving the work breakdown structure. Task custom fields (TaskFields) map to additional Columns on the Board.

ProjectManager Tasks with dependency relationships (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) map to monday.com Items with dependency column configured. We import tasks in topological order to avoid triggering monday's dependency cascade and preserve the original manually-set dates. Four dependency types in ProjectManager map to monday's dependency column, which supports predecessor and successor linking.

ProjectManager TaskAssignees linking a Resource to a Task map to monday.com Person column values on the corresponding Item. We resolve the assignee by email against the monday Workspace members list. Any TaskAssignee referencing a Resource not yet in the monday Workspace is held in a reconciliation queue for the customer's admin to provision the user account before migration resumes.

ProjectManager Resources represent team members with availability windows and cost rates. Resources map to monday.com person entities within the Workspace. The Resource name, email, and availability map to monday user profile fields. Cost rates from ProjectManager do not map to a native monday field; we preserve them in a custom number column on the person's profile Board if the customer requires rate tracking, or flag for manual reconciliation.

ProjectManager ResourceTeams group Resources for scheduling and workload reporting. These map to monday.com Teams scoped to the Workspace. We preserve team memberships and cross-reference with TaskAssignees to ensure workload views are populated post-migration. The customer chooses during scoping whether ResourceTeams drive the monday workload reporting or whether a different grouping is preferred.

ProjectManager Teams (organizational membership, distinct from ResourceTeams) map to monday.com Teams or Groups depending on the customer's intended use. If the Teams object drives access permissions in ProjectManager, we configure monday Teams to match membership. If it drives workload grouping, we align with the ResourceTeam mapping decision above.

ProjectManager Risks are standalone objects linked to Projects. We create a dedicated Risk Board in the destination Workspace and map each Risk to an Item with Status column set to Open, Mitigated, or Closed and a Severity or Priority column matching the source Risk severity. Risk description, probability, and impact migrate to text and number columns.

ProjectManager ProjectFields (custom properties scoped to the Workspace) require two-step migration: field schema discovery via GET, then field creation, before values can be written. We replicate this by creating monday Column types that match the ProjectField type (text, number, date, choice). For choice fields, the options list migrates as monday column labels. Field values write to the corresponding Column on each Board Item after column creation.

TaskFields work identically to ProjectFields but are scoped to Tasks. We handle both field definitions and per-record values using the same two-step process. The destination Column type is selected based on the TaskField data type (string becomes text, number stays number, date stays date, choice becomes dropdown or multi-select). Not all ProjectManager field types have a direct monday equivalent; we select the closest type and flag any precision loss.

ProjectManager Tags and TaskTags are lightweight labeling objects. We map tag names to monday.com Labels on the Board, preserving the label name and color. Item-label associations migrate as Label assignments on the corresponding Items. monday Labels are board-scoped, so we create the label set on each destination Board where source tags are present.

ProjectManager Timesheets record actual hours logged by Resources against Tasks. We migrate hours as time tracking entries on the corresponding monday Items. Billing rates embedded in historical Timesheet records do not map directly to monday's time tracking model, which records duration only. We flag Timesheet data during discovery and give the customer the choice to migrate hours only or attempt rate reconciliation, which may require manual cleanup. Enterprise customers relying on detailed billing history may need a custom solution.

ProjectManager UserRoles define permissions within a Workspace. Role definitions are proprietary to ProjectManager. We map source permission profiles to the closest matching monday Workspace role (Member, Admin, or Viewer). Custom roles that have no direct monday equivalent are flagged for the customer's admin to configure post-migration.