Migrate from Cobalt Project Manager to Trello

Each Cobalt Project maps to a Trello Board. We create the Board in the customer's Trello Workspace and preserve the Project name as the Board title and Project description as the Board description. If the Cobalt Project has a start date and end date, we note these in the Board description for the admin to use when configuring a Timeline view (Premium) or setting up a Gantt Power-Up post-migration.

Cobalt Milestones are milestone markers on a project timeline. We create a Trello Card with the Milestone name and the due date set to the Milestone target date, then attach a Label (color-coded by milestone category or priority) to that Card. If the customer uses named Milestone categories, we create equivalent Label colors in Trello. We do not create a separate Label for every Milestone instance because Trello limits Boards to 50 Labels; for migrations exceeding 50 Milestones we use a naming convention on a single Label color to group milestone cards.

Each Cobalt Task maps to a Trello Card. The Task name becomes the Card title, Task description becomes the Card description, and the Task status maps to the Card's List position (we define the List names from the distinct Cobalt Task status values during scoping). Assignee resolves from Cobalt owner email to Trello Workspace member and is set as the Card member. Due dates migrate from Cobalt Task due-date fields to Card due dates.

Cobalt Subtasks map to Checklist items within the parent Trello Card. We preserve Subtask completion status as the Checklist item checked state. If a Cobalt Subtask has its own assignee or due date, we add that information as a Checklist item note rather than creating a separate Card, because Trello does not support nested Cards natively.

Cobalt Task priority levels (typically High, Medium, Low, or numeric) map to Trello Label colors. We agree on a priority-to-color mapping during scoping and apply the Label to each Card during migration. If the customer also uses Trello Premium, priority can be represented as a Custom Fields dropdown for more precise sorting.

Trello has no native time-tracking object. If the destination Workspace is on Standard or Premium, we create a Number Custom Field on each Card and populate it with the summed time-entry hours from Cobalt. If the Workspace is on the Free tier, time entries are preserved as a structured note appended to the Card description with the hours, date, and user for audit. We flag during scoping which approach the customer prefers based on their Trello tier.

File attachments from Cobalt Tasks are uploaded to Trello Cards as native Card attachments (Trello supports up to 10MB per file on Free, 250MB on Standard/Premium). Files exceeding Trello's limit are linked from the Card description as an external URL pointing to the source location (Google Drive, SharePoint, or the customer's document store). We do not migrate file versions; only the current attachment version moves.

Cobalt Task comments map to Trello Card comments with the comment author resolved to the matching Trello Workspace member by email. Comment timestamps are preserved by posting the comment at the original timestamp (within API constraints). If the comment author has no matching Trello account, the comment is posted by the migration service account with the original author name noted in the comment body.

Cobalt Users referenced on Tasks, Projects, and Milestones are resolved by email against the destination Trello Workspace member list. We create a reconciliation report of any Cobalt User without a matching Trello account; the customer's admin provisions missing accounts before the migration runs so that Cards are assigned to the correct members rather than left unassigned.

Cobalt Tags map to Trello Labels on the corresponding Card. If the number of distinct Tags exceeds 50 per Board (Trello's hard limit), we consolidate low-frequency Tags into an 'Other' Label and document the full tag-to-label mapping for the admin to adjust post-migration. Tag colors are approximated to the nearest Trello Label color palette.

Cobalt custom properties map to Trello Custom Fields by type: text properties to Text Custom Fields, numeric properties to Number Custom Fields, date properties to Date Custom Fields, and picklist properties to Dropdown Custom Fields. This mapping requires the destination Workspace to be on Standard or Premium; on Free tier we preserve custom property values as structured text appended to the Card description and flag the limitation in the scope document.

Boolean custom properties from Cobalt map to Checkbox Custom Fields on Trello Standard/Premium. If the Workspace is on Free tier, boolean flags are represented by adding or removing a specific Label color to indicate True/False state. We agree on the boolean-to-label convention during scoping.

If Cobalt tracks project-level status (Active, On Hold, Completed, Archived), we represent this in Trello using the Board background color (Trello's built-in Board color coding) or by creating Lists named for each status and placing project Cards accordingly. The approach is agreed during scoping based on how the customer uses Cobalt project status.

Cobalt attachment metadata (filename, upload date, uploaded by user) migrates as Trello attachment card data. We do not migrate the attachment version history; the most recent file version is the one that moves.