Migrate from Taiga to monday Work Management

Each Taiga Project maps to a monday.com Workspace, with the project name preserved as the workspace name and project description carried into the workspace overview. We create one primary Board per project for sprint work and a secondary Board for backlog items if the Taiga project contains both active sprints and a backlog queue. Project-level member roles (Admin, Member, Viewer) map to monday.com workspace member permission levels. If the customer has more than 10 Taiga projects, we consolidate low-volume projects into boards within a single workspace to avoid monday.com workspace limit surprises on the Basic plan.

Taiga Milestones with start_date and finish_date become monday.com Groups on the project's primary board. The group name carries the Milestone subject, and we create a Date column with the sprint window. monday.com has no native sprint velocity tracking or burndown, so if the customer relies on sprint velocity reports from Taiga, we flag this for manual reporting setup in monday.com dashboards post-migration. Where Taiga Milestones are unordered, we sequence the Groups to match Taiga's order_by field.

Taiga Epics have no direct monday.com equivalent. We create a dedicated monday.com Feature board with one item per Epic, preserving Epic color and status. The Epic's description maps to the item description, and linked User Stories are tracked as sub-items or linked items using monday.com's Connect Boards integration. The customer chooses between a single cross-project Epics board or one per project during scoping. If the customer does not use Epics, this step is skipped.

Taiga User Stories map to monday.com items on the project's primary board, grouped by their Milestone. Story subject becomes item name. The Taiga status (New, In Progress, Ready for Test, Done, Archived) maps to the monday.com Status column values, which we rename to match Taiga's status labels. Story points (numeric) map to a Numbers column. Assignee maps to the Person column. Custom attributes on User Stories map to monday.com custom fields (Dropdown, Date, Number, Text) based on the Taiga attribute type. If Taiga uses a custom attribute as a priority field, we create a Priority column in monday.com.

Tasks inside User Stories can map as monday.com sub-items (available on Pro and Enterprise plans) or as linked items on the same board depending on the customer's preference and plan tier. We default to sub-items when the customer is on a Pro or Enterprise monday.com plan. For Standard and Basic plans without sub-item access, Tasks become standalone items on the board with a Text column linking to the parent User Story item name. Task status, assignee, due date, and custom attributes map using the same column pattern as User Stories.

Taiga Issues (standalone bugs and tracked work outside the sprint backlog) map to monday.com items on the project's secondary Backlog board. Issue type (Bug, Enhancement, Question, General) maps to a Dropdown column; Severity and Priority map to Dropdown or Labels columns. We preserve issue status using the same Status column mapping as User Stories. If the customer has no active Issues, this step is skipped.

Taiga wiki pages with Markdown content export as monday.com Docs. We convert Markdown to monday.com's rich text format during import. However, inter-page wiki links (links from one wiki page to another using Taiga's internal wiki syntax) do not map to monday.com Doc cross-links, which do not exist in the platform. We flag every broken inter-page link in the handoff document so the customer's admin can re-link manually. Teams relying heavily on wiki documentation should plan a manual review post-migration.

Taiga custom attributes are defined per project and per artifact type. We extract every distinct custom attribute name and type from the source project export, then configure matching monday.com custom fields on the target board. Enum and multi-enum attributes become Dropdown or Tags (Tags requires Pro or Enterprise). Text and long text become Text columns. Numbers and dates map directly. If a custom attribute uses free-form text but the customer expects controlled vocabulary in monday.com, we flag this as a normalization decision during scoping. All custom attribute values are carried as column values into the migrated items.

Taiga member roles (Admin, Member, Viewer) per project map to monday.com workspace member roles with equivalent permission levels. We extract all Taiga user memberships and role assignments per project, then create matching monday.com workspace invitations during migration. If a Taiga user has different roles across different projects, we grant the highest permission level in monday.com to avoid under-accessing and flag the discrepancy in the role reconciliation report.

Attachments on User Stories, Tasks, and Issues are stored as media URLs in Taiga's export. We retrieve files from Taiga's media storage URL (for cloud-hosted instances) or the configured S3/storage path (for self-hosted), then upload each file to the corresponding monday.com item's Files column using the monday.com API. For self-hosted Taiga instances where the media storage is inaccessible after decommissioning, we include the original file URLs as clickable links in the item description and flag this in the handoff document. Attachment metadata (filename, upload date) is preserved in a Text column.

Taiga free-form tags on User Stories, Tasks, and Issues map to monday.com Tags (Pro and Enterprise plans only) or Labels (Standard and above). If the customer is on Basic plan, tags are converted to Text column entries, which limits filtering capability. We extract the full tag vocabulary from Taiga and apply it consistently across all migrated items. If Taiga uses a controlled vocabulary of tags that maps to a dropdown in monday.com, we apply the Tags column as the closest functional equivalent.

Taiga stores comments on User Stories, Tasks, and Issues as activity entries in its JSON export. We extract comment text, author, and timestamp and create monday.com Updates (comments) on the corresponding items. The author maps to the monday.com workspace member if a matching email exists; otherwise, the comment author name is preserved as text. Inline code blocks and Markdown formatting in Taiga comments convert to plain text or basic bold/italic in monday.com Updates, which has no Markdown support.