Migrate from Priority Matrix to monday Work Management

Priority Matrix Projects map to monday.com Boards. Each Project becomes a separate Board in the destination workspace, with the Project name as the Board name and the Project description preserved in the Board description field. We recommend grouping related Projects into a monday.com Workspace during scoping so that the top-level organization matches the customer's existing Priority Matrix project hierarchy.

Priority Matrix Items migrate directly to monday.com Items. The Item title maps to the Item name, the Item body/description maps to the monday.com description column, and the creation date and last modified date preserve as native date metadata. Completion status migrates as a Status column value. Items without a due date are flagged during scoping so the destination does not receive null date columns where the customer expects populated due dates.

The four quadrants (Do First, Schedule, Delegate, Eliminate) are a Priority Matrix convention with no native monday.com equivalent. We encode the quadrant label as a custom Status column (created during migration) or as a Label tag on each migrated Item. During scoping, the customer chooses whether to create four explicit status values mapping to each quadrant or to use a Labels column for more flexible tagging. We document the chosen mapping and recommend configuring monday.com board filters by quadrant label so teams can replicate the quadrant view they relied on in Priority Matrix.

Due dates on Priority Matrix Items migrate as monday.com Date column values. We preserve the original timezone where available. Items without due dates are flagged as undated during scoping. Calendar Sync entries from Priority Matrix (items synced to external calendars) are converted into native due dates with a flag noting they originated from calendar sync; the live calendar link is not recreated in monday.com.

Priority Matrix Items can have one or more assignees. We extract assignee email addresses and map them to monday.com User accounts by email match. Orphaned assignees (users present in Priority Matrix but not provisioned in monday.com) are flagged in a reconciliation report for the customer's admin to provision before record import resumes. Migration cannot proceed past assignee resolution because monday.com's People column requires valid user references.

Priority Matrix Tags migrate as monday.com Labels or a custom multi-select column, depending on whether the customer uses Labels for cross-board classification or column-specific tagging. We extract all distinct tag names during scoping and recommend a tag strategy before migration. Labels are the preferred mapping because they appear on the Item card regardless of board, matching Priority Matrix's cross-project tag behavior.

Priority Matrix custom fields on Items and Projects migrate to monday.com custom columns. We map field types during schema alignment: text fields to Text columns, numbers to Numbers columns, dates to Date columns, and checkbox fields to Checkbox columns. The customer chooses column placement during board design. Custom fields are pre-created in the destination before any Items are imported.

File attachments on Priority Matrix Items are exported and re-uploaded to monday.com File columns. We preserve the original filename and note the original uploader in the Item description. Attachment-heavy accounts (over 500 files) require feasibility assessment before migration begins because file re-upload throughput depends on monday.com file size limits and network conditions. We flag accounts exceeding this threshold during scoping.

Priority Matrix comments migrate to monday.com Updates on each Item. Comment text, author, and timestamp preserve. Comment ordering is maintained by posting updates in chronological sequence. If the original author is not a monday.com user, the update is attributed to the migration service account with the original author name noted in the comment body.

Priority Matrix Templates define pre-populated Item structures within a Project. We migrate the template schema as draft Items in the destination Board, preserving field structure and custom field definitions but clearing completion statuses and due dates so the template can be instantiated as new Items. Template-to-active-Item conversion is documented separately for the customer's admin.

Priority Matrix user accounts (name, email, role) map to monday.com Workspace members. We extract all users referenced on Items, Projects, and Comments and match by email against the monday.com workspace. Any Priority Matrix user without a matching monday.com account is held in a provisioning queue. monday.com licensing (Basic, Standard, Pro, Enterprise) determines which users receive paid seats versus free guest access.

Priority Matrix Calendar Sync entries create separate date records outside the native due date field. We deduplicate by Item ID during extraction, keeping the native due date and flagging the calendar link as inactive post-migration. The original calendar sync destination (Outlook, Google Calendar) is not recreated in monday.com; teams set up monday.com's native calendar integration post-migration if required.