Project Management migration
Field-level mapping, validation, and rollback between Shotgun and Trello. We move data and schema; workflows are rebuilt natively in Trello.
Shotgun
Source
Trello
Destination
Compatibility
10 of 13
objects map 1:1 between Shotgun and Trello.
Complexity
BStandard
Timeline
4-6 weeks
Overview
Moving from Shotgun to Trello is a structural simplification, not a lateral move. Shotgun's entity model (Projects, Sequences, Shots, Assets, Tasks, Versions, Notes) is purpose-built for VFX and animation pipelines; Trello's entity model (Workspaces, Boards, Lists, Cards) is a general Kanban system. The migration collapses Shotgun's hierarchical pipeline schema into a flat card-and-list structure. We preserve what Trello can represent: Shot as a Card, Sequence as a List, Asset as a Card, Task assignment as a Card assignee, and pipeline status as a Trello label. What Trello cannot natively represent — Version chains, per-shot review annotations, custom field types beyond text and number, pipeline stage logic, and work schedules — we document in a written inventory for your team to rebuild using Trello Power-Ups and Butler automations. We do not migrate Shotgun Workflows, Rules, or pipeline automations as code.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Shotgun object lands in Trello, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Shotgun
Project
Trello
Workspace or Board
1:1Shotgun Projects map to Trello Workspaces if the studio has multiple unrelated Productions, or to a single Board if all Shots and Assets belong to one Production. We create the Workspace first, then create a Board per Shotgun Project, preserving the Project name, description, and start/end dates as Board metadata in the Board description field. Multiple Boards within one Workspace is the recommended structure for multi-Project studios migrating from Shotgun.
Shotgun
Sequence
Trello
List
1:1Shotgun Sequences map directly to Trello Lists. The editorial sequence name and cut order are preserved as the List name. Shotgun's sequence-level metadata (description, shotgun code) is appended to the List description. Lists are ordered within the Board to match the editorial cut sequence, which Trello supports via positional ordering.
Shotgun
Shot
Trello
Card
1:1Shotgun Shots map to Trello Cards. The Shot code (e.g., SQ010_SH010) becomes the Card name, with the Shot description and cut in/cut out values stored in the Card description. Shotgun's pipeline status maps to the Card's List position (the List representing the Sequence acts as the status column). Due dates migrate from the Shot's due date field if set. Assignees map from Shotgun Task assignees to Trello Card members.
Shotgun
Asset
Trello
Card
1:1Shotgun Assets (characters, props, environments) map to Trello Cards in a dedicated Board or List labeled Assets. The Asset name becomes the Card title. Asset status maps to the Card's List position. We flag any Asset with linked Versions or Notes as requiring a Trello Power-Up (Card Peek or Card Checklist) to approximate the Shotgun version chain.
Shotgun
Task
Trello
Card Checklist or Card
1:manyShotgun Tasks assigned to a Shot map to Trello Card Checklists. Each unique Task type (Lighting, Comp, Rigging, Layout) becomes a Checklist within the Card. Task status (wip, omit, rev, app) becomes the Checklist item state. Unassigned Tasks or Tasks with no parent Shot map to separate Cards in a dedicated Task Board. Task assignees are preserved as Checklist item assignees if the Trello workspace has Premium access.
Shotgun
Version
Trello
Card or Attachment
1:1Shotgun Versions are linked iterations in the review pipeline and have no native Trello equivalent. We create a linked Card for each Version chain using the Version code as the Card name and store the Version status (wip, pending, mav, omv) in the Card description. The most recent Version's thumbnail becomes the Card cover image. We flag Version chains as requiring manual reconstruction via Card linking or a Power-Up because Trello has no built-in revision history per card.
Shotgun
Note
Trello
Card Comment
1:1Shotgun Notes attached to Shots, Assets, or Versions migrate as Card Comments. The Note body migrates as plain text (Shotgun rich text annotations are simplified). Threaded replies are flattened into a sequential comment chain ordered by creation timestamp. Notes attached to entities that cannot be mapped directly (e.g., Versions) are attached to the parent Shot or Asset Card instead.
Shotgun
Custom Field
Trello
Card Description or Custom Field Power-Up
lossyShotgun custom fields require a two-tier migration strategy. Text and number custom fields map to Trello Custom Fields Power-Up if the destination workspace is on Premium or Enterprise, where they are accessible via API. Complex types (entity links, list_order, serializable) are injected as structured text into the Card description with a [SHOTGUN CUSTOM FIELD] header so they remain human-readable. We document every Shotgun custom field name, type, and value set during scoping so the customer can decide which to preserve and which to drop.
Shotgun
Attachment
Trello
Card Attachment
1:1Shotgun Attachment URLs are downloaded and re-uploaded to Trello Cards as attachments. We flag any file exceeding Trello's size limit (10MB Free, 250MB Standard, 50MB Premium) in the migration report and advise on a Trello Power-Up like Google Drive or Dropbox linking as a workaround for large media files. We chunk attachment downloads in batches to manage memory and studio WAN throughput, and we skip thumbnail-only attachments if the Trello workspace is on the Free plan to avoid attachment count bloat.
Shotgun
Thumbnail
Trello
Card Cover Image
1:1Shotgun entity Thumbnails (Shots, Assets, Versions) migrate to Trello Card cover images where the workspace plan supports cover images. Thumbnails are resized to Trello's recommended cover dimensions during migration. If the destination workspace is on Free or Standard, Thumbnails are stored as Card attachments instead. Version Thumbnails are given priority as cover images over Shot or Asset Thumbnails in the migration queue.
Shotgun
Pipeline Status
Trello
List or Label
lossyShotgun pipeline status values (e.g., wip, omt, rev, app, ppa) map to List positions within the Sequence Board. If the studio prefers a single List with status labels, we map pipeline status to Trello Labels with color coding. We document the full Shotgun pipeline workflow during scoping and deliver a written mapping table that the Trello admin uses to configure Lists or Labels, because Trello has no native pipeline automation.
Shotgun
User
Trello
Workspace Member
1:1Shotgun Users migrate as Trello Workspace members by email match. Shotgun role and permission sets do not map to Trello's workspace permission model and are documented in the written handoff inventory for the customer's admin to reassign. Deactivated Shotgun users are migrated as inactive Workspace members so that historical assignment data is preserved.
Shotgun
Tag/Label
Trello
Trello Label
1:1Shotgun Tags migrate to Trello Labels by name match. Shotgun tag colors (if configured via custom fields) map to Trello Label colors where supported. Free-form Shotgun tags that do not match any existing Trello Label are created as new Labels with a default color and flagged in the migration report.
| Shotgun | Trello | Compatibility | |
|---|---|---|---|
| Project | Workspace or Board1:1 | Fully supported | |
| Sequence | List1:1 | Fully supported | |
| Shot | Card1:1 | Fully supported | |
| Asset | Card1:1 | Fully supported | |
| Task | Card Checklist or Card1:many | Fully supported | |
| Version | Card or Attachment1:1 | Fully supported | |
| Note | Card Comment1:1 | Fully supported | |
| Custom Field | Card Description or Custom Field Power-Uplossy | Fully supported | |
| Attachment | Card Attachment1:1 | Fully supported | |
| Thumbnail | Card Cover Image1:1 | Fully supported | |
| Pipeline Status | List or Labellossy | Fully supported | |
| User | Workspace Member1:1 | Fully supported | |
| Tag/Label | Trello Label1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Shotgun gotchas
Undocumented API rate limits cause migration failures
No bandwidth throttling on file attachment transfers
API authentication tied to individual user accounts
Trello gotchas
Billing model uses maximum seat quantity at term midpoint
Custom Field data historically stored in pluginData
API rate limits are token-gated and can block bulk migration
Guest-to-paid seat conversion triggers on multi-board membership
Automation command runs are capped per plan and overage triggers upgrade pressure
Pair-specific challenges
Migration approach
Shotgun inventory and scoping
We run a read-only discovery script against Shotgun's Python API across all source Projects. We capture record counts per entity type (Projects, Sequences, Shots, Assets, Tasks, Versions, Notes), Attachment file sizes, custom field schemas with type and list values, pipeline status workflows, and the distinct set of Users referenced as owners and assignees. We create a dedicated integration account in Shotgun with read-all permissions before this phase begins. The inventory output is a written scope document with record counts, batch sizing estimates, and a custom field mapping table.
Trello workspace and Board schema design
We design the destination Trello workspace structure based on the Shotgun inventory. Each Shotgun Project becomes a Trello Board. Each Shotgun Sequence becomes a Trello List. Assets are placed in a dedicated Board or a labeled List within each Project Board depending on the customer's preference. We configure Labels to mirror Shotgun pipeline statuses if the customer chooses Label-based status over List-based status. We set up the Custom Fields Power-Up with the applicable custom field definitions for Premium and Enterprise workspaces; for Standard workspaces we design the Card description template that will carry custom field data.
Attachment extraction with size filtering
We extract Shotgun Attachments in staged batches using Shotgun's download_attachment endpoint. Files are named by Shotgun entity code and attachment ID. We compare each file size against the destination Trello workspace plan's attachment limit and flag oversized files in the migration report. We extract entity Thumbnails separately and store them in a local cache for cover image assignment during the Card creation phase. Attachment extraction is paced to respect Shotgun's undocumented rate limits using exponential backoff starting at a conservative request interval.
Sandbox migration and reconciliation
We run a full migration into a test Trello Workspace using a subset of the largest Project from the source Shotgun site. The customer's project coordinator reconciles record counts (Cards in, Lists in, Attachments in, Comments in), spot-checks 25-50 Cards against the Shotgun source for field accuracy, and reviews the custom field injection format in Card descriptions. The customer signs off the sandbox migration before production migration begins. Any custom field schema changes, Label color conventions, or Board structure changes happen in this phase.
Production migration in dependency order
We run production migration in staged batches: Workspaces and Boards first, then Lists per Board, then Cards per List. Card creation includes description injection with custom field data, cover image assignment from the Thumbnail cache, member assignment from the User mapping, and due date migration. Notes migrate as Card Comments after all Cards are created to ensure the parent Card exists. Attachments migrate in size-filtered batches, with oversized files documented for Power-Up linking. Version chains are reconstructed as linked Cards with the Version status in the Card description. Each phase emits a row-count reconciliation report.
Cutover, validation, and written handoff
We freeze writes in Shotgun during the cutover window. We run a delta migration of any records created or modified during the migration window. We deliver a Trello Workspace migration summary with record counts, a written inventory of what did not migrate (pipeline automation, Version review chains, complex custom fields on Standard workspaces, work schedules), and a Trello-specific rebuild guide for the customer's admin team. We support a one-week hypercare window for reconciliation issues. We do not rebuild Shotgun Workflows or automations in Trello Butler as part of the migration scope.
Platform deep dives
Shotgun
Source
Strengths
Weaknesses
Trello
Destination
Strengths
Weaknesses
Complexity grading
Standard Project Management migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Shotgun and Trello.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Shotgun: Not publicly documented. Community reports confirm quota enforcement at the authorization endpoint with no self-service visibility into current usage..
Data volume sensitivity
Shotgun doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Shotgun to Trello migration scoping. Not seeing yours? Book a call.
Walk through your Shotgun to Trello migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Shotgun
Other ways to arrive at Trello
Same-Project Management migrations
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.