Migrate from Breeze to Trello

Breeze Projects map directly to Trello Boards. We export project name, description, start/due dates, status, and owner. Trello Boards have no native start/due date fields at the board level, so we preserve these as the first Card in a designated 'Project Metadata' List with dates in the card description, or as Custom Fields on the board if the Custom Fields Power-Up is active. Project status (active, archived) maps to Trello's open vs archived Board state.

Breeze Tasks map to Trello Cards with the task name as Card title and the task description as Card description. Breeze status (To Do, In Progress, Done) maps to Trello Lists (we create Lists named after each Breeze status value present in the source project). Assignee, priority, and due date migrate to Card members and due date fields. Breeze Task IDs are preserved as an external reference in the Card description for audit trail.

Breeze Subtasks map to Trello Checklist items on the parent Card. Breeze supports one level of subtasks; Trello Checklists are a flat list, so the hierarchy depth maps cleanly. Completed subtask status in Breeze maps to the checked state of the Checklist item. If the destination uses a dedicated Power-Up for hierarchical checklists, we flag that option during scoping.

Breeze Custom Fields require per-project reconciliation before mapping to Trello. Breeze allows the same field name (e.g., 'Priority') to be a text field in one project and a dropdown in another. We detect each project's field schema during scoping, resolve type collisions where the same name has different types across projects (by appending a project-scoped suffix or flattening to text), then create matching Trello Custom Field definitions on each destination Board before Card import. This is the most labor-intensive object in a Breeze-to-Trello migration.

Breeze Tags are flat label-style identifiers attached to Tasks. We map them to Trello Labels on Cards. Trello Labels have a name and color; if Breeze Tags carry no color data, we assign a default color or cycle through the available palette. Trello Labels are board-level (one label set per Board), so if a Breeze workspace has cross-project tag consistency, we replicate the label set on each destination Board. If the customer used Tags as a taxonomy with implicit hierarchy, we flatten them to flat labels with a post-migration cleanup recommendation.

Breeze Time Entries (billable hours, duration, date, and description) have no native Trello equivalent. We convert each Time Entry to a Checklist item on the parent Card with the format '[HH:MM] Description - Date'. If the destination Trello workspace has a time-tracking Power-Up active (e.g.,, Time Tracking by Cor vena or Tempo), we preserve time entries as Power-Up records linked by Card ID. Without a Power-Up, the checklist conversion is the functional equivalent and is the most honest representation of the data in Trello's native structure.

Breeze stores attachments in its file system and exposes them via URL in the API. We export the attachment metadata (filename, URL, size, upload date). We write the attachment URL as a Trello Card attachment link. Actual binary files require a separate file-system export session from Breeze that we coordinate in parallel with the API export to minimize the migration window. Trello accepts URL attachments natively, so the reference migrates without transformation; the customer must ensure the Breeze storage account remains accessible for the file download phase.

Breeze Users (email, name, role) map to Trello Board Members. We export the user roster and map task assignees by email match against Trello member accounts. Trello permissions operate at the Board level (admin, normal, observer) with Card-level member assignment; Breeze role-based permissions map to Trello Board roles and do not enforce at the task level. If the destination uses a different identity system (Google Workspace, Atlassian account), we flag the SSO configuration requirement during scoping.

Breeze task statuses (To Do, In Progress, Done, Archived, plus any custom per-project statuses) map to Trello Lists within each Board. We extract the per-project status schema, create one Trello List per unique status value, and map card placement to the corresponding List. If Breeze uses multiple pipelines per project, we create separate Boards per pipeline to preserve pipeline context, which Trello natively supports.

Breeze task priority (Low, Normal, High, Urgent) has no direct Trello native field. We map priority to Trello Labels with a reserved naming convention (e.g., label name 'Priority: High') applied to Cards. Alternatively, for workspaces using Trello Card Covers, we assign cover colors by priority level. The customer chooses the strategy during scoping.

Breeze does not expose task-level Comments via its public REST API. We cannot export comment history programmatically. If comment data is required in Trello, customers must use Breeze's in-app CSV export to extract comments manually before migration, or take screenshots of comment threads. We flag this gap during scoping and advise customers to budget time for manual comment recovery. Trello Card comments are not generated from this source data.

Breeze workspace settings (notification preferences, default views, working days) have no direct Trello equivalent. These are organizational preferences that require manual reconfiguration in Trello's Board settings post-migration. We document the source settings in the migration inventory so the admin can apply them to each destination Board.