Migrate from YouTrack to Asana

YouTrack Issues map to Asana Tasks using summary as name, description as notes, and status as a mapped section or workflow stage. Priority (Urgent, High, Normal, Low) maps to Asana Custom Fields of enum type. The issue number is preserved in a custom field yt_issue_number__c for cross-reference. Attachments download from YouTrack via PersistentFile API and re-upload to Asana Tasks as file attachments, preserving original filenames and MIME types.

YouTrack Projects map 1:1 to Asana Projects. Project type (Scrum, Kanban, Bug-tracking) is preserved as a custom property so the customer's admin knows which board view and workflow template to apply in Asana. We create Asana Projects in the target workspace using the YouTrack project slug as a prefix to maintain naming continuity during the transition window.

YouTrack CustomFields are globally defined but have per-project bindings. We export the global field definition plus all project-level default values. On import, we create corresponding Asana Custom Fields at the workspace level and apply them to the relevant Projects. Enums, integers, strings, dates, and user fields map to Asana enum, numeric, text, date, and person Custom Field types respectively. Project-specific field defaults are recorded in a migration notes sheet for manual application.

YouTrack Agile Boards store configuration as board-specific settings referencing Issues, swimlanes, and column states. Asana does not have a separate Board entity; Board is a view mode applied to a Project. We export board definitions (column order, WIP limits, swimlane grouping) as a written configuration guide and include the list of Issues and their column assignments so the customer's admin can recreate the board structure manually. We do not export board configuration as deployable code because the schema is not transferable.

YouTrack Sprints are time-boxed issue collections with start/end dates and capacity settings. Asana has no native Sprint entity. We export sprint assignments (which Issues were in which Sprint with what start and end dates) and map them to Asana Sections named after the Sprint. Workload and capacity data does not transfer to Asana because there is no sprint capacity model; we document this gap in the migration handoff so the customer can evaluate Asana's Workload view as an alternative.

YouTrack attachments are PersistentFile entities linked to Issues. We download file content via the YouTrack API and re-upload to the corresponding Asana Task using the Asana Attachments API. Original filenames and MIME types are preserved. Large files (over 100 MB) are flagged in the migration report for the customer's admin to handle manually or via a file transfer service to avoid API timeout issues.

YouTrack Tags attached to Issues map directly to Asana Tags. We preserve the full tag set per Issue and recreate them in the destination Asana workspace. Tag colors from YouTrack do not transfer because Asana does not support per-tag color customization in the current API.

YouTrack Workitem entries (duration and description linked to Issue and User) export as structured data. In Asana, we create Subtasks with the work description as the subtask name and the duration stored in a custom field yt_workitem_duration__c. The customer's admin decides whether to display time data as subtasks (visible in Timeline) or as a custom field summary. Asana's native time tracking is not available below Enterprise tier; we flag this gap and offer a custom field workaround for Standard and Premium plans.

YouTrack Saved Queries store filter definitions referencing field names and values. Asana has no Saved Query equivalent. We export all Saved Queries as written filter definitions (field, operator, value) so the customer's admin can recreate them as Asana filters. Saved Query names map to Asana custom field labels where applicable.

YouTrack Issue comments map to Asana Task Stories (the comment thread). Comment author maps to the Asana user matched by email. Timestamps are preserved. Comments containing @mentions convert to Asana @mentions by email match against the Asana workspace user list.

YouTrack Issue Links (blocks, is blocked by, relates to, duplicates, clone of) map to Asana Task Dependencies. We apply the dependency direction from the YouTrack link type (e.g., 'is blocked by' in YouTrack becomes a 'blocks' dependency in Asana with reversed direction). Asana only supports blocks/blocked-by dependency types, so some link types (relates to, clone of) map to a custom field yt_link_type__c with the original relationship noted.

YouTrack KB articles are project-scoped Markdown documents with tags and attachments. Asana has no Knowledge Base feature. We export full article content and structure, preserving Markdown formatting, and deliver them as a structured inventory document with project tags so the customer's admin can recreate them in Confluence, Notion, Google Docs, or another knowledge management tool of their choosing.

YouTrack Workflows are JavaScript-based rule sets defined per project, often referencing custom field IDs. We export workflow source code as text files and deliver a written inventory of every Workflow with its name, project scope, trigger condition, actions, and a note that field ID references will need manual updating if the Workflow is deployed in another YouTrack instance. Workflows cannot be deployed to Asana because Asana's Rules-based automation uses a different execution model.

YouTrack ProjectTeam entities define group membership per project. We map these to Asana Teams, preserving group names and memberships. Role assignments (Viewer, Editor, Reporter, Admin) map to Asana team roles (Member, Admin). ProjectTeam visibility settings become Asana Team project membership settings.