Migrate from Flowzone to Asana

Flowzone Jobs are the central record and map 1:1 to Asana Tasks. We preserve the Job title, description, status (active/closed), assignee, due date, and creation timestamp. The source Job ID is stored in a custom text field flowzone_job_id__c for reconciliation. Jobs with sub-Jobs or linked Jobs map to subtasks or Tasks linked via Asana Dependencies respectively, depending on the relationship type in Flowzone.

Flowzone Lists are container views grouping Jobs and map directly to Asana Projects. We preserve the List name, description, and the Jobs assigned to each List. The organization hierarchy of nested Lists in Flowzone maps to Asana's Project hierarchy (parent and sub-projects). If Flowzone Lists have custom colour or icon metadata, we store this in a custom text field on the Asana Project.

Flowzone Columns are the custom data fields on a Job (text, numeric, date, dropdown, etc.). We map standard column types to their corresponding Asana Custom Field types: text columns to Text fields, numeric columns to Number fields, date columns to Date fields, and single-select columns to Enum fields. Multi-select columns in Flowzone map to Asana multi-enum Custom Fields. We validate the column name and type during the field-mapping phase before import, and create the Custom Field in Asana at the Project or Portfolio level before Task import begins.

Flowzone Forms capture structured input and submitted responses link to Jobs. We export the form schema and any submitted form responses. If the destination Asana org has Advanced ($24.99/user), the form schema maps to Asana Forms with intake routing to the corresponding Project. If Advanced is not in scope, form submissions restore as Tasks with the submitted field values mapped to Custom Fields and the form name stored in a custom field for reference. Form-to-field routing logic requires manual configuration in Asana Forms post-migration.

Flowzone documents attached to Jobs export with their filename, binary content, version number, and approval status. We restore them as Asana Attachments linked to the corresponding Task. The document approval status (approved, pending, rejected) is stored as a custom Enum field doc_approval_status__c on the Attachment or as a Task-level custom field. Note that Flowzone annotation threads are UI-stored data that may not export in a portable format; we flag any annotated documents during the export audit and restore the binary and approval status, with annotation detail noted as requiring manual reference.

Flowzone workflows are step-based with branching, looping, and step-jumping logic. We export the workflow definition and the current step of each Job, then document the workflow as a written inventory: workflow name, step sequence, branching conditions, and the current Job-step mapping. Asana does not have a direct equivalent to Flowzone's step-state model. We recommend rebuilding using Asana Tasks as workflow steps with Dependencies for sequencing, Milestones for stage gates, and Rules for trigger-based transitions. The inventory document is delivered at migration handoff so the admin can rebuild or engage an Asana partner.

Flowzone Activities (Pro plan) are time-planned events linked to Jobs with date, assignee, and description. These map to Asana Tasks with a due date and the activity description stored in the Task description field. If the destination Asana has the Calendar view enabled, the migrated Tasks appear in calendar view automatically. All-day events and multi-day activities map to Tasks with start and due dates preserved.

Flowzone time recording entries capture hours logged against Jobs (date, assignee, hours, and optional notes). We export the amount, date, and assignee. If the destination Asana org has Advanced ($24.99/user) with time tracking enabled, time records migrate to the native time tracking feature linked to Tasks. If Advanced is not in scope, hours are stored as a Number Custom Field (hours_logged__c) and a Date Custom Field (time_record_date__c) on the Task, with a note in the migration report recommending time-tracking tooling if billable-hour tracking is required.

Flowzone user accounts include group-based permissions. We export the user list, their email addresses, group membership, and permission levels (admin, member, external). In Asana, we map Flowzone groups to Teams, and Flowzone members to Asana Members. Flowzone external users map to Asana Guests with the appropriate project-level access. We resolve users by email match; any Flowzone user without a matching Asana account goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Flowzone custom dashboard panels (bar charts, pie charts, summary widgets) are UI-level visualisation definitions that do not carry underlying data separately from the records they summarise. The Job, List, and Column data migrates through the standard object mapping, but the panel layouts themselves do not transfer. We inform customers that dashboard configuration must be recreated in Asana's Dashboard feature post-migration and that the migrated data is available for rebuilding those visualisations. We do not create a custom dashboard definition in the migration scope.

Flowzone Jobs may carry a priority level (urgent, high, medium, low, or custom values). We map this to an Asana Custom Enum Field (priority__c) with the same value set. If Flowzone uses a numeric priority score, we map it to a Number Custom Field (priority_score__c). Priority-based sorting in Flowzone translates to sorting or filtering by the custom field in Asana's list view.

Flowzone may use tags or labels on Jobs for categorical tracking. We export the tag values and map them to Asana Tags on the corresponding Task. Tags migrate as text labels and appear in Asana's tag filtering and search. If the destination Asana org uses Topics instead of Tags, we map to TopicAssignment records.

Flowzone approval chains on Documents are multi-step approval processes with approver sequence. We export the approval status (pending, approved, rejected) and the current step number. Asana has no native multi-step approval chain model; Approval Tasks (Advanced tier) support single-level approvals. We restore approval status as a custom Enum field (doc_approval_status__c) and document the approval sequence as a written record so the admin can design an approval workflow using Asana's Advanced Forms or a third-party approval tool if multi-step sign-off is required.

Flowzone Jobs may carry comments from team members or external collaborators. We export the comment text, author, and timestamp and restore them as Asana Stories on the Task. The story body preserves the original comment text, and the author maps to the matching Asana user by email. External comments from Flowzone's client portal map to Stories with a note indicating the external author for admin awareness.