Migrate from ftrack to Microsoft Project

ftrack Projects map directly to Microsoft Project .mpp files or Project for the web/Planner projects. Each ftrack Project becomes a single .mpp file or one Project Online project. Project-level custom attributes migrate to Project-level custom fields. We preserve the Project start date as the baseline and project status from ftrack's project-level metadata.

ftrack Sequences sit between Project and Shots in the hierarchy. When migrating, each Sequence becomes a Microsoft Project Summary Task grouped under the parent Project. Shots nested within the Sequence become child Tasks of the Summary Task. This preserves the creative production grouping without forcing the customer to rebuild Sequence-level task groupings manually.

ftrack Shots map to Microsoft Project Tasks at the same hierarchy level as Sequences' child level. Each Shot's name, status, and due date migrate to the Task name, percent complete, and finish date. Shot-level custom attributes migrate to task custom fields. Shot thumbnail references are not stored in Microsoft Project; we document the expected thumbnail path in the written inventory for the customer's reference.

ftrack Tasks map to Microsoft Project Tasks with full parent-child hierarchy preserved. Task status, assignee, due date, notes, and custom attributes migrate. If a Task has no parent Shot (orphan task at project level), it becomes a top-level Task under the Project. Task notes migrate as Task Notes text field; ftrack note attachment misplacements are resolved during the pre-import audit.

ftrack Users assigned to Tasks as assignees map to Microsoft Project Resources. We extract the distinct assignee list from ftrack Tasks, match by email against the destination Resource list, and create Resource records with name, initials, and type (Material or Work). ftrack role names (e.g., 'Lead', 'Artist') migrate as Resource Notes for the customer's team to assign to Resource Groups.

ftrack Notes on any entity (Project, Shot, Task) migrate to the Microsoft Project Task Notes field of the matching parent. A known ftrack webplayer behavior causes notes to attach to the wrong task level (topmost parent instead of intended child); we detect these mismatches during pre-import scope by comparing note context_id against the task hierarchy and re-associate them with the correct parent before writing. Notes that cannot be resolved are flagged in the written inventory.

ftrack custom attributes (typed key-value pairs on any entity) map to Microsoft Project task custom fields using the closest equivalent type: text attributes map to Text fields, numeric to Number, date to Date, and dropdown options to dropdown custom fields. Hierarchical custom attributes that return raw values in the ftrack API (rather than inherited evaluated values) are flagged during scoping; we query the parent entity for the effective value and write that. Expression attributes are flagged as needing recalculation post-migration because the ftrack API returns only the unevaluated formula string.

ftrack Task Statuses (configurable per project) map to Microsoft Project percent complete or a custom Flag field depending on status semantics. Status names with no exact Microsoft Project equivalent are flagged in the written scope for the customer to map manually before migration. The status schema variation between ftrack workspaces is handled per-project during scoping.

ftrack Assets (published files or asset builds) have no Microsoft Project equivalent. Asset names, types, and metadata are exported as a written inventory document with expected file paths. The asset inventory lists which Assets belong to which Shot or Task so the customer's team can re-link attachments manually after migration. Asset version history is not migrated; the latest version reference is included in the inventory.

ftrack Asset Versions have no Microsoft Project equivalent. Version numbers, file paths, and component metadata are included in the Asset inventory document with a reference to the parent Asset and Shot context. The customer manually re-attaches files or links to SharePoint after migration. Review session annotations linked to specific Asset Versions are documented separately in the written inventory.

ftrack review sessions with frame annotations and approval status have no Microsoft Project equivalent. Review session metadata (session name, date, participants, annotations list, approval decision) is exported as a written inventory document organized by Asset Version. Media files are not moved; the inventory references the expected media location for the customer's review team. We do not migrate review data as records.

ftrack Locations define storage configuration for studio infrastructure (cloud and on-premises paths, Python plugin logic for file transfer). These are studio-specific and have no Microsoft Project equivalent. We export Location names, path templates, and storage type as metadata in the written inventory. The customer's infrastructure team uses this to reconfigure any downstream storage integrations after migration.