Migrate from Taskworld to Trello

Taskworld's Workspace is the top-level container holding all Projects, Members, and settings. We map workspace-level organization metadata (name, description, member list) directly to a Trello Workspace. Guest collaborators in Taskworld (up to 30 on Business) do not have direct Trello equivalents; they are mapped as Workspace members at the Standard tier or flagged for manual invitation post-migration. On Trello Enterprise, guest management policies are controlled separately by the workspace admin.

Each Taskworld Project maps to a Trello Board. The project's name, description, color label, and member list transfer directly. Taskworld's default view setting (Kanban, Timeline, Calendar) has no native Trello equivalent; we note the original preference and apply Kanban as the destination default since Trello is built around list-based boards. Projects with Timeline/Gantt views are flagged for the Timeline Power-Up if the destination plan supports it.

Taskworld Tasks map to Trello Cards. Assignee transfers as Card member; due date transfers as the due date field; priority level transfers as a color label (red for high, orange for medium, green for low, blue for none); description transfers as card markdown. Completed status maps to a closed card or a card moved to a Done list. Labels from Taskworld tags transfer as Trello labels with the original tag string preserved.

Taskworld nested subtasks (tasks within a parent task) have assignees, due dates, and checklists of their own. Trello has no native subtask object. We convert top-level subtasks to checklist items under the parent card. If a subtask itself contains a nested checklist, we flatten it to a single-level checklist set under the parent card and flag any subtask with a sub-checklist for manual rebuild as a child card using the Hierarchy Power-Up. Percent-complete displayed on the Taskworld task is recalculated from the checklist completion ratio in Trello.

Taskworld checklist items migrate directly to Trello checklist items under the corresponding card. Completion status is preserved. If a checklist item is a standalone item (not tied to a subtask), it transfers as a plain checklist entry. Checklist item order within the parent task is preserved in the card checklist sequence.

Taskworld custom fields are defined per-project via the Customize panel, meaning the same attribute (e.g., Customer Name, Priority Level) must be defined separately in each project. We extract all project-level custom field definitions and their values across the workspace. In Trello, the Custom Fields Power-Up applies board-wide: we consolidate duplicate custom field definitions from multiple Taskworld projects into a single custom field per board, avoiding the per-project repetition. The customer must install the Custom Fields Power-Up on each destination board before migration.

Taskworld stores directional task dependencies (blocks/blocked-by) as properties on the task object. Trello has no native dependency tracking at the free or standard tiers. We resolve the dependency graph during extraction and apply it in one of two ways depending on the destination plan: at Premium and Enterprise, we use the Card Dependencies Power-Up API to create explicit dependency links; at Standard, we apply a labeled convention (e.g., DEP-BLOCKED-BY: card name) as a card label so the admin can visually reconstruct the dependency chain post-migration.

Taskworld file attachments stored on tasks are downloaded from Taskworld storage and re-uploaded as Trello card attachments. We preserve the original filename, file type, and upload date. Files exceeding Trello's 10MB per-attachment limit (or 250MB on Enterprise) are flagged and provided in a manifest for manual handling. Trello Enterprise allows larger file sizes via admin-configured attachment settings.

Taskworld task-level comments migrate as Trello card comments with the original comment text, author attribution, and timestamp preserved. Taskworld's separate project chat messages do not have a direct Trello equivalent; we migrate chat message text as comments on the most recently updated card within that project or flag them for a manual move to a project documentation tool. Author attribution resolves by matching email against the Trello workspace member list.

Taskworld time entries logged against tasks have start time, duration, and optionally a description. Trello has no native time tracking field. We extract logged time entries and store the duration as a custom field on the card (if the Custom Fields Power-Up is installed), or as a checklist item with a formatted duration string. Time entry metadata (total hours, billable flag if present) is preserved in the migration manifest for the admin to configure in a Trello time-tracking Power-Up if needed.

Taskworld workspace members and guest collaborators (up to 30 on Business) map to Trello workspace members by email. Full members become active Trello workspace members; guests without an email-matched Trello account go to a reconciliation queue. Role mapping (admin, member, guest) in Taskworld translates to Trello Workspace Admin or normal Member. On Trello Enterprise, SAML SSO provisioning is a separate admin step post-migration.

Taskworld tags (applied to tasks and projects for categorization) migrate as Trello card labels. Tag strings are preserved exactly; color assignment uses Trello's default label colors unless the customer specifies a color mapping during scoping. Tag hierarchy (if used in Taskworld) is flattened to a single-level label string. Labels are applied at the card level for task tags and at the board level for project-level tags.