Migrate from Flow to Trello

Flow Projects map directly to Trello Boards. We extract each Project's name, description, and member list and create a corresponding Board in the destination Workspace. Project-level custom properties become Board description or are stored in a metadata Card pinned to the top of each Board. We use the Project member list to set Board membership during import.

Flow Tasks are the primary work unit and map 1:1 to Trello Cards. We preserve Task title, description (rich text), due date, assignee (mapped to a Trello Board member), and the source List name as the destination List. Tasks without an existing List in Flow become Cards in a default 'Backlog' List that we create on each Board.

Flow Lists group Tasks within a Project. We map each Flow List to a Trello List on the same Board in the same order. If a Flow List name exceeds Trello's 512-character List name limit, we truncate while preserving uniqueness. Lists with no Tasks are created as empty Lists for structural fidelity.

Flow Subtasks under a parent Task become Checklist items on the migrated Trello Card. The parent-child hierarchy is resolved at migration time by associating each Checklist item with its parent Card. Checklist item completion status (checked/unchecked) migrates directly. Trello supports up to 500 checklist items per Card, which accommodates the vast majority of Flow subtasking use cases.

Flow Assignees (Members assigned to Tasks) map to Trello Board Members. We extract the Member's name and email from Flow's workspace access and match by email against the destination Trello's Workspace member list. Members without a matching Trello account go to a reconciliation queue for the customer to provision before Card import. Card assignment migrates as a Trello Card member.

Flow Comments attached to a Task become Trello Card comments. We preserve comment body, author name, and the timestamp returned by Flow's UI. Flow's UI may truncate timestamps to a date rather than an exact datetime; we preserve whatever precision Flow returns and flag this in the post-migration report as a known precision limitation. Comments are imported after Cards to ensure the Card exists before the comment is posted.

Flow Custom Fields on Tasks map to Trello Custom Fields Power-Up if the destination Trello workspace is on Standard plan or above. We create the Custom Field in Trello (supporting Text, Number, Date, Dropdown, Checkbox, and Label types), then set the value on each migrated Card. If the destination is on the Free plan, Custom Fields are serialized as structured text appended to the Card description with a '[Custom Field: Name = Value]' format for manual reconstruction.

Flow Tags on Tasks map to Trello Labels on Cards. We preserve the tag name as the Label name and map Flow's color scheme to Trello's available label colors (blue, green, orange, purple, red, yellow, sky, lime, pink, black) or use a default gray if no Flow color is available. Multiple Flow Tags on a single Task create multiple Labels on the same Card.

Flow Due Dates on Tasks map directly to the Trello Card due date field. We preserve the original date value and time zone context. Cards without a due date in Flow are created without a due date in Trello. Cards with past due dates are flagged in the migration report for the customer's review.

Flow Saved Views represent saved filter and sort states in the UI. These are transient UI constructs with no persistent data backing that we can extract. We document the View names from Flow's workspace as a reference list for the customer to recreate manually in Trello using Trello's native Board filtering and, on Premium, using the Table view or Dashboard view.

Flow provides no bulk attachment export path. Each file attached to a Task must be downloaded individually via browser. We document the full list of Cards with attachments as a customer checklist and provide step-by-step instructions for downloading files. After the customer completes the download, we provide a mapping file linking each downloaded file to its Card for manual re-upload in Trello. This is a manual effort item, not a data-loss gap, because the files exist in Flow and can be recovered with customer action.

If Flow contains time entry records linked to Tasks, we append a formatted text block to the Card description in Trello with the entry date, duration, and notes. Trello has no native time tracking field; if the customer requires time tracking, we recommend adding a time-tracking Power-Up (TimeCamp, Planyo, or a custom integration) post-migration.