Migrate from Cerebro to monday Work Management

Cerebro Projects map to monday.com Boards, with the option to create a monday.com Workspace per Cerebro project grouping if the customer uses multiple projects under a single account. Project name, description, status, dates, and tags migrate as board name, description, status column, and date columns. We preserve the original Cerebro project identifier in a custom column for audit traceability.

Cerebro's unlimited task nesting depth is the primary reconstruction challenge. We extract the full parent-child hierarchy, then map top-level Cerebro tasks to monday.com Items within a Board Group, and map second-level Cerebro subtasks to monday.com Sub-items. For nesting beyond two levels (Cerebro supports arbitrary depth), we use additional Board Groups as a third conceptual layer and flag the remaining depth for manual review or restructuring in monday.com, since monday.com natively supports only one level of sub-items.

Cerebro Subtasks map directly to monday.com Sub-items, preserving the parent Item reference, assignment, status, due date, and description. Sub-item ordering is preserved by position index. If the customer uses Cerebro's recursive subtask feature (subtasks of subtasks), those beyond the first sub-item level are flagged as requiring manual parent reassignment in monday.com.

Cerebro tags used to categorize any project element map to monday.com Label columns. We extract all tag values per task, create the corresponding Label options in the destination board, and assign them to each Item. Tag naming conventions vary by team; we normalize duplicates and merge identically named tags during the transform phase.

Cerebro Gantt chart dependencies expose explicit predecessor-successor edges between tasks. We export these as dependency pairs and recreate them in monday.com using the native Dependency column on items. Note that monday.com's Dependency column requires Pro plan ($19/seat) or above. If the customer is on a lower tier, we map dependencies to a Status-based workflow or document them as a manual checklist for admin review.

Cerebro stores media files—images, video, audiovisual commentaries—on its own distributed server infrastructure with URLs that are not included in standard exports. We extract all attachment URLs from the Cerebro task export, download each file individually (respecting source server rate limits with exponential backoff), then upload to monday.com storage via the monday.com API's file upload endpoint. File size limits (50 MB per file in monday.com) and any re-upload failures are flagged per asset for the customer's review. Audiovisual commentaries are treated as linked media assets; thumbnail previews are preserved where available in the export.

Cerebro comments on tasks migrate as monday.com Item Updates (the activity log entry on an item). Author attribution is preserved via user email mapping to monday.com team members. Inline media references in comments are converted to download links pointing to the re-uploaded media assets. We strip Cerebro's built-in translator UI artifacts during comment normalization, but any remaining localization noise requires manual review of comment content post-migration.

Cerebro team and individual calendars aggregate task assignments and deadlines. We map calendar entries to monday.com Item date columns (Start Date and Due Date), and reconstruct the calendar view using monday.com's native Timeline view (available on Standard plan and above). All-day versus partial-day semantics differ between platforms; we preserve the original Cerebro date-time values and flag any ambiguity for the customer to resolve in the destination.

Cerebro uses a permission-group access model where users belong to named groups with specific access rights per project. monday.com uses Workspace-level roles (Member, Admin, Viewer) and board-level permissions (Full, Limited, View Only). We extract all Cerebro group memberships, map them to the closest matching monday.com role or permission setting, and flag any group with no direct equivalent as requiring manual post-migration permission review. Users without an email match in monday.com must be provisioned by the admin before migration.

Cerebro Gantt views are generated from task start dates, end dates, durations, and dependency edges. We extract the timeline data (start, end, duration, % complete) and reconstruct the view in monday.com's Timeline column (Standard plan and above) or by using the native Gantt chart view if available on the customer's tier. Dependency arrows are drawn from the Dependency column configuration. Milestone tasks map to date-only items with a milestone indicator column.

Cerebro user records map to monday.com team members by email address. We extract every distinct user referenced on tasks, subtasks, comments, and permission groups, then match by email against the monday.com workspace members list. Users without a match are placed in a reconciliation queue for the customer's admin to provision in monday.com before record assignment migration proceeds. Active and inactive status is preserved as a custom field for audit.

Cerebro custom fields per project map to monday.com board columns. We extract the full custom field schema per Cerebro project, then create the equivalent monday.com column types: text fields to Text columns, numeric fields to Numbers, dates to Date columns, dropdowns to Dropdown columns, checkboxes to Checkbox columns. Custom field data migrates as column values on the corresponding items. Note that custom field types beyond monday.com's 30+ native column types may require conversion to the nearest equivalent or manual post-migration data entry.