Migrate from Favro to Trello

Favro Cards map directly to Trello Cards with title, description (markdown preserved), assignee, due date, start date (Favro Enterprise), and checklist items carried over. A critical resolution is required for Favro's cross-board Card existence: a Card can live on multiple Boards simultaneously, which has no native Trello equivalent. We handle this by applying a label to each Card for every Board on which it originally appeared, preserving the cross-team context as a searchable label attribute rather than a native multi-board relationship. Card ID from Favro is stored in a custom field for reconciliation.

Favro Boards map to Trello Boards with their configured column (list) structure intact. Board name, description, visibility settings, and Card ordering migrate. Board-level permissions in Favro map to Trello's Board permission levels (private, workspace, public). If the Favro Board uses a sheet or timeline view, we recreate that perspective as a Trello Board view if the destination Trello plan supports it, otherwise the default Kanban view is used.

Favro Collections aggregate multiple Boards for team or management visibility. Trello has no direct Collection equivalent; we map Collections to Trello Workspaces (available on Standard and Premium) or, for plan-constrained migrations, to a naming convention (prefixed Board names) that lets teams filter by Collection group. We capture the Collection-to-Board membership as a JSON reference file and apply it to the destination during migration so the grouping is recoverable even if the Workspace strategy differs.

Favro Relations link Cards and Boards across teams to model dependencies or cross-functional ownership. Trello has no native cross-Card relation model. We resolve Relations by either enabling a Card Link Power-Up in Trello (recommended for dependency tracking) or by applying paired labels to both Cards so that teams can filter by relationship type. The customer selects the strategy during scoping. We preserve the Relation type name (blocks, relates-to, parent, child) as part of the label or link metadata.

Favro Labels applied to Cards migrate as Trello Labels. We preserve label names and hex color values and deduplicate any label collisions during import. Labels created from cross-board Card resolution (see Card mapping above) are prefixed with a reserved namespace (e.g., FAVRO_BOARD_) to distinguish them from manually created labels. Label count limits in Trello (unlimited on Standard and Premium) mean no label collapsing is required.

Favro custom fields on Cards (dropdown, date, number, text, checkbox types) map to Trello Custom Fields via the Custom Fields Power-Up. We pre-create the Custom Field definitions in the destination Trello workspace before Card migration begins, using matching field names and types. Dropdown options from Favro migrate as Custom Field options in Trello. Note: the Custom Fields Power-Up must be installed and enabled on each destination Board before migration; we include this as a pre-migration step in the approach.

Favro Comments on Cards migrate as Trello Card Comments, preserving author attribution, timestamp, and content. Threaded replies in Favro flatten to a single comment chain in Trello. We preserve the reply hierarchy in a JSON reference file attached to the Card record so the structure is recoverable if the team later uses a commenting Power-Up that supports threading.

Favro file attachments on Cards migrate to Trello Card Attachments. Favro-stored file URLs transfer as direct link attachments. Favro attachments referencing external URLs migrate as link attachments in Trello. We do not re-upload files to Trello's storage; we preserve the attachment URL reference so that the link remains active. If Favro attachments are stored internally and the URL becomes inaccessible after account closure, those files cannot be migrated.

Favro guest accounts with restricted Board and Collection visibility have no direct Trello equivalent. Trello Standard and Premium allow Board members with observer or normal permission levels but no separate guest tier. We flag every Favro external member record during scoping and recommend either promoting them to full Trello workspace members or restricting their Trello Board access to specific Boards. The customer decides on the access model during scoping, and we apply it during migration.

Favro Automations (trigger-based rules with conditions and actions) are not accessible via API in a form that allows replay in Trello. We document every active Favro automation during migration scoping, capturing trigger type, conditions, action types, and board scope. We deliver an Automation Inventory document that maps each Favro automation to an equivalent Butler command syntax or a Butler board Power-Up configuration. The customer's team rebuilds these in Butler post-migration; we do not write Butler commands as part of standard migration scope.

Favro Dashboards aggregate Board and Card metrics into configurable widgets available on Standard and Enterprise. Trello has no native dashboard or portfolio-level reporting. We migrate dashboard widget configurations as a structured reference document (JSON export) so the customer understands what metrics were tracked. For simple metric views, we recommend Trello's native Board views (Calendar, Timeline, Dashboard on Premium) as partial replacements. Full dashboard rebuilds require a third-party reporting Power-Up (Screenful, Pl字gl, or similar) which is outside migration scope.

Favro timesheet entries (hours logged, date, user attribution against Cards) are available only on the Enterprise plan. Trello has no native time-tracking capability. We flag timesheet data during scoping and offer two options: migrate the timesheet data as a Card attachment (CSV export attached to the relevant Card) or exclude it from migration entirely. No native time-tracking rebuild in Trello is available without a third-party Power-Up.