Migrate from TeamWork Live to Trello

Each TeamWork Live Project maps to one Trello Board. We migrate the project name as the Board title, project description as the Board description, start and due dates as metadata flags, and project status (active/archived) as Board archival state. Project-level custom fields migrate to the Board description or a Custom Fields Power-Up note if the Trello destination is on Standard or Premium. TeamWork Live's per-project client access controls do not map directly to Trello Guest access; we flag this permission gap and recommend board-level Guest configuration post-migration.

Each TeamWork Live Task List within a Project maps to one Trello List within the corresponding Board. The list name migrates as the List title. Task ordering within each list is preserved by computing a sequence index from the TeamWork Live API response order; since ordering is not exposed as a discrete API field, we capture the iteration order at retrieval time and apply it as card position integers during Trello card creation. Lists are created before cards in the migration sequence to satisfy Trello's list-must-exist constraint.

Each TeamWork Live Task maps to one Trello Card. Standard fields migrate directly: task title becomes card name, task description becomes card description, task status maps to a Label color (or archived card state if the destination supports archival), priority maps to a priority Label, due date migrates to card due date, and estimated time is stored as a custom field or card description note. Assignee resolution uses email match against the Trello Workspace member list; unresolved assignees are flagged in the reconciliation report for admin provisioning before the migration phase.

TeamWork Live Milestones have no direct Trello equivalent. We encode Milestones as Cards with the milestone target date set as the card due date, a dedicated milestone Label (e.g., 'Milestone') applied, and the milestone name as the card name. Completed milestones receive an additional 'Completed' Label. Milestones without a linked task are created as standalone cards within the corresponding Board List. If the customer has milestone completion dates, those migrate as the card due date with the 'Completed' Label and the card moved to a Done list.

TeamWork Live internal users map to Trello Workspace Members by email match. Guest or client-level users in TeamWork Live do not map to standard Trello Workspace Members; they map to Trello Board-level Guests, which we configure per Board after migration. We flag any TeamWork Live user without an email (unusual but possible with imported or manually created records) and store them in the reconciliation queue with a placeholder email for admin resolution.

TeamWork Live time entries are linked to Tasks and contain hours logged, date, and optional notes. Trello has no native time tracking object. We migrate time entry data as structured text appended to the corresponding Card description in a 'Time Entries' section (format: date, hours, notes). For accounts with high-volume time tracking requirements, we recommend a separate time-tracking Power-Up post-migration; we deliver a CSV export of all time entries keyed by source task ID for the customer's admin to ingest into their chosen tool. The TeamWork Live API requires sequential retrieval for time entries (no bulk endpoint), so we apply chunking and retry logic for accounts with over 1,000 entries.

TeamWork Live comments attached to Tasks migrate to Trello Card comments. We preserve comment text, author (resolved by email match to Trello Workspace Member), and timestamp. Rich-text formatting in TeamWork Live comments may not round-trip cleanly; HTML-heavy comments are flagged in the migration report for manual review. Comments on Projects (not attached to a specific task) migrate to the Board description or a designated 'Project Notes' card at the customer's discretion during scoping.

Files attached to TeamWork Live Tasks or Projects are referenced by URL in the TeamWork Live API. We retrieve attachment metadata (filename, URL, upload date, uploader) and re-upload each file to the corresponding Trello Card as a Card Attachment via the Trello API. Files that were stored in TeamWork Live's internal storage are downloaded and re-uploaded; files stored externally (Google Drive, Dropbox) are re-linked as URL attachments if the original link remains accessible. Failed uploads are logged for manual retry.

TeamWork Live task-level custom fields (text, number, dropdown) migrate to Trello Custom Fields Power-Up on Standard and Premium plans. We detect at scan time whether the source account is on a Premium subscription (custom fields are gated behind Premium); if not, no custom field definitions or values exist in the API response and we flag this in the scoping report. Dropdown options in TeamWork Live must be recreated in Trello's Custom Fields Power-Up configuration before migration; we deliver the option list as a configuration reference during the pre-migration schema step.

Project-level custom fields in TeamWork Live migrate to the corresponding Trello Board. For Standard and Premium Trello accounts, project custom fields become Board Custom Fields if the destination supports board-level custom fields; otherwise they are encoded as structured notes in the Board description. The customer chooses the preferred encoding during scoping. If the source TeamWork Live account is not on Premium, no project custom fields exist to migrate.

TeamWork Live tags stored as string arrays on Tasks or Projects map to Trello Labels. We migrate tag names as Label names with a default color assignment; the customer can customize label colors in Trello post-migration. If a TeamWork Live tag name conflicts with a Trello reserved label name or exceeds the label name length limit, we rename it with a suffix (e.g., '_teamwork_tag') and log the rename in the migration report.

TeamWork Live Companies and Clients linked to Projects for access control or billing tracking do not have a direct Trello equivalent. We migrate the company name and primary contact to the Board description as structured text. If the customer relies on client-level permissions in TeamWork Live, we recommend configuring a Trello Board-level Guest for each client post-migration; we deliver a client-to-email mapping CSV during the handoff for the admin to provision Guest access.