Migrate from Cerebro to Trello

Cerebro Projects map to Trello Workspaces (the organizational container) with one Board per Project. Project name becomes the Board name, project description becomes the Board description, and project status (active/archived) is noted for manual triage. Tags applied at the project level become Workspace-level labels. We create the Workspace first, then provision one Board per Cerebro Project within it, preserving project-level metadata as Board attributes.

Top-level Cerebro Tasks migrate directly to Trello Cards. Task name becomes the card title, description migrates as card description, due date migrates to the card due date field, and assignee migrates to card member. Status in Cerebro maps to card position within the target List (To Do, In Progress, Done) based on the customer's status-to-list mapping defined at scoping.

Cerebro Subtasks nested one level below a Task migrate as Checklist Items within the parent Trello Card. Subtasks nested two-plus levels below a Task are flagged as structural exceptions: we convert them to linked child cards using Trello's Cards Power-Up if available on the destination plan, or document them as manual card-creation tasks for the customer's admin. Deep hierarchies exceeding Trello's flat model are documented in the structural exception report delivered at cutover.

Cerebro Tags migrate to Trello Labels with a one-to-one name mapping. Cerebro's tag taxonomy is team-defined and not globally enforced, so we deduplicate tag name collisions that occur across different Cerebro object types and normalize label names to Trello's 25-character limit. The customer chooses whether to apply labels at the card level or filter by label during migration validation.

Cerebro exposes Gantt chart dependency edges between tasks. Trello has no native dependency model, and no dependency Power-Up is included in Standard or below. We extract all dependency edges, document them in a dependency matrix (predecessor, successor, dependency type), and deliver this as a written artifact for the customer's admin to rebuild manually or via a selected Power-Up. Dependencies do not fail the migration but are not recreated automatically.

Cerebro stores media files on its own distributed server infrastructure. These files are not included in standard web exports and must be extracted by URL from the task export, downloaded individually, and re-uploaded to the corresponding Trello Card as a native attachment. Large files are chunked for re-upload, and failures are logged per asset for retry. Audiovisual commentaries are treated as linked media assets; thumbnail previews do not carry over. File size limits and re-upload failures must be handled explicitly per asset.

Cerebro Comments migrate to Trello Card Comments as plain text. Author attribution is preserved by resolving the comment author's Cerebro user to a Trello workspace member via the User mapping table. Inline media references in Cerebro comments are converted to download links pointing at the re-uploaded attachment at migration time. UI artifact strings from Cerebro's built-in translator feature are stripped during comment normalization.

Cerebro team and individual calendars aggregate task assignments and deadlines. Trello Calendar Power-Up (included in Standard and above) displays cards with due dates on a calendar view, but Cerebro calendar entries with all-day versus partial-day semantics and team availability overlays have no direct equivalent. We map task due dates to card due dates, document the calendar structure as a separate artifact, and recommend the customer configure the Calendar Power-Up post-migration to match their team availability view.

Cerebro Users migrate to Trello workspace members matched by email address. We extract every Cerebro user referenced on any migrating record and cross-reference against the Trello destination workspace. Any Cerebro user without a matching Trello member account goes to a reconciliation queue for the customer's admin to provision before record migration begins. Active versus inactive status is preserved in a custom field for audit.

Cerebro uses a permission-group access model where users belong to named groups with specific access rights per project. Trello uses workspace roles (Viewer, Member, Admin) and board-level permissions (Private, Workspace, Public). We extract all group memberships, map them to the closest matching Trello role, and flag any Cerebro group with no direct equivalent (custom permission sets, per-project granular rights) as requiring manual post-migration permission review and rebuild in Trello Workspace settings.

Gantt views in Cerebro are generated from task dates and dependency edges. Trello has no native Gantt chart; the Calendar Power-Up provides a partial timeline view but lacks dependency arrows and resource loading views. We extract all timeline data and dependency edges into a written Gantt reference document delivered at cutover. The customer's admin uses this to configure a third-party Power-Up or accept the Calendar Power-Up as the replacement timeline view.

Cerebro project templates enable consistent workflow cloning across recurring engagements. Trello does not import project templates directly; Board Templates are created manually or from existing boards. We document the full Cerebro template structure (board layout, default labels, default lists, default cards, and checklist templates) and deliver it as a reference so the customer's admin can recreate it as a Trello Board Template for future projects. Template migration is not automated.