Migrate from Shotgun to monday Work Management

Shotgun Projects map to monday.com Workspaces as the top-level container, or to a monday.com Board if the studio prefers project-per-board over workspace-per-project. We preserve project-level metadata (status, description, pipeline configuration) as Board settings or as custom columns on a primary Status board. Studio-specific pipeline stage configurations are extracted during discovery and mapped to monday.com Status column values per board.

Shotgun Sequences (editorial acts or groupings of Shots) map to monday.com Groups within a Board. The sequence-to-shot relationship is preserved as the parent-child hierarchy: each Shotgun Sequence becomes a Group, and the Shots within that Sequence become Items within the Group. Sequence-level metadata (cut order, description) migrates as Group-level columns or as custom columns on a reference Item in the Group.

Shotgun Shots map to monday.com Items within the corresponding Sequence Group. Shot fields (cut order, status, assigned Tasks) migrate as monday.com columns: Shotgun pipeline status becomes a monday.com Status column, cut order becomes a Number or Order column, and assignee becomes a Person column. Shot-specific custom fields map to monday.com custom columns by type: text fields to Text columns, date fields to Date columns, list fields to Dropdown or Status columns.

Shotgun Assets (characters, props, environments) map to monday.com Items, typically organized in a dedicated Board or in a separate Group within the Project Board. Asset type (character, prop, environment) migrates as a Dropdown or Status column to preserve categorization. Asset-level thumbnails migrate as monday.com file attachments via the File Upload column type, noting that thumbnail resolution and aspect ratio may differ from Shotgun's native thumbnail display.

Shotgun Tasks assigned to Shots or Assets map to monday.com Subitems attached to the corresponding Item. Task pipeline stage and status migrate as the Subitem's Status column, and assignee migrates as the Subitem's Person column. Task-level custom fields (shot-specific notes, deliverables) map to Subitem custom columns. Subitems are only available on Pro and Enterprise monday.com plans; Standard-plan migrations map Tasks to Items in a separate Tasks Board with a Lookup column linking to the parent Shot or Asset.

Shotgun Version chains (iteration history for Shots and Assets) have no direct monday.com equivalent. We do not migrate Version chains as version-control records. Instead, we attach the most recent Version's published media as a monday.com File Upload on the Item. The version iteration history is preserved as a written inventory with the version number, creation date, author, and status, which the customer's admin can reference in a linked document or use to manually recreate the history if required.

Shotgun Notes attached to Shots, Assets, or Versions map to monday.com Updates on the corresponding Item. Note body migrates as the Update text, preserving rich text formatting where possible. Note threading (replies) migrates as nested Updates in chronological order. The Shotgun entity link (what the Note was attached to) resolves to the monday.com Item via the entity mapping established during scoping.

Shotgun custom fields per entity type map to monday.com custom columns scoped per Board. Shotgun field types translate as follows: text and paragraph to monday.com Text column; date to Date column; list (single-select) to Dropdown or Status column; multi-select list to Tags column; entity link (e.g., link to Artist) to Person column (if User) or Link column (if external); number to Number column. Shotgun custom field schemas vary between Shotgun sites, so we perform field-level mapping for each migration and flag any Shotgun field types with no monday.com column type equivalent.

Shotgun pipeline statuses are customizable per entity type and vary between studios. We extract the source site's full status workflow (stage names, colors, order) and map each stage to a monday.com Status column value on the relevant Board. Pipeline status assignments on individual Shots, Assets, and Tasks migrate as the corresponding Status column value. If the destination monday.com account uses a different Status color scheme, we document the original Shotgun color mapping for the customer's admin to reassign if color continuity matters for their pipeline review process.

Shotgun Attachments (uploaded files, render outputs, published media linked to Shots, Assets, or Versions) migrate as monday.com File Upload column attachments on the corresponding Item. We use Shotgun's download_attachment and get_attachment_download_url endpoints, chunk Attachment downloads into staged batches, and pace download throughput to avoid saturating studio WAN links. monday.com storage limits apply per plan (5 GB on Basic, higher on Standard and Pro); we flag any Items with attachments exceeding plan limits before migration so the customer can provision additional storage or trim the attachment scope.

Shotgun Thumbnails on Shots, Assets, Versions, and Tasks migrate as monday.com File Upload attachments on the corresponding Item. We extract thumbnails via upload_thumbnail or download_attachment from Shotgun's API and re-associate them in monday.com. Note that monday.com does not display thumbnails in the same shot-grid thumbnail view that Shotgun uses; thumbnails appear as file attachments that users click to view rather than as inline previews.

Shotgun Tags are freeform labels applied to any entity. We preserve tag assignments as a flat list and map them to monday.com Tags column values on the corresponding Item. Tags used for Shot classification, Asset type, or pipeline stage all migrate to the Tags column. If the customer requires tag-based filtering in monday.com, we configure a Tags column on the relevant Board during migration.

Shotgun Users (persons with roles and permissions) migrate to monday.com Team Members by email match. Shotgun role and permission sets do not map to monday.com workspace roles because the permission models are structurally different. We preserve the user's name and contact email; the customer's admin reassigns monday.com workspace permissions (Viewer, Editor, Admin) post-migration based on the user's intended role in monday.com.