Migrate from CONTACT Project Office to monday Work Management

CONTACT Project Office Projects map to monday.com Boards. Each Board is created with the source Project name, and the primary Group inside the Board is created with the default group name or the Project's top-level task grouping. We set Board privacy to the monday.com workspace default during migration and flag for the customer's admin to configure board-level permissions post-migration.

CONTACT Project Office Tasks map to monday.com Items. The Task name becomes the Item title. Task description maps to the Item's Update or Notes field depending on the content type. We set Item Status to a default state (commonly First Column) and flag that the customer's admin should configure the board's Status column values to match their original task stage lifecycle before users access the board.

CONTACT Project Office Subtasks map to monday.com Subitems attached to the parent Item. Subitem title, description, assignee, due date, and status all transfer. Subitems inherit the parent Item's board context, so no cross-board reference resolution is required. If the source subtask has no parent Task, we escalate to the migration PM for resolution before import.

Task and Subtask Assignees map to monday.com Person column values. We resolve assignees by email match against the monday.com workspace User list. Assignees without a matching monday.com User go to a reconciliation queue for the customer's admin to provision before the main import phase. We do not create monday.com Users as part of the migration; the platform requires admin provisioning.

Each CONTACT Project Office Custom Field maps to a monday.com Column of the closest matching type: text fields map to Text columns, numbers to Number columns, dates to Date columns, dropdowns to Dropdown columns, and boolean flags to Checkbox columns. We create the Columns on the destination Board before Item migration begins. Complex custom field types (e.g., multi-select from concatenated values) require a pre-migration normalization step.

File attachments linked to Tasks and Subtasks migrate as Files attached to the corresponding monday.com Item via the Item's file attachment feature. We download attachments from the source system, store them in a FlitStack AI staging bucket, and upload them to monday.com using the Files API. File naming conventions preserve the original filename. Files over 500 MB per individual attachment require chunked upload handling.

Task and Subtask Comments map to monday.com Item Updates. Comment body, author, and timestamp all transfer. If the source comment references another Task or Subtask by ID, we replace the reference with the migrated Item name. Rich text in comments is converted to monday.com's update formatting. Author resolution uses the same email-match approach as Assignee resolution.

Task stages from CONTACT Project Office (e.g., Open, In Progress, Review, Done) map to monday.com Status column values. We create the Status column on the destination Board with values matching the source stage names and colors as closely as possible. The customer's admin refines the Status column configuration during the sandbox review phase.

Task due dates map to monday.com Date column values on the Item. Start dates, if present in the source, map to the Date column's include-time option or to a separate Date column. If the source has both a start and end date, we use monday.com's Timeline column to represent the full date range on a single column.

If CONTACT Project Office stores explicit task dependency relationships (predecessor links, parent task references, or blocking relationships), we map these to monday.com's Dependencies column on the target Board. Dependencies column values reference Item IDs that must exist before the dependency row is inserted, so we import Items first and then add Dependencies as a secondary phase. Cross-board dependencies are supported but require careful Item ID tracking across Boards.

If the source has nested Projects (parent Project containing child Projects), we map this to a monday.com workspace containing multiple Boards with a naming convention that preserves the hierarchy (e.g., Parent Project Board with child Boards inside the same workspace). Groups within a Board are used for top-level task categorization rather than project hierarchy. We flag any nested-project scenario during discovery for explicit customer decision on the target structure.

Task tags or labels from CONTACT Project Office map to monday.com Tags column values on the Item. Tags are free-form in monday.com, so no pre-creation of the tag list is required. If the source uses a structured taxonomy for tags, we preserve it as-is in the Tags column and note for the customer that Tags can be converted to a Dropdown column for stricter data governance.

If CONTACT Project Office tracks time spent on tasks, we map this to monday.com's Time Tracking column. Time values migrate as logged durations in hours and minutes. Note that monday.com's Time Tracking column records elapsed time logged against an Item rather than start/end timestamps, so we preserve the duration value only.

Automations and rule-based workflows from CONTACT Project Office do not migrate to monday.com because the automation models are structurally incompatible. We deliver a written inventory of every active Automation with its trigger, conditions, and actions for the customer's admin to rebuild in monday.com's Automation builder or monday workflows. This inventory is delivered as part of the migration handoff package.

Reports and Dashboards from CONTACT Project Office do not migrate. monday.com has a separate Dashboard product with different widget types, filters, and data sources. We deliver a written report inventory describing each source Report's structure and recommended monday.com Dashboard equivalent, including which Boards and Columns supply the underlying data. The customer's admin rebuilds the Dashboards post-migration.