Migrate from Cobalt Project Manager to monday Work Management

Cobalt Projects map directly to monday.com Boards. The Project name becomes the Board name; Project description maps to the Board description field. We create the Board in monday.com first so that the Board ID is available as a parent reference for all Items migrated in the next phase. Cobalt's project-level custom fields map to Board-level Custom Fields added via the monday.com Custom Fields API before Item migration begins.

Cobalt Tasks map to monday.com Items on the corresponding Board. The Task name becomes the Item name; Task description maps to the Item description (stored as an update or text column depending on structure). Task status from Cobalt maps to a monday.com Status column with equivalent state values created during board setup. The Item is created after the Board is confirmed to exist, and the Item ID is captured for Subtask parent resolution.

Cobalt Subtasks map to monday.com Subitems. The Subtask name becomes the Subitem name; Subtask description migrates as a text column on the Subitem. We resolve the parent Item ID from the Cobalt parent-task reference and attach the Subitem via the monday.com Subitems API. Subitems inherit the parent Item's group and board context. Cobalt's Subtask-level custom fields map to Subitem Custom Fields using the same type-mapping logic applied to Tasks.

Cobalt Milestones do not have a direct monday.com equivalent. We handle this as a configuration mapping: Cobalt Milestone name and target date migrate as a dedicated Status column value (e.g., 'Milestone: Q1 Launch') and a corresponding entry on a Timeline column. If Cobalt milestones have dependencies, we map those to monday.com Dependency column links between Items. The customer chooses during scoping whether to use a dedicated milestone board, a dedicated group, or inline milestone status values.

Cobalt Time Entries map to monday.com Time Tracking column entries on the parent Item. Each time entry becomes a tracked time segment with the Cobalt duration, user, and date preserved. monday.com's Time Tracking column stores time per Item and supports multiple entries per user per day, matching Cobalt's multi-entry model. We map Cobalt's billable/non-billable flag to monday.com's time tracking label field.

Cobalt Assignees map to monday.com Person column values on Items and Subitems. We resolve assignees by email address against the monday.com workspace members. Any Cobalt assignee without a matching monday.com user is held in a reconciliation queue for the customer's admin to provision before Item import resumes. Multiple assignees on a single Task map to multiple Person column entries on the Item.

Cobalt Project status values (Active, On Hold, Completed, Archived) map to monday.com Status column labels on the Board. We create the Status column during board setup with values that match Cobalt's status vocabulary. The Status column appears as a coloured dot on the Item card.

Cobalt Task Priority (typically High, Medium, Low, or a numeric scale) maps to either a monday.com Numbers column or a Labels column depending on the customer's preference. Numeric priority scores migrate directly; label-based priorities require a value-mapping table created during board setup.

Cobalt Task start_date and due_date map to the monday.com Timeline column (start_date to Timeline start, due_date to Timeline end). The Timeline column is available from the Standard plan ($12/seat/mo) and above. If Cobalt stores only a due_date with no start_date, we set the Timeline start to the due_date minus the average task duration or a customer-defined default offset.

Cobalt Attachments migrate to monday.com File column entries on the corresponding Item or Subitem. We download each Cobalt attachment to local storage, then upload to monday.com via the monday.com Files API, capturing the returned file URL and attaching it to the Item via the File column. File name and any inline comment migrate as the file label.

Cobalt project-level custom fields (e.g., Client Name, Contract Value, Project Type) map to monday.com Board-level Custom Fields created via the Custom Fields API. We map Cobalt field types to monday.com column types: text fields to Text columns, numeric fields to Numbers columns, dropdown fields to Dropdown or Tags columns, date fields to Date columns, and checkbox fields to Checkbox columns.

Cobalt task-level custom fields map to monday.com Item-level Custom Fields using the same type-mapping logic as project-level custom fields. The Custom Field must exist on the Board before Item migration begins; we create all task custom fields during the board setup phase using monday.com's bulk Custom Field creation endpoint.

Cobalt Task dependencies (e.g., Task B blocked by Task A) map to monday.com Dependency column links between Items. We create the monday.com Dependency column during board setup and then link each dependent Item to its predecessor using the monday.com Column API. The Pro plan ($19/seat/mo) is required for the Dependency column feature.

Cobalt Tags or Labels applied to Tasks map to monday.com Tags column values. Tags stored as multi-checkbox properties migrate to Tags column entries. We normalise tag names during the transform phase to match monday.com's tag format and create any missing tags in the workspace during board setup.