Migrate from Taiga to Trello

Taiga Projects map directly to Trello Boards. In Trello's Workspace model, each Board sits inside a Workspace. We create one Trello Workspace per Taiga Project or consolidate multiple Taiga projects into a single Workspace depending on the customer's board strategy. Project settings (description, color, membership) map to Board description and Workspace member invites.

Taiga Milestones have start_date, end_date, and name. Trello has no native sprint object. We map each Taiga Milestone to a Trello List on the destination board, naming it with the milestone name and optionally adding the date range in the list header. For teams needing sprint reporting, we pre-create Custom Fields on the board (Sprint Start, Sprint End) and populate them per card.

Taiga Epics are top-level backlog items with status, color, and description that can contain multiple User Stories. Trello has no Epic object. We map each Taiga Epic to a Trello Label with a naming convention (e.g., [Epic] Feature Name) and assign that Label to all Cards derived from User Stories within that Epic. We document the Epic-Label mapping so the customer can maintain it as Labels are managed per board.

Taiga User Stories carry subject, description, status, points, assignee, milestone reference, and custom attributes. We map story points to a Trello Custom Field (Number: Points), status to the appropriate List on the destination board, and the milestone reference to the List name. Assignee becomes a Trello member assignment on the Card. Description migrates as card description with Markdown preserved.

Taiga Tasks belong to User Stories and have their own status, assignee, custom attributes, and due date. For smaller projects, Tasks map directly to Trello Cards on the same board as their parent User Story. For larger projects, we map Tasks to Checklist items on the parent User Story Card (using the 'move tasks to checklist' strategy) to reduce board clutter and preserve the parent-child relationship that flat Trello Cards cannot natively express.

Taiga Issues are standalone work items with type (bug, question, enhancement), severity, priority, status, and custom fields. We map Issue type to a Trello Label (Bug, Question, Enhancement), Issue severity and priority to Custom Fields (Select: Low/Medium/High) on the Card, and status to the appropriate List. Archived issues in Taiga become Archived Cards in Trello.

Taiga supports per-project custom attributes on User Stories, Tasks, and Issues with types including text, number, date, url, and enum (dropdown). We pre-create Trello Custom Fields on the destination board matching the custom attribute definitions, then populate them on each migrated Card. Enum attributes become Trello Select Custom Fields with the same options. If the same custom attribute is defined across multiple projects, we create it once per board and flag any project-specific variations.

Taiga roles (Admin, Member, Viewer) per project map to Trello Workspace member roles. We resolve each Taiga user by email and invite them to the destination Trello Workspace with the closest available role. Trello's permission model (Workspace Admin, Workspace Member, Board Observer) requires a mapping decision during scoping: Taiga Admins become Workspace Admins, Members become Workspace Members, Viewers become Board Observers if the Enterprise tier is purchased or as a restricted Board Member otherwise.

Taiga Wiki Pages are Markdown documents stored per project. Trello has no native wiki. We export the wiki page tree and convert each page's Markdown content into the description field of a dedicated Card (titled with the wiki page name) on the destination board. For teams with extensive wiki content, we recommend Trello's Docs Power-Up as a replacement and map the wiki hierarchy to a Docs folder structure. Links between wiki pages do not automatically re-link in Trello and require manual review.

Taiga free-form tags on User Stories, Tasks, and Issues map directly to Trello Labels. We extract all tag strings, deduplicate them, and create matching Labels on the destination board. Where Taiga tags serve dual purposes (e.g., some tags represent Epics, others represent priority), we recommend splitting them during scoping: Epic tags become the dedicated Epic Label set (mapped in object #3), and remaining tags become standard Trello Labels.

Taiga stores file attachments as media URL references on User Stories, Tasks, and Issues. We retrieve files from Taiga's media storage URL (cloud or self-hosted instance URL) and re-upload them as Card Attachments in Trello via the Trello API. File size and type limits in Trello (10MB on Free, unlimited on Standard+) apply. We flag any attachments exceeding Trello's per-plan size limit for manual handoff.

Taiga's Kanban mode supports swimlanes (horizontal lanes splitting rows) for WIP limits or team ownership. Trello does not have native swimlanes. We map swimlane groups to a Trello Board strategy: either as a separate Board per swimlane (preferred for WIP-limit enforcement) or as a Label per swimlane on a single Board (preferred for visibility). The customer chooses during scoping, and we document the mapping decision in the migration spec.