Migrate from Breeze to monday Work Management

Breeze Projects map 1:1 to monday.com Boards. We preserve the project name, description, start and due dates, status, and owner. Each Breeze Project becomes a monday.com Board with its own column schema. If the customer uses Breeze's Master Project Board to aggregate sub-projects, we create a monday.com workspace folder and place the individual boards within it to replicate the hierarchy. The board privacy settings and team access permissions are configured in monday.com based on the Breeze project's access level.

Breeze Tasks are the core migration unit and map directly to monday.com Items. We export task name, description (migrated as rich text), status, priority, assignee (via email lookup), due date, and custom fields. Breeze Task IDs are preserved as an external ID column in monday.com so that linked objects (Subtasks, Time Entries) can resolve their parent reference during import. If the destination board uses Groups (organized by status, phase, or team), we distribute Items into Groups based on the Breeze Task status value.

Breeze Subtasks (one level of nesting under Tasks) map to monday.com Subitems. We preserve the parent-child relationship by resolving the parent Breeze Task ID to the corresponding monday.com Item during import. Breeze Subtask fields (name, assignee, due date) become Subitem fields in monday.com. If a customer relies on deeper task hierarchies than one level, we flag the limitation and suggest flattening to Subitem level during scoping.

Breeze per-project custom fields map to monday.com Board columns. This is the highest-risk mapping in the migration because Breeze enforces no global field schema—a field named Priority can be a text field in Project A and a dropdown in Project B. We detect field schemas per project during export scoping and build a field map per board. Name collisions with type conflicts are resolved with explicit type-mapping before monday.com column creation. monday.com's supported column types (text, number, date, dropdown, checkbox, link, file, etc.) are matched to the detected Breeze field type, and any unsupported Breeze field types are flagged for the customer's admin to handle post-migration.

Breeze Tags are flat, label-style identifiers attached to Tasks with no hierarchical taxonomy. We export tags as an array per task. monday.com Tags are flat labels on Items and do support grouping by topic, but there is no native hierarchical taxonomy either. We write Breeze tags directly to monday.com Tags. If the customer uses Breeze tags to simulate a taxonomy (e.g., tagging by client, project type, and priority simultaneously), we advise on the use of separate monday.com Tag topics post-migration as a follow-up cleanup task.

Breeze Time Tracking produces time entries linked to Tasks with billable hours, duration, and date. We export all time entries and write them as either a number column (hours) or duration column on the parent monday.com Item. Parent reference resolution is critical: we resolve each time entry's Breeze Task ID to the corresponding monday.com Item ID using the external ID column before inserting. Time entries without a resolvable parent task are held in a reconciliation queue.

Breeze Users are referenced by email, name, and role. We export the full user roster and map each task assignee by email to the monday.com workspace member. monday.com requires that a user be provisioned as a workspace member before they can be assigned to an Item. We resolve assignees by email match. Any Breeze User without a matching monday.com workspace member goes to a reconciliation queue for the customer's admin to provision before Item assignment proceeds.

Breeze uses a fixed set of task statuses (To Do, In Progress, Done, Archived) customizable per project. We extract the per-project status schema and map each Breeze status value to a corresponding monday.com Status column value. If Breeze uses custom status labels (e.g., Review, QA, Blocked), we create matching Status column options in monday.com before Item migration. The status column is placed as the first or second column on each board so that the task status is immediately visible in board view.

Breeze attachments are stored in Breeze's file system and referenced by URL in the API. We export the attachment URL, filename, size, and upload date. monday.com File columns can store URLs referencing external files. The actual binary file download must be performed separately from Breeze's file export process before migration day, and the customer coordinates a parallel file-system export session to minimize the migration window. We write the attachment metadata as URL references on the corresponding monday.com Item.

Breeze does not expose Comments via its public REST API. We cannot export task-level comments programmatically. This is a known platform gap documented in Breeze's API limitations. If comments are critical to project context, customers must use Breeze's in-app manual export or take screenshots before migration. We flag this gap during scoping, advise on manual comment recovery workflows, and exclude comments from the migration scope entirely. Monday.com item updates and comments are not populated from Breeze because the source data does not exist in an accessible format.

Breeze recurring task rules and automation triggers are not migratable as code to monday.com's automation framework. We do not transfer automation logic. We deliver a written inventory of every active Breeze automation rule and recurring task configuration with its trigger, conditions, and actions, and the customer's admin rebuilds equivalents using monday.com's automation builder. Monday.com's Standard and Pro plans include automations with triggers, conditions, and actions that can replicate most Breeze automation patterns.

Breeze project reports and progress dashboards are not migrated. monday.com Dashboards are a separate view layer that aggregates data across boards using widgets (numeric, chart, calendar, timeline). We deliver a written map of every Breeze report that existed, the data it referenced, and the recommended monday.com Dashboard widget configuration to reproduce the view. The customer's admin or a monday.com partner rebuilds the dashboards post-migration.