Migrate from Breeze to Asana

Breeze Projects map directly to Asana Projects. We preserve the project name, description, start date, due date, status, and owner. Breeze's project-level status field maps to Asana's project privacy setting and color label since Asana does not have a project-level status enum beyond Archived. If Breeze projects are set to Archived, we map them to Asana's Archived status on the project. Owner is resolved by email match against the destination Asana workspace members.

Breeze Tasks map to Asana Tasks. We preserve task name, description (rich text), due date, start date, priority, assignee, and status. Breeze task IDs are stored as external references on the Asana task for traceability. Breeze's To Do, In Progress, and Done statuses map to Asana's default section or to Custom Fields for status if the customer requires a named status column in List view.

Breeze supports one level of Subtasks under Tasks. We export the full parent-child relationship and recreate it as Asana Subtasks under the parent Task. Breeze task IDs are preserved in the Asana task notes or as a custom field for reconciliation. If any Breeze subtask contains nested subtasks, we flag those records for the customer to restructure post-migration since Asana supports infinite nesting but the source data had a non-standard depth.

This is the most complex mapping in a Breeze-to-Asana migration. Breeze allows each project to define its own custom field set, so the same field name can be a text field in one project and a dropdown in another. We inspect every Breeze project's field schema during export scoping, detect all unique field names across projects, resolve type collisions (for example, Priority as text in Project A and dropdown in Project B), and build a unified Asana global Custom Field set. We then apply each field to the relevant Asana projects via Custom Field Settings. Customers are advised during scoping if significant type collisions exist and must confirm the resolution strategy before migration begins.

Breeze Tags are flat, label-style identifiers attached to Tasks. Asana Tags are also flat. We export tags as an array per task and create corresponding Tag records in the destination workspace, then apply them to each migrated task. Asana's Topics feature provides cross-project classification beyond flat tags, but since Breeze has no hierarchical taxonomy, we map tags 1:1 to Asana tags and flag Topics as a post-migration organizational option.

Breeze Time Tracking entries contain billable hours, duration, date, and optional description. Asana's native time tracking is available on Premium and above plans and stores time logs against tasks. We migrate time entries as a series of time logs against the corresponding Asana task with the original duration, date, and description preserved. If the destination Asana workspace is on the Free or Standard plan without time tracking enabled, we write billable hours and duration as a number Custom Field plus a text Custom Field for description against the task, and flag the Premium time tracking upgrade as an option.

Breeze Users are referenced by email, name, and role. We export the full user roster and map each task assignee by email against the destination Asana workspace members list. If the destination workspace does not yet have all Breeze users provisioned as members, we hold those tasks in a reconciliation queue pending user provisioning. SSO or domain-based user provisioning is outside migration scope and requires admin action before those users can be assigned in Asana.

Breeze uses customizable task statuses per project. Asana does not have a native per-project status enum equivalent to Breeze's model. We offer two migration strategies: map Breeze statuses to Asana Sections in List view (Section per Breeze status value, tasks grouped accordingly), or create a single-select Custom Field named Status with the Breeze status values as options and apply it to tasks. The customer chooses the strategy during scoping. We do not recommend mapping Breeze statuses directly to Asana's task completion checkbox since that loses the intermediate status values.

Breeze attachments are stored in Breeze's file system and referenced by URL in the API. We export attachment metadata (filename, URL, size, upload date) but not the binary file content. We write the attachment URL as a link on the Asana task. Actual files must be downloaded separately from Breeze's storage and re-uploaded to Asana or a linked cloud storage provider (Google Drive, Dropbox). For migrations with hundreds of attachments, we coordinate a file export session in parallel with the API export to minimize the overall migration window.

Breeze's public REST API does not expose task-level comments. We cannot programmatically include comment history in a migration export. This is a platform-level limitation of Breeze's API, not a mapping gap. We flag this gap during scoping and advise customers to use Breeze's in-app CSV export or take screenshots of comment threads before the migration window opens. Comment recovery is a manual step that sits outside the automated migration scope.

Breeze includes budget and estimate fields at the project level. Asana does not have native budget fields. We create number and currency Custom Fields on the project record (using Asana's custom fields on projects feature) and map the budget and estimate values. If the customer requires budget tracking against individual tasks, we discuss creating a project-level budget Custom Field and task-level allocation tracking as a separate configuration post-migration.

Breeze Workflows are property-triggered automations with conditions and actions. Asana's Workflow Builder and Rules use a different trigger and action model. We do not migrate automations as code. We deliver a written inventory of every active Breeze Workflow with its trigger, conditions, actions, and a recommended Asana Workflow Builder equivalent. The customer's admin rebuilds them post-migration.