Migrate from ftrack to monday Work Management

ftrack Projects map to monday.com Workspaces (top-level container) with one or more Boards inside. Each Project becomes its own monday.com Workspace, and the Project-level custom attributes (project code, client name, budget) become Workspace-level columns or custom fields on the primary Board. If the studio prefers a flat structure, Projects map to Boards within a single Workspace, with Group names matching the Project name for cross-project views.

ftrack Sequences are children of Projects and parents of Shots. In monday.com, each Sequence maps to a Group within a Board (or a dedicated Board if the studio prefers granular separation). Group naming preserves the Sequence name, and Sequence-level custom attributes become Group-level columns or metadata tags. The Sequence-to-Shot parent-child relationship is preserved as Item-to-Sub-item structure within the Group.

ftrack Shots map to monday.com Items within the appropriate Group. The Shot ID from ftrack (e.g., SH010) maps to the monday.com Item name or a dedicated Shot ID column. Shot status, thumbnail URL (if stored as a URL rather than a file), and custom attributes map to monday.com columns. The Shot-to-Task parent-child linkage becomes the Item-to-Sub-item hierarchy in monday.com. We note that monday.com does not have a dedicated Shot entity type; all creative units are Items.

ftrack Tasks are children of Shots and carry status, assignees, due dates, notes, and custom attributes. They map to monday.com Sub-items attached to the Shot Item. Task status values map to the Sub-item status column (using monday.com labels or a Status column). Assignees on the Task link to monday.com Board members. Due dates map to a date column. Notes attached to a Task become Sub-item comments. Task-level custom attributes become Sub-item columns.

ftrack Assets represent published files or asset builds linked to a Shot or Sequence context. They map to monday.com file attachments on the corresponding Item. The Asset name and description migrate as text fields on the Item. Asset metadata (file type, file size) is stored as custom columns if the studio requires it. We note that monday.com does not support a structured Asset tree with version history; all attachments are a flat list on the Item.

ftrack Asset Versions (sequential publishes with version numbers, file paths, and components) cannot migrate to monday.com because monday.com has no Asset Version or component data model. We export the Asset Version metadata (version number, publish date, published by user) as a JSON reference document linked to the parent Item, and flag the expected file storage path for the customer's admin to re-associate after migration. The media files themselves are not moved by FlitStack AI.

ftrack review sessions and frame annotations are review-specific data that have no equivalent in monday.com. We export the review session metadata (session ID, linked Asset Version, reviewer name, annotation count) as a written reference document. The customer reviews this document and re-creates review links or external review URLs (e.g., Frame.io, SyncSketch) manually. Monday.com does not support annotation markup on media files.

ftrack custom attributes on any entity type (Project, Sequence, Shot, Task) map to monday.com custom columns on the corresponding Board or Item. Attribute type mapping: text attributes map to Text Column, numeric attributes to Number Column, date attributes to Date Column, dropdown attributes to Dropdown Column, and checkbox attributes to Checkbox Column. We flag hierarchical and expression attributes as requiring evaluation from the parent entity (see gotchas) and document which values must be recalculated post-migration.

ftrack Users referenced as task assignees map to monday.com Board members. We match by email address. If a monday.com account does not yet exist for a given ftrack user, we create a placeholder member in monday.com and flag it for the customer's admin to provision or invite before the migration window. Owner records from ftrack (project lead, studio admin) map to monday.com Workspace admins.

ftrack Locations define studio-specific storage paths for assets, including cloud and on-premises paths with Python plugin logic. monday.com has no storage location concept. We export the Location configuration as a structured JSON reference document (storage path, cloud region, transfer rules) for the customer's infrastructure team to reconfigure in their new storage workflow. Location-specific path logic must be rebuilt outside monday.com.

ftrack Task Statuses are configurable per project with name, color, and order. We map each ftrack status value (e.g., Pending, In Progress, On Hold, Approved, Rejected) to a monday.com Status Column label. Color mapping follows the closest monday.com color equivalent. Any ftrack statuses with no clear monday.com counterpart are flagged during scoping for the customer to decide whether to consolidate or map to a tag column.

ftrack Notes attached to Projects, Sequences, Shots, or Tasks migrate to monday.com comments on the corresponding Item or Sub-item. We detect notes posted at the wrong hierarchical level in ftrack (a known webplayer issue) by comparing context_id against the task hierarchy and re-associate them with the correct parent before writing. Rich text formatting in ftrack notes is preserved as plain text in monday.com comments.