Project Management migration

Migrate from Shotgun to Trello

Field-level mapping, validation, and rollback between Shotgun and Trello. We move data and schema; workflows are rebuilt natively in Trello.

Shotgun logo

Shotgun

Source

Trello

Destination

Trello logo

Compatibility

77%

10 of 13

objects map 1:1 between Shotgun and Trello.

Complexity

BStandard

Timeline

4-6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Shotgun logo

Shotgun

What's pushing teams away

  • Undocumented API rate limits cause production-scoped migration scripts to fail silently or return 429 errors without warning.
  • Studios outgrow the per-seat pricing model as crew sizes grow, prompting evaluation of in-house or open-source alternatives.
  • Limited offline and mobile access frustrates production coordinators working from sets or locations without reliable connectivity.
  • Performance degrades noticeably on Projects containing tens of thousands of Task or Shot records, particularly in the web UI.
  • Authentication is tied to individual user accounts with no API-key or service-account model, making automated migrations brittle.

Choosing

Trello logo

Trello

What's pulling them in

  • Free plan supports unlimited users and 10 boards, giving small teams full access to core Kanban functionality before any paid commitment is required.
  • The drag-and-drop board/card/Label interface requires no training, which reduces adoption friction and onboarding time across distributed teams.
  • Atlassian ecosystem integration with Jira, Confluence, and Bitbucket provides native cross-tool workflows for teams already using Atlassian tools.
  • Butler automation on paid tiers enables rule-based triggers without third-party integrations, covering basic workflow automation needs.
  • Simple visual task management with due dates, checklists, and member assignments keeps individual contributors and small teams organized without complexity.

Object mapping

How Shotgun objects map to Trello

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

maps to

Trello

Workspace or Board

1:1
Fully supported

Shotgun 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

maps to

Trello

List

1:1
Fully supported

Shotgun 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

maps to

Trello

Card

1:1
Fully supported

Shotgun 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

maps to

Trello

Card

1:1
Fully supported

Shotgun 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

maps to

Trello

Card Checklist or Card

1:many
Fully supported

Shotgun 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

maps to

Trello

Card or Attachment

1:1
Fully supported

Shotgun 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

maps to

Trello

Card Comment

1:1
Fully supported

Shotgun 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

maps to

Trello

Card Description or Custom Field Power-Up

lossy
Fully supported

Shotgun 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

maps to

Trello

Card Attachment

1:1
Fully supported

Shotgun 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

maps to

Trello

Card Cover Image

1:1
Fully supported

Shotgun 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

maps to

Trello

List or Label

lossy
Fully supported

Shotgun 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

maps to

Trello

Workspace Member

1:1
Fully supported

Shotgun 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

maps to

Trello

Trello Label

1:1
Fully supported

Shotgun 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.

Gotchas + challenges

What specifically takes care here

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 logo

Shotgun gotchas

High

Undocumented API rate limits cause migration failures

Medium

No bandwidth throttling on file attachment transfers

High

API authentication tied to individual user accounts

Trello logo

Trello gotchas

High

Billing model uses maximum seat quantity at term midpoint

Medium

Custom Field data historically stored in pluginData

Medium

API rate limits are token-gated and can block bulk migration

Medium

Guest-to-paid seat conversion triggers on multi-board membership

Low

Automation command runs are capped per plan and overage triggers upgrade pressure

Pair-specific challenges

  • Shotgun API authentication expires mid-migration

    Shotgun's Python API uses session-based authentication tied to a named user account. There is no API key or service account model. When the account used for migration is deactivated, renamed, or has its permissions changed, the migration session invalidates and the transfer halts. We require a dedicated, permanently active integration account at scoping, with credentials scoped to read all Projects, Shots, Assets, and Attachments required by the migration. We recommend creating a service account in Shotgun before migration kickoff that will not be deprovisioned.

  • Shotgun custom fields lack native Trello API support on Standard

    Trello's Custom Fields Power-Up is the only native mechanism for storing structured field data on Cards, but it is not accessible via Trello's REST API on Standard-tier workspaces. Only Premium and Enterprise workspaces can create and update Custom Fields via API. We work around this by injecting custom field values as structured text blocks in Card descriptions for Standard workspaces, which makes them human-readable but not queryable as structured data. We flag this limitation in the migration report and recommend upgrading to Premium if custom field queryability is required in Trello.

  • Attachment file sizes exceed Trello's limits for large media

    Shotgun stores render outputs, texture maps, and plate sequences that routinely exceed 1 GB per file. Trello's attachment limits are 10MB on Free, 250MB on Standard, and 50MB on Premium per file. We extract file sizes during the Shotgun inventory phase, flag every Attachment exceeding the destination workspace's limit, and document them in the migration report with a recommendation to use the Google Drive or Dropbox Power-Up to link rather than attach large files. We do not compress or transcode media during migration.

  • Shotgun Version chains have no Trello equivalent

    Shotgun's Version entity represents an iteration in the client review pipeline with supervisor approval states (wip, pending, mav, omv). Trello has no version history, revision tracking, or approval workflow for Card attachments. We reconstruct Version chains as linked Cards named with the Version code and store the approval state in the Card description, but the version comparison, per-frame annotation, and supervisor approval workflow do not migrate. We deliver a written inventory of every Version chain with its parent Shot, Version count, and annotation count for the customer to rebuild using a Trello Power-Up or an external review tool.

  • Large Projects risk memory exhaustion during Trello import

    Migration tools that load all source records into memory before writing to Trello fail silently when system RAM is exhausted, producing incomplete imports without error logs. Community posts from Vikunja's Trello migration documentation confirm that Projects with thousands of Cards and hundreds of Attachments exhaust memory on single-pass import attempts. We migrate Shotgun Projects sequentially, flushing each Project's Cards and Attachments to Trello before starting the next, which prevents memory accumulation. We also cap in-flight Card creation at 100 records per batch to respect Trello's write rate limits.

Migration approach

Six steps for a successful Shotgun to Trello data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Shotgun logo

Shotgun

Source

Strengths

  • Rich entity model purpose-built for animation, VFX, and game production pipelines.
  • Strong version and review workflow with per-shot annotation and comparison tools.
  • Customizable pipeline stages and entity schemas to match studio-specific terminology.
  • Integrations with Maya, Nuke, Houdini, and other DCC tools keep artist data canonical.
  • Per-project permission granularity controls visibility across large studio deployments.

Weaknesses

  • API rate limits are not publicly documented, causing migration scripts to fail without warning.
  • Authentication relies on individual user accounts rather than service tokens, breaking automated migrations when users leave.
  • Performance degrades on Projects with tens of thousands of Task or Shot records.
  • No bulk export or dedicated migration API endpoint means all data must be read record-by-record via find queries.
  • Custom field schemas vary between ShotGrid sites, requiring field-level mapping work for each migration.
Trello logo

Trello

Destination

Strengths

  • Generous free tier with unlimited users and 10 boards, the lowest barrier to entry among major project management tools.
  • Intuitive drag-and-drop Kanban interface requires no training or onboarding documentation.
  • Deep Atlassian integration with Jira, Confluence, and Bitbucket for teams already in the ecosystem.
  • Built-in Butler automation covers rule-based triggers without requiring third-party integrations.
  • REST API with comprehensive documentation enables programmatic access to all core objects.

Weaknesses

  • Reporting and analytics are absent, with no built-in velocity tracking, burndown charts, or historical performance metrics.
  • The flat board/list/card data model scales poorly for complex projects requiring hierarchical task structures.
  • Customization is limited compared to platforms like Asana, monday.com, or Jira that offer richer field types and workflow configuration.
  • Advanced views (Timeline, Dashboard) require Premium and are not available on Standard, inflating total cost for teams needing visibility features.
  • Guest user billing rules are confusing and prone to accidental seat overages when guests join multiple boards.

Complexity grading

How hard is this migration?

Standard Project Management migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Shotgun and Trello.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Shotgun: Not publicly documented. Community reports confirm quota enforcement at the authorization endpoint with no self-service visibility into current usage..

  • Data volume sensitivity

    B

    Shotgun doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Shotgun to Trello migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Shotgun to Trello data migrations

Answers to the questions buyers ask most during Shotgun to Trello migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Shotgun to Trello migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Migrations under 5 Projects, 1,500 Shots, and 10 GB of attachments complete in four to six weeks. Migrations with complex custom field schemas, large asset libraries exceeding 50 GB, or multiple Studios each with separate Workspaces move to eight to twelve weeks because of batch pacing, memory-managed attachment extraction, and the sandbox reconciliation phase. Shotgun's undocumented API rate limits add buffer time that we account for during the extraction phase.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Shotgun.
Land in Trello, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day