Migrate from YouTrack to Trello

YouTrack Issues map to Trello Cards with the Issue Summary as the Card title, Issue description as the Card description, Issue type as a Card Label, and Issue priority as a colored Label. We preserve the created and updated timestamps as Card metadata. The migration is 1:1 at the record level, but the visual representation shifts from a structured issue row to a card on a board List.

YouTrack Projects map directly to Trello Boards. The Project name becomes the Board name, and the Project description becomes the Board description. We create the Board in the destination Trello Workspace before any Cards are imported so that the Board ID is available for Card assignment. Project type (Scrum, Kanban, Bug-tracking) is noted as a Card label since Trello has no native project type field.

YouTrack Agile Boards with swimlanes and columns map to Trello Boards where the board Lists represent columns and swimlanes are expressed as either additional Lists or Label-filtered Card groups. We export the board configuration (column names, WIP limits, swimlane definitions) and recreate them in Trello, mapping column States to Lists with matching names. Multiple Agile Boards covering the same project create multiple Trello Boards if the customer chooses to preserve board-level filtering, or are consolidated into one Board with List-based separation.

YouTrack CustomFields map to Trello Labels if the destination plan is Standard or lower. If the customer is on Trello Business Class or Enterprise, we map to Trello Custom Fields (checkbox, date, dropdown, number, text). YouTrack's multi-value custom fields (e.g., multi-select) cannot map to Trello's single-value dropdown Custom Fields without a value-split or a choice to store concatenated values in a text field. We flag every CustomField with a type incompatibility during scoping and document the chosen resolution strategy.

YouTrack Issue State values (e.g., Open, In Progress, Resolved, Closed) map to Trello List names on the target Board. We preserve the State order as List order. If YouTrack uses a custom state workflow with more than 20 distinct states, we consolidate them to the most commonly used values or add a State label on Cards to preserve the full state history without exceeding the practical List limit.

YouTrack Priority field values (e.g., Critical, High, Normal, Low) map to colored Trello Labels. We assign consistent colors per priority level (Critical = red, High = orange, Normal = yellow, Low = green) across all migrated Boards so that priority filtering works uniformly in Trello's filter view.

YouTrack Issue Type values (Bug, Feature, Task, Story, etc.) map to Trello Labels with type-specific colors. Trello has no native issue type concept, so a Label per type is the standard workaround. We document the label color assignment per type and apply it consistently across all migrated Boards.

YouTrack PersistentFile attachments linked to Issues download via the YouTrack REST API and upload as Trello Card attachments. We preserve the original filename and MIME type. Large attachments (over 10 MB) require Trello's Power-Up configuration or an external hosting reference; we flag files exceeding Trello's 10 MB attachment limit during scoping and recommend a pre-upload to Trello's Google Drive or Dropbox Power-Up as a pre-migration step.

YouTrack Issue comments map to Trello Card comments. The comment author and timestamp are preserved. If comments contain @-mentions or YouTrack-specific formatting (YouTrack markdown variant), we convert the formatting to Trello's markdown subset and flag @-mentions as requiring manual re-notification post-migration since Trello does not have a user mention system in comments equivalent to YouTrack's.

YouTrack Tags are label entities attached to Issues and map directly to Trello Labels. Tag names and colors migrate. If the customer uses tag hierarchies (e.g., product.frontend.bug), we flatten them to single-label names and add a prefix so filtering in Trello still reflects the original taxonomy.

YouTrack Workitems are structured time entries (duration + description) linked to Issues. Trello has no native worklog or timesheet object. We offer two migration strategies: (1) convert work entries to Checklist items on the Card with the entry description and duration; (2) append a time log summary to the Card description as a formatted table. The customer selects the strategy during scoping. If the customer uses Trello with a time-tracking Power-Up (Everhour, Planyo), we flag the Workitem export format needed to integrate with that Power-Up's import tool.

YouTrack Knowledge Base articles have no native Trello equivalent. We offer two strategies: (1) migrate article content as Markdown Cards pinned to the Board and titled with the article name; (2) populate the Board description with a structured summary of all articles and add a link to an external document repository where articles are stored post-migration. We do not migrate the Knowledge Base as code; articles require manual reorganization by the customer post-migration.

YouTrack Workflows are JavaScript rule sets referencing internal field IDs. They cannot migrate as functional code to Trello's Butler automation, which uses a different rule syntax and trigger model. We export the workflow source and parse for field references to produce a written inventory documenting what each workflow does (trigger conditions, actions, field dependencies). The customer rebuilds equivalent Butler rules in Trello manually or with assistance from a Trello partner.

YouTrack Saved Queries store filter definitions referencing YouTrack field names. Trello Filters support a different syntax (label:, @member, due:, list:, etc.). We export Saved Queries as a written inventory with the original filter text and a Trello-equivalent filter string where one can be constructed. Filters that reference custom fields not available in the destination Trello plan (e.g., date range filters on Custom Fields when on Standard plan) are flagged as requiring manual rebuild post-migration.

YouTrack ProjectTeam entities define group membership and roles per project. Trello Workspace and Board permissions do not have the same role granularity (Trello uses Admin, Normal Member, Observer, Guest). We export the project membership structure as a written document and flag the role gaps so the customer's admin can map the closest Trello permission level to each original project role.