Migrate from UpWave to Jira

Each UpWave Board maps to a Jira Project. We create the Jira Project first, assign the appropriate Project key (derived from the board name), and configure the default Issue Type scheme before card ingestion begins. Jira's project permissions and notification schemes apply from this point.

UpWave columns map to Jira Status values within the project's workflow. The column names become Status display names; the column order becomes the workflow sequence. If UpWave columns use color coding or custom types, we map them to Jira Labels or a custom color field in the destination. Jira Status values must belong to a configured workflow before issues can transition through them.

UpWave cards migrate as Jira Issues. The card title becomes the Jira Summary; the card description migrates as the Jira Description field (plain text or rich text depending on destination field configuration). Card color maps to Jira Labels with color-coded label prefixes. Due dates migrate to the Issue Due Date field; completed dates migrate to Resolution Date if the destination Jira project has a Resolved status in its workflow.

UpWave subtasks flatten into Jira Subtask issues with the parent-card mapped to the Jira parent Issue. We use the parent card's Jira Issue key as the parentId on each subtask insert. Jira requires that the parent Issue type scheme includes Subtask as a subtask issue type; we confirm this during project setup and document any required scheme changes.

UpWave assignees (stored as comma-separated names per card) split into individual user records. We match by email against Jira's user directory using the Jira REST API. Unmatched assignees go to a reconciliation queue; the customer's Jira admin provisions any missing users before record import resumes. Jira requires the migrating user to have the Browse Users global permission.

UpWave due dates migrate directly to Jira's Due Date field. Dates export from UpWave in the timezone of the user who initiated the export; we normalize all dates to UTC before inserting into Jira. Jira Cloud stores all dates in UTC internally and displays in the user's configured timezone.

UpWave completed dates map to Jira's Resolution Date when the card is in a closed or resolved state in the destination Jira project. We set Resolution Date only for cards that were completed in UpWave, and only when the Jira workflow includes a resolved status category.

UpWave estimate fields migrate to Jira's Original Estimate only when time tracking is enabled on the source UpWave board. Boards where time tracking was never turned on will not have this column, and Jira will not receive an estimate. We flag missing estimates in the migration report and note the board-level setting for the customer's awareness.

UpWave time-spent fields migrate to Jira's Time Spent field. Jira requires the issue to have the Aggregate Progress or Original Estimate fields set before time tracking can record spent time, so we insert estimates before logging time. Time tracking must be enabled on the Jira project before this field accepts values.

UpWave card colors (red, blue, green, yellow, orange, purple, grey) map to Jira Labels with color-prefixed values (e.g., color:red, color:blue). We create the label prefix during scoping and apply the mapping during the card-to-issue transform. Jira labels have a 255-character limit per label; color names stay well within that limit.

UpWave Teams grouping boards and members map to Jira Project Roles (Developers, Administrators, Members) or Groups depending on the destination Jira project's permission scheme. We document the UpWave team membership during discovery and create matching Jira groups or project roles before assigning user memberships.