Migrate from .STUDIO to Trello

Each .STUDIO Project maps to a Trello Board. We use the project name as the Board title and preserve the project status (active, on-hold, completed) as a Board label or checklist item depending on the destination workspace configuration. Projects with no tasks still become empty Boards with a note in the migration manifest. If multiple .STUDIO workspaces are migrating to a single Trello organization, we namespace Board names with a workspace prefix agreed during scoping.

.STUDIO task lists within a project map to Trello Lists. The list name preserves, and we maintain the list order sequence from .STUDIO. If .STUDIO uses nested task lists, we flatten to a single list level and optionally use Card checklists to represent sub-items, noting this in the scoping manifest.

Individual .STUDIO tasks map to Trello Cards. The task name becomes the Card title, description maps to Card description (with markdown formatting preserved where possible), due date maps to Card due date, assignee maps to Card member, and estimated hours become a checklist item or Card label. Task status (complete/incomplete) maps to Card archival for completed tasks.

.STUDIO Clients have no native Trello equivalent. During scoping, the customer chooses one of three strategies: (1) add a Client label to all Cards within that client's project Board; (2) prefix Board names with the client name; (3) store client contact info in a Board description or a linked Card at the top of the Board. We apply the chosen strategy consistently across all Boards from that point in migration.

Trello has no native time entry object. We offer two options: (1) append time entry data as structured text in the Card description with date, duration, user, and billable flag; (2) create a Time Tracking Power-Up-enabled migration where time entries become checklist items with duration metadata. Option 2 requires the customer to have a Trello Power-Up installed before migration; we flag this dependency during scoping. .STUDIO rounds to 6-minute increments (0.1 hour) by default; we expose this rounding setting and allow the customer to choose whether to preserve source rounding or strip it.

.STUDIO typed custom fields (date, number, dropdown, text) map to Trello Custom Fields via the Custom Fields Power-Up, which is available on Standard and above. Formula fields referencing other custom fields have no Trello equivalent; we fall back to plain-text storage of the last computed value and note this in the migration manifest. Multi-reference custom fields (linking to other .STUDIO records) require manual resolution and are flagged as high-severity items during scoping.

.STUDIO users map to Trello Workspace members by email address. We extract all distinct users referenced on tasks, time entries, and project assignments. Any user without a matching Trello account is held in a reconciliation queue for the customer to provision before Card member assignment begins. Deactivated .STUDIO users map to Trello guests if the customer wants to preserve their historical assignment; otherwise they are dropped with a note.

.STUDIO tags on tasks and projects map to Trello Labels. Tags are stored as flat string labels in .STUDIO; we split comma-separated tags and upsert each as a Trello Label. If the destination Board has no matching Label color, we create a default grey Label and note it for the customer's admin to recolor post-migration.

.STUDIO file attachments export with filename, URL, size, and type metadata. We re-attach files at Trello via the Trello API by uploading to the Card and preserving the original filename. Large files (over 10 MB per Trello's attachment limit) are flagged and handled as follows: we upload to the customer's linked Google Drive or Dropbox if a Power-Up is configured, otherwise we note the file URL in the Card description as a manual link.

.STUDIO task comments migrate as Trello Card comments with author, timestamp, and body text preserved. We resolve the .STUDIO comment author to a Trello Workspace member by email; if no match exists, the comment author appears as the migration system user with a note that the original author was not found in the destination Workspace.

.STUDIO project templates export as template structure only, not populated task instances. We map the template schema to a Trello Board with empty Cards representing each template task. The customer's admin fills the Cards with actual data post-migration. We note which Boards are template-derived in the migration manifest.

The .STUDIO invoicing submodule is a separate data layer and is not part of the core PM export schema. We do not migrate invoice records. If the customer needs invoice history preserved, we recommend a separate invoice-specific export from .STUDIO and a manual or third-party import into a dedicated accounting tool.