Migrate from Teamwork.com to Trello

Teamwork Projects map 1:1 to Trello Boards. We extract the project name, status (active/completed/on-hold), start and end dates, and project description as the board description. Archived projects in Teamwork map to archived Trello boards if the destination workspace supports board archival. Projects with a large task count (over 500 tasks) may warrant pre-migration scoping to confirm the board structure fits the team's workflow in Trello. The Trello free tier caps workspaces at 10 boards, which is a hard constraint we verify during scoping; customers with more than 10 active projects must upgrade to Standard ($5/user/mo) or above before migration begins.

Teamwork Task Lists are section headers within a Project that group related Tasks. We map them 1:1 to Trello Lists within the destination Board. List ordering is preserved by the sequence value returned by the Teamwork API. Note that switching from Teamwork's list view to a board view does not automatically surface pre-existing tasks in the new lists — we explicitly extract all tasks from each Task List and insert them as cards into the corresponding List during migration, replicating the correct card placement rather than requiring manual drag-and-drop after cutover.

Teamwork Tasks are the core work unit and map to Trello Cards. We preserve the task name as the card title, the description as the card description, the due date as the card due date, priority as a color-coded Label, assignee as the card member, and tags as Labels. Task status (open, completed) maps to the card's List position or a completion Checklist item depending on the customer's preferred Trello convention. Subtask relationships are handled separately (see Subtask mapping). Task-level milestones from Teamwork are resolved during extraction and set as card due dates before cards are written to the destination Board.

Teamwork Subtasks exist as nested records under Tasks, each with its own assignee, due date, and status. We flatten Subtasks into a Trello Checklist on the parent Card using the checklist format (title plus completion checkbox). We preserve subtask assignee by adding a note within the checklist item in the format '@[name]: [item]' so that accountability is visible on the card. If a subtask has a sub-subtask (deeper nesting), we flatten it one additional level or flag it for manual decomposition. Checklist item ordering is preserved by the sort order returned by the Teamwork API.

Teamwork Milestones are date-driven project markers that may or may not be linked to specific tasks. Trello has no native milestone object. We resolve milestones in two ways based on scoping: if a milestone is linked to one or more tasks, we set the corresponding card's due date to the milestone date and apply a 'milestone' label; if a milestone has no linked tasks, we create a standalone milestone card in a dedicated 'Milestones' board or list that the customer reviews manually. Milestone name and date are always preserved regardless of the mapping strategy. Customers who need structured milestone tracking post-migration should evaluate the Trello Timeline Power-Up (included in Premium) which supports milestone rows alongside Gantt-style views.

Teamwork Time Entries are first-class records linked to tasks or projects with billable/non-billable flags, hourly rates, and logged durations. Trello has no native time tracking object. We export all time entries as a structured CSV (task name, project, user, date, duration, billable flag, hourly rate, total amount) during migration. Customers who need to preserve time data in Trello configure a Trello Power-Up such as Planyo, Track茸, or a native time-tracking integration post-migration; we document the CSV schema and field mappings to support that configuration. Time entries linked to billing or invoicing in Teamwork Grow or Scale tier have no Trello equivalent and are flagged for the customer's finance team to handle separately.

Teamwork Custom Fields exist as project-level or site-wide types (text, number, date, dropdown, checkbox) and are gated behind the Premium-equivalent Grow plan ($25.99/user/mo). Trello Custom Fields are available from the Standard plan ($5/user/mo) and apply at the board level. We verify the destination Trello plan during scoping. If the destination has Standard or above, we map Teamwork custom field definitions to Trello Custom Field definitions using equivalent types (Teamwork text → Trello text, Teamwork date → Trello date, Teamwork dropdown → Trello dropdown with options array preserved). If the destination is on Trello Free, custom fields are not available and we flag each field for manual recreation after the customer upgrades.

Teamwork Comments attach to Tasks and carry author attribution, timestamp, and formatted text including @mentions. We map them 1:1 to Trello Card comments. Comment threads are preserved in sequence order by timestamp. @mentions are transferred as plain text within the comment body and do not trigger Trello member notifications (the @mention syntax does not cross-migrate). Image embeds within comments migrate as card attachments.

Teamwork Attachments link to Tasks, Projects, or Posts and carry file metadata (name, type, size, uploader, upload date). We extract file URLs from the Teamwork API and re-attach them to the corresponding Trello Card. Files larger than Trello's attachment limit (10MB on free, 250MB on Standard and Premium) are flagged for the customer to host externally and link via URL attachment rather than direct upload. The Trello free tier also caps total board storage, which we verify during scoping against the customer's total attachment volume.

Teamwork Tags are string labels applied across Projects and Tasks for cross-cutting categorization. We map them 1:1 to Trello Labels. Tag colors in Teamwork (if customized) map to Trello label colors by closest match; default tags map to unlabeled labels in Trello. Tags used for priority classification that overlap with Teamwork's built-in priority field are consolidated to avoid duplicate classification after migration.

Teamwork Clients are top-level entities that own multiple Projects and carry contact info, billing rates, and client portal accounts. Trello has no native Client object. We map Client records to Trello Workspace members with specific board access, or we create a dedicated 'Clients' board where each client gets a list of project boards they can access. Client billing rates and payment terms from Teamwork Grow or Scale have no Trello equivalent and are exported as a separate CSV for the customer's finance team. Client portal access does not migrate; we document the client email list for manual re-invitation post-migration.

Teamwork Users have profiles with name, email, role, hourly cost rate, and working hours. We map Users to Trello Workspace members by email match. Any Teamwork User without a matching Trello account is held in a reconciliation queue for the customer's admin to provision before card import. User cost rates from Teamwork (used for billing and profitability reporting) do not have a Trello equivalent and are exported in the time-entry CSV if billing reconstruction is needed.