Migrate from YouGile to Jira

YouGile Projects map directly to Jira Projects as top-level containers. The project name, description, and member list transfer. Jira requires that each Project be assigned a Project Key (prefix for issue keys) before issue import begins, so we define keys during scoping using the YouGile project name abbreviation. Jira projects also require a Project Lead and an Issue Type Scheme, which we configure before migration.

YouGile Board Columns (e.g., To Do, In Progress, Review, Done) map to Jira Status values. Custom column names require explicit mapping because Jira uses a defined status set tied to a Workflow Scheme. We create a custom workflow scheme for the Jira project that includes the exact status values from YouGile, preserving the column order as the status sequence. Standard Kanban columns typically map 1:1; custom columns require a judgment call during scoping on whether to create new statuses or merge into existing ones.

YouGile Tasks are the primary work item and map to Jira Issues. We preserve summary, description (as Jira Description in Atlassian Document Format), assignee (by email lookup to Jira User), due date, priority, labels, creation date, and last-modified date. Status is set by resolving the YouGile Column to the mapped Jira Status value. Issue type defaults to Task; the customer chooses whether bugs use Issue type Story or Bug based on their Jira project configuration.

YouGile Subtasks map to Jira Sub-Task Issues, which require that the Jira project enable sub-tasks (Issue Type Sub-Task must be in the project's Issue Type Scheme). The parent-child relationship is preserved by setting the Parent Issue Key on each sub-task. Completion state from YouGile maps to Status resolved or unresolved on the Jira sub-task. Multi-level subtask nesting (sub-subtasks) flattens to single-level Jira sub-tasks with the full path preserved in the sub-task summary as a prefix.

YouGile treats each Task as a chat thread. We extract chat messages as Jira Comments with author (by email lookup), timestamp, and message body. Jira Comment ordering is chronological by creation timestamp. Rich text formatting in YouGile messages converts to Atlassian Document Format. Thread continuity is not preserved as a nested structure in Jira; all messages land as flat comments on the issue.

YouGile embeds time-tracking entries within tasks as hours logged. We extract logged hours and map them to Jira Worklog entries (native, with author and timestamp) if the Jira project has Time Tracking enabled. If YouGile time entries include billing rates, we store those as a custom field rate_log__c since Jira Worklog does not carry rate data by default. The customer chooses between worklog or custom field during scoping based on their billing workflow.

YouGile Labels map to Jira Labels (native label field). Label names and color metadata migrate where the source label carries a hex color; Jira Labels are text-only, so color is documented as a custom text field if the customer needs to preserve it. Label assignment on Tasks becomes Label assignment on the corresponding Jira Issue.

YouGile file attachments are referenced by URL in YouGile's data. We download each attachment and re-upload to the Jira issue via the Jira Attachments API. The original filename and linked issue association are preserved. Large files (>10 MB) require chunked upload handling. If YouGile attachments are hosted behind authentication, we work with the customer's credentials to access them.

YouGile team members map to Jira Users by email address. We extract all distinct user emails referenced on tasks, subtasks, and comments. Each email is matched against the Jira destination site's user list. Users without an existing Jira account go to a reconciliation queue for the customer's admin to provision. If YouGile stores user roles or titles, these map to Jira project role assignments.

YouGile limited custom fields on tasks map to Jira Custom Fields of equivalent type. Text fields map to Jira Text Field (Short Text or Free Text); number fields map to Number fields; date fields map to Date fields; dropdown values map to Select Lists. Jira project administrators must pre-create custom fields in the target project before migration because Jira Custom Fields are scoped per project. We flag any YouGile custom field types with no Jira equivalent for customer decision during scoping.

YouGile Gantt-chart visual data is view-only and not stored as a structured field in the data export. We extract start and end dates on tasks as Jira Date fields (Start Date and Due Date on the issue). The visual Gantt layout cannot be reproduced in Jira; we document this as a manual rebuild item in the migration report. Jira Premium's Advanced Roadmaps offers a Gantt-style view if the customer subscribes.