Migrate from ftrack to Trello

Each ftrack Project becomes a Trello Workspace (or a top-level Board within a Workspace) to serve as the primary container. Project-level custom attributes migrate to Board-level Custom Fields if the customer's Trello plan supports them. The Project name becomes the Board name, and any project-level status settings are documented for manual configuration in Trello.

ftrack Sequences map to individual Trello Boards when the Project-to-Board mapping uses one Board per Sequence. When a single Board represents an entire Project, Sequences are documented as Lists within that Board. The mapping choice is made during scoping based on the customer's board structure preference.

ftrack Shots are children of Sequences and parents of Tasks, representing a key production deliverable. In Trello, Shots map to milestone Cards (named Cards with a distinct label such as 'Shot') to preserve the production vocabulary. Shot status (WIP, awaiting review, final) maps to Card labels that mirror the shot pipeline stage.

ftrack Tasks are the core work unit and map directly to Trello Cards. Task name becomes the Card title, Task description maps to Card description, due date maps to Card due date, and assignees map to Card members. Task status maps to the Card's position within the Trello List (To Do, In Progress, Review, Done) rather than a status label. We validate that the parent Shot is represented as a milestone Card in the destination before inserting child Task Cards.

ftrack Assets represent published files or asset builds linked to a Shot or Sequence context. Each Asset has multiple Asset Versions representing sequential publishes. Trello has no native Asset or version tracking model; we attach the most recent Asset Version's file as a Card attachment on the corresponding Shot Card. Historical version history is documented in a written record for manual reference. Asset context_id linkage is preserved as a Card label or description note.

Asset Versions represent sequential publishes of a ftrack Asset. Trello has no version tracking. We document the Asset Version chain in a written inventory linked to the parent Card, noting the version number, publish date, and file reference. Version comparison and lineage tracking are not available in Trello and must be handled manually or with a separate DAM tool.

ftrack Notes attached to Tasks migrate to Trello Card Comments. We handle the known ftrack webplayer issue where notes occasionally attach to the wrong task level by comparing the note's context_id against the task hierarchy during migration and re-associating misplaced notes with the correct parent Task Card. Note body and author transfer as plain text. Notes with @mention or action-item formatting are migrated as-is and may need manual reformatting in Trello.

ftrack custom attributes on any entity type (Project, Shot, Task) map to Trello Custom Fields if the customer's Trello plan supports them. Custom Field types in Trello are limited to checkbox, date, dropdown, number, and text. ftrack attributes with hierarchical inheritance (which the API returns as raw values rather than evaluated inherited values) are resolved by querying the parent entity for the effective value before migration. Expression attributes (calculated formulas) are flagged in the scope document because Trello cannot evaluate them; the customer recalculates these post-migration.

ftrack Users assigned to Tasks as assignees map to Trello Card members. We match assignees by email against the Trello destination workspace. Any ftrack User without a matching Trello account is placed in a reconciliation queue for the customer's admin to provision before the final migration phase. Active and inactive user status is preserved in a Card label for post-migration review.

ftrack Task Statuses are configurable per project and include name, color, and order. The status schema varies between ftrack workspaces. We map ftrack status values to Trello List names (e.g., 'wip' to 'In Progress', 'hrev' to 'Awaiting Review', 'final' to 'Approved'). Any ftrack status without an exact Trello List match is documented during scoping. Lists are created in the destination Board before Card migration begins.

ftrack Locations define storage configuration for assets and files, including cloud and on-premises path logic. Trello has no storage configuration capability. Locations are documented as unsupported in the migration scope, and the customer's infrastructure team assesses whether file paths can be managed externally or require a separate asset management tool post-migration.

ftrack Review sessions and frame annotations are linked to Asset Versions and represent the client and stakeholder approval workflow. Trello has no native review, annotation, or approval workflow system. Review sessions and annotation data are documented as unsupported. We flag the expected file path of reviewed media for manual handoff. If approval tracking is required, the customer needs a separate review tool or Trello Butler automation configured manually post-migration.