Migrate from Flowzone to Trello

Flowzone Jobs are the central record and map directly to Trello Cards. We extract Job title, description, status, assigned users, creation date, and last-modified date, then create a Trello Card in each target List with those fields populated. Flowzone's List structure is preserved by creating a Trello Board and populating its Lists (columns) with the migrated Cards in the same order.

Flowzone Lists are container views that group related Jobs. We evaluate the List hierarchy and decide whether to map each List to a Trello Board (for top-level containers) or a List within a Board (for sub-groupings). If Flowzone has nested List groups, we create multiple Trello Boards and link them with Card mirroring (available on Standard and above) to preserve cross-project visibility.

Flowzone Columns are the custom data fields on a Job (text, numeric, date, dropdown, etc.). We map standard column types to Trello Custom Field types: text columns become Free Text Fields, numeric columns become Number Fields, date columns become Date Fields, and dropdown columns become Dropdown Fields with the same option values. The Custom Fields Power-Up is available on Trello Standard and above; Free-tier migrations map Flowzone column values to Card description appends or Labels instead.

Flowzone Forms capture structured input and route submissions to Jobs. We export the form schema and any submitted form responses linked to Jobs, then map each form field to a Trello Custom Field on the Card. Form-to-field routing logic in Flowzone does not migrate; we document the routing rules in the handoff inventory so the admin can apply Trello Automation rules or Butler commands to replicate the logic.

Flowzone documents attached to Jobs are exported with their filename, binary content, approval status, and annotation thread summary. We restore each document as a Card Attachment on the target Trello Card. Approval status is noted in the Card description or a Custom Field (Approved/Pending/Rejected) since Trello has no native approval workflow; annotation threads are noted in the handoff inventory as a manual reference because they cannot be ported as a linked discussion thread.

Flowzone Activities (available on Pro plan) are time-planned events linked to Jobs with date, assignee, and description. We export the activity date, assignee, and description and map to Trello Card due dates (for single-day items) or as Checklist items (for multi-step activity checklists). Trello Premium Calendar view provides a timeline visualisation for migrated activities.

Flowzone time recording entries capture hours logged against Jobs on the Pro plan. We export the hours amount, date, and assignee and map to Trello Card Custom Fields of type Number (hours logged) and type Date (log date). Budget comparison data (budget-to-actual) does not have a Trello native equivalent; we flag these for rebuild in a connected spreadsheet or the Card Metrics Power-Up. Time record data that spans multiple Jobs requires cross-referencing during scoping.

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 deliver a written workflow inventory that maps each Flowzone workflow step to a recommended Trello Butler trigger-action rule or a sequence of Labels and Custom Field states. The workflow logic (branching conditions, loops, jump targets) is documented per workflow so the admin can rebuild it as a set of Butler rules or a dedicated Power-Up such as Placker or WeGantt that supports step-state tracking.

Flowzone user accounts include group-based permission sets. We export the user list, their group membership, and permission levels and map to Trello Workspace Members with Board-level permissions. Flowzone roles (Admin, Member, Guest) map to Trello Workspace Admin, Member, or Guest. External client portal sharing from Flowzone maps to Trello Guest boards. The admin configures Workspace settings and board invitations post-migration.

Flowzone custom dashboard panels (bar charts, pie charts, custom dashboard layouts) are UI-level visualisation definitions tied to the Flowzone platform. We do not migrate them. The underlying data (Jobs, time records, deal values) is migrated through the object mappings above, and the admin rebuilds the dashboard in Trello Premium Dashboard view or a connected BI tool. We flag this explicitly during scoping so the customer does not expect chart definitions to carry over.

Each Flowzone Job carries a current workflow step state. We map this to Trello Card Labels (with a consistent colour scheme per step) or a Custom Field of type Dropdown named 'Workflow Step' with the step names as options. The mapping is documented in the workflow inventory so the admin can configure Trello Automations to trigger on Label or Custom Field changes to progress cards through a workflow sequence.

Flowzone Job assignments map to Trello Card assignees. We resolve each Flowzone user (by email or user ID) against the target Trello Workspace member list and assign the Card to the matching member. Unresolved assignments are held in a reconciliation list for the admin to provision before the final import pass.