Migrate from Flow to Asana

Flow Projects map directly to Asana Projects. We preserve the project name, description, and creation timestamp. Any project-level custom properties from Flow become custom fields on each child Task rather than project-level fields in Asana, since Asana does not support custom fields at the project level by default. Project membership (members with access) maps to Asana project team members by email match.

Flow Lists within a Project map to Asana Sections. Sections preserve the grouping order and can be expanded or collapsed in Asana's list view, matching Flow's organizational behavior. If a Flow List contains a custom ordering of Tasks, we preserve that sequence as the Section's task order. Multi-level List nesting in Flow flattens to a single Section level in Asana with task grouping maintained.

Flow Tasks are the primary work unit and map 1:1 to Asana Tasks. We preserve title, description (rich text), due date, start date if present, assignee, priority, and completion status. Task IDs are assigned by Asana during import and cross-referenced in the migration manifest for reconciliation. Completed Tasks retain their completion timestamp from Flow.

Flow subtasks nested under parent Tasks map to Asana's native subtasking model. We preserve the parent-child relationship via the subtask field on the parent Task. If Flow has multi-level subtask nesting (sub-subtasks), we replicate the hierarchy by nesting subtasks within subtasks up to Asana's display limit. Each subtask carries its own title, assignee, due date, and completion status.

Flow Tags on Tasks map to Asana Labels. We preserve the tag name and create a matching Label in Asana, assigning it to the migrated Task. Label color metadata from Asana is assigned by us using a default palette; the customer can recolor in bulk post-migration. Tags that appear across many Tasks are batch-assigned in a single import pass rather than per-record to avoid redundant API calls.

Flow Members are matched to Asana Users by email address during import. We extract every distinct member email from Flow Tasks and cross-reference against the Asana destination workspace's user list. Members without a matching Asana User are held in a reconciliation queue for the customer's admin to provision before task import resumes. Active/inactive status maps from Flow member state to Asana user membership.

Flow custom fields on Tasks export as key-value pairs. We infer the field type from the value (text, number, date, or dropdown) and create the corresponding Asana Custom Field before migration. Dropdown-style Flow custom fields map to Asana enum (single-select) or multi-enum (multi-select) based on whether the field accepts one or multiple values. Custom field values are set on each Task at import time. Custom fields that existed across many Tasks are batch-assigned.

Due dates on Flow Tasks map directly to the due_date field on Asana Tasks. Time zone context is preserved from Flow's display setting. If Flow due dates include a time component, we map it to Asana's due_at field; if date-only, we use due_date. Completed Tasks retain the original due date for historical accuracy. Tasks without due dates are imported without a due date field.

Flow comments attach to Tasks. We preserve comment body text, author name, and timestamp. Note that Flow may truncate comment timestamps to a date rather than an exact datetime; we preserve whatever Flow returns and flag this limitation in the post-migration report. Comments are imported after their parent Task is created so the Task GID is available for the comment attachment. Author attribution relies on email matching to Asana Users.

Flow time entries (if present in the workspace) map to Asana Time Tracking if the destination workspace has this feature enabled (Advanced and Enterprise tiers), or to a custom number field tracking hours if the customer is on a lower tier. We preserve the time entry value, the associated Task reference, and the original date. The customer decides on the tracking strategy during scoping.

Flow attachments cannot be exported via API because no API exists. We identify every Task with an attachment and produce a detailed checklist itemizing each file (filename, URL if visible, parent Task name) for the customer's team to download manually via browser. Upon completion of manual downloads, the customer delivers the file set to us, and we upload each file to the corresponding Asana Task. This manual dependency is the primary timeline risk item in Flow migrations.

Flow saved Views are UI-level filter and sort states with no persistent data behind them. We document the View names, their filter criteria, and sort order as a reference sheet for the customer's admin to recreate in Asana using Asana's saved views and custom filters. This is a manual rebuild item, not a data migration, and is included in the post-migration handoff documentation.