Migrate from GUIDEcx to monday Work Management

Each GUIDEcx Project becomes a monday.com Board. The Project name maps to the Board title, planned end date becomes a Date column, status label and status_category map to a Status column, and project-level custom fields map to custom columns on the Board. GUIDEcx's project description maps to the Board description field. We create one Board per Project so that the project-level container is preserved and cross-project reporting can run at the board level via monday's Dashboard.

GUIDEcx Phases map to monday Board Groups. The Phase name becomes the Group name, and the Phase's planned start and end dates map to Date columns on the group's items. GUIDE 1.0 Phases require the self-serve GUIDEcx clone tool before migration; we flag any 1.0 template origins during scoping. A documented GUIDEcx bug causes phase attachments and project role assignments to drop during API-created phases—we extract these separately and re-attach files at the destination as file columns on the relevant items.

GUIDEcx Milestones can map to either a monday Group (if the milestone represents a major phase checkpoint) or a named Status column value with a date column. We determine the mapping during scoping based on whether the customer uses milestones as pure date markers or as grouping containers for tasks. Milestone dependencies (milestone-to-milestone finish-to-start chains) become monday Dependency column entries where the milestone item is a parent to the dependent item.

monday.com supports nested groups within a Board as of recent releases. GUIDEcx Task Groups map to sub-groups within the Phase Group, preserving the sort order and assignee list. If the destination workspace does not have nested groups enabled, Task Groups fall back to a custom text column that acts as a label within the parent Group. We validate the nesting capability against the destination workspace during scoping.

Each GUIDEcx Task becomes a monday Item. Task name maps to Item title, due date maps to a Date column, status maps to Status column, instructions map to a Text column, and assignee resolves to a Person column via email lookup. Checklist items on GUIDEcx tasks (which have known migration unreliability in the 2026 release notes) are treated as a structured JSON array in a custom Text column or as a sub-item list in monday. The GUIDEcx completed_date bug means we cross-reference task export data against direct API calls to fill gaps.

GUIDEcx finish-to-start task dependencies map to monday's native Dependency column. We preserve the full dependency graph but flag known GUIDE 2.0 bugs: subtask-child shared dependencies and N/A-marked tasks that break dependency chains. These are filtered out during export and flagged in the reconciliation report. In monday, we re-draw the dependency arcs using only the validated relationships.

GUIDEcx Custom Fields V2 (Text, Date, Email, Number, Dropdown) map to monday column types of equivalent definition. We pull field type definitions from the GUIDE 2.0 Data Dictionary during scoping because the standard task export only includes field values, not schema. Dropdown fields in GUIDEcx become Dropdown columns in monday with the same option list. Text fields become Text columns; Number fields become Numbers columns with any decimal precision preserved.

GUIDEcx tags are preserved as a tag list in monday. We apply the tags to the corresponding Items after import. The customer chooses during scoping whether tags become monday native Tags (searchable across boards) or a label-based Dropdown column for tighter column filtering. Note that tags on template-level tasks in GUIDEcx do not always propagate to project-level tasks—a known GUIDEcx issue we flag and handle by re-evaluating tag assignments at the task level rather than relying on template propagation.

GUIDEcx Customer Team contacts (external stakeholders assigned to the project) map to monday Person column values or Guest accounts, depending on whether the destination monday workspace has Guest access enabled. Customer Roles (internal role labels) map to a Text or Dropdown column on the item. We extract the full Customer Team roster during scoping and flag any contacts that cannot be matched to an email in the monday workspace, routing them to a manual handoff list.

Phase-level and project-level attachments from GUIDEcx migrate to monday File columns on the corresponding Items. GUIDEcx's API-created phase bug (where attachments drop) is handled by extracting file metadata separately from the phase record and re-attaching during the migration load. We download files from GUIDEcx's storage, upload to monday via the API, and attach to the correct item. Files without a resolvable target item are logged for manual assignment.

GUIDEcx Time Records map to monday's Time Tracking column or a custom Numbers column depending on the destination workspace's plan. The 2026 release notes document missing values in the GUIDE 2.0 Time Records dataset—we cross-reference API export against the dataset and flag gaps in the reconciliation report. If the customer uses time records for billing, we recommend a dedicated time-tracking integration rather than relying on the migrated values alone.

GUIDEcx task comments are retrieved via API and represented in monday as Update items linked to the corresponding Item, preserving the comment body, author (via Person column), and timestamp. Embedded links and @-mentions in comments are preserved as text. We do not migrate embedded images as separate file attachments; they remain as URL references in the Update body.