Migrate from Breeze to Microsoft Project

Breeze Projects map 1:1 to Microsoft Project plans. We export project name, description, start date, due date, status, and owner. Breeze project owner maps to a Microsoft Project Resource (the project manager role). Active and archived Breeze projects migrate; we recommend archiving completed projects separately to keep the active plan set clean in Microsoft Project.

Breeze Tasks map to Microsoft Project tasks with task name, description, start date, finish date, priority, and assignee preserved. Breeze status (To Do, In Progress, Done) maps to Microsoft Project percent complete or custom flag fields, since Microsoft Project uses duration-based scheduling rather than status-based progression. Assignees from Breeze map to named Resources in the project resource sheet.

Breeze subtasks export with the full parent-child relationship preserved as outline hierarchy in Microsoft Project. Breeze supports one level of subtasking; Microsoft Project supports multiple outline levels. We maintain the single-level Breeze structure as-is and flag deeper nesting possibilities for the customer's PMO to configure post-migration.

Breeze per-project custom field schemas require pre-migration reconciliation. We detect every unique field name across all Breeze projects, identify type conflicts (text vs dropdown for the same field name), and resolve them to a single Microsoft Project custom field type before schema creation. The resolved schema is deployed to Project Online before record import. Fields with no type conflict map directly; conflicting fields are flagged in the scoping report and resolved with explicit customer input.

Breeze Tags are flat label-style identifiers. We export tags as an array per task and write them to a Microsoft Project custom text field. Where the customer's PMO requires hierarchical grouping of tags (e.g., categories and subcategories), we document the recommended outline code structure and flag post-migration taxonomy cleanup as a configuration task.

Breeze time entries (billable hours, duration, date) linked to tasks map to Microsoft Project Task > Work field. We write the logged duration as hours into the Work field and preserve the date. Breeze billable flag maps to a custom flag field in Microsoft Project. Note that Microsoft Project's Work field reflects resource assignment hours rather than standalone billable time entries; the time-tracking nuance requires post-migration review for teams that depend on billable reporting.

Breeze attachments are referenced by URL in the API. We export the attachment URL, filename, size, and upload date as a hyperlink attached to the relevant Microsoft Project task. Actual binary file content requires a separate file-system export from Breeze's storage; we coordinate this in parallel with the API export to minimize migration window time.

Breeze Users referenced as task assignees map to Microsoft Project Resources. We extract the user roster by email and create Resource records in the destination project. If a Breeze assignee has no corresponding user in the destination Microsoft 365 tenant, we flag them in the reconciliation report and the customer's admin provisions the resource before record import resumes.

Breeze task statuses (To Do, In Progress, Done, Archived) export as flag fields or percent-complete values in Microsoft Project. Breeze project-level pipeline stages map to summary task groupings or custom flag fields. We preserve the per-project status schema as documented during scoping but note that Microsoft Project's scheduling model does not use status as a primary task driver.

Breeze does not expose task-level comments via its public REST API. We cannot programmatically export comment history. Customers who rely on comments for project context must use Breeze's in-app CSV export or take screenshots before the migration window. We flag this gap during scoping and advise customers to budget time for manual comment recovery if comment history is critical for audit or compliance.