Migrate from Work as Team to Trello

Work as Team Projects map directly to Trello Boards. The Project name becomes the Board name, and Project description maps to the Board description. Each Project gets its own Board as the default migration pattern; for organizations with dozens of small projects, we can discuss grouping multiple Projects into a single Board by team or portfolio during scoping. We preserve the Project start date and target end date in a custom field on the Board if the Trello plan supports Custom Fields, or as a Board description note if not.

Work as Team Lists map directly to Trello Lists. The List name migrates verbatim. Status labels from Work as Team (To Do, In Progress, Review, Complete) map to the corresponding Trello List positions by ordinal order rather than by name. If the source has more Lists than the team wants to preserve in Trello, we consolidate during scoping by merging Lists that share the same workflow stage.

Work as Team Tasks map to Trello Cards. Task name becomes Card title. Task description migrates as Card description. Task assignees map to Card members. Task due date migrates as Card due date. Task priority (Low, Medium, High, Urgent) maps to Card labels with a color-coded label set that we define during scoping. Archived tasks in Work as Team migrate to archived cards in Trello if the Trello plan supports card archival.

Work as Team Sub-tasks migrate as Checklist items on the parent Trello Card. Each sub-task name becomes a checklist item with the original assignee and due date appended in parentheses if available. If the sub-task has its own sub-sub-tasks, we flatten them into additional checklist items with indentation notation. Sub-task completion status maps to the checklist item checked state. Work as Team sub-task dependencies have no Trello equivalent and are flagged in the deliverable inventory.

Work as Team Milestones do not have a direct Trello equivalent. We map each Milestone to a Trello Label (named with the Milestone name and a distinct color) and create milestone-tracking Cards with the Milestone date as a due date and the label applied. If the team prefers a separate Milestone Board, we can discuss that during scoping. Milestone task linkages (which tasks are part of which milestone) are preserved as a custom field or label on the linked cards.

Work as Team time entries have no native Trello equivalent. Time tracking requires a Power-Up in Trello, and there is no standard migration path for time data. During scoping we confirm whether the team wants to preserve time entry summaries (total hours per task) in card descriptions as a text note, move time tracking to a separate tool post-migration, or use a Trello time-tracking Power-Up. We flag the chosen approach and do not attempt to create native time records in Trello without a specified Power-Up.

Work as Team file attachments on tasks migrate as Trello Card attachments. We use the Trello API to attach files directly to cards. Attachments stored in Work as Team are downloaded and re-uploaded to Trello during migration. File size limits in Trello are 10MB per attachment on Free plans and up to 250MB on paid plans; we identify oversized attachments during scoping and flag them for the customer's admin to handle manually or via a cloud storage link in the card description.

Work as Team task comments migrate as Trello Card comments. Comment author and timestamp are preserved in the comment body as a header line. HTML-formatted comments are stripped to plain text with line breaks preserved. Mentions of team members in comments are not migrated as @mentions since Trello does not support cross-system mention resolution.

Work as Team task tags migrate to Trello Labels on the corresponding Card. We create labels in Trello with names matching the Work as Team tag names and assign a default color. If Work as Team has more than 10 distinct tags across all projects, we consolidate to the top 10 by frequency during scoping to stay within Trello's label limit per Board.

Work as Team team members map to Trello Board members. We resolve members by email match. If a Work as Team user does not have a corresponding Trello account, we create a guest invitation plan during scoping. Member roles in Work as Team (Admin, Project Manager, Member, Guest) do not have direct Trello equivalents; Board admin is the highest permission level in Trello and is assigned to the original Project admin.

Work as Team project status (On Track, At Risk, Off Track, On Hold) has no native Trello equivalent. We map project status to a Board background color or a status label on all active cards. The customer chooses during scoping which approach fits their workflow better.

Work as Team custom fields migrate to Trello Custom Fields if the destination plan supports them (Standard and above). Trello Custom Fields support checkbox, date, dropdown, number, and text types. We map Work as Team field types to the closest Trello type and flag any that cannot map directly (for example, Work as Team currency fields become number fields in Trello with a note about manual currency handling). Trello custom field titles are limited to 25 characters, which we manage during scoping by truncating or abbreviating longer field names.