Migrate from Accolade to Jira

Accolade Portfolios are top-level organizational containers with budget allocations, strategic alignment tags, and linked Projects. We map each Portfolio to a Jira Project (either Software or Business type depending on the innovation type). Portfolio metadata including start date, end date, and strategic tags migrate as Jira Project description fields and custom fields. Budget figures migrate as numeric custom fields on the project level. Jira has no native portfolio roll-up object, so we document the full portfolio hierarchy for the customer to configure in Jira Product Discovery or a third-party portfolio tool.

Accolade Projects map to Jira Issues (typically Epic at the top level, with Stories or Tasks below). Each Accolade Project maps to a Jira Epic within the corresponding Project. Project stage, status, owner assignment, start date, and end date migrate as Epic fields and custom fields. Multiple Accolade Projects linked to a single Portfolio create multiple Epics under the target Jira Project.

Accolade Innovations represent early-stage ideas submitted through the platform. We map Innovations to Jira Stories or Tasks depending on their estimated scope. Submission date, originator, scoring attributes, and workflow state map to Jira Story fields and custom fields. Where Accolade tracks an Innovation-to-Project promotion relationship, we reconstruct the Jira Epic-link relationship to preserve the lineage that Accolade does not always export intact.

Accolade Business Units segment data for reporting and governance. We map each Business Unit to a Jira Project (preferred for data isolation) or to Jira Components within a Project (preferred when the same team manages multiple BUs). Multi-level BU hierarchies flatten during export, and we document the flattening path so the customer can restore hierarchy in Jira if needed.

Accolade supports user-defined fields on Projects and Innovations. We extract the full schema including field type, required flag, and picklist options. At import time, we create matching Jira custom fields. Since Accolade allows different BU-scoped schemas on the same object, we build a field superset and flag per-record nulls in the field-coverage report. Picklist options migrate as Jira custom field options.

Accolade uses configurable workflow stages with gate approvals. We export the full stage definition including stage name, order, and optional approver assignment. Each stage maps to a Jira Status in a Jira Workflow. Approver assignments document separately as a written inventory; Jira does not have a native approval gate object, so the customer configures approver notification rules in Jira automation or Jira Service Management approval gates post-migration.

Documents and files attached to projects and innovations export with their original filenames, MIME types, and content. We transfer binary blobs directly and re-attach them to the corresponding Jira Issue. Files over 100MB are chunked during extraction and reassembled on the Jira side with SHA-256 checksum verification. Attachment metadata (upload date, uploader) migrates as Jira comment or attachment description.

User accounts include name, email, role, and BU assignment. We export the user roster and map Accolade roles to Jira project roles (Administrators, Developers, Users). Active licenses and deprovisioned accounts flag separately for the customer's Jira admin to provision or deactivate during onboarding.

Audit comments and activity history are stored as timestamped entries linked to a project or innovation. We export these as a flattened feed and append them as Jira comments on the corresponding Issue. Comment author maps to the Jira user by email match; comments from deprovisioned users import under the migration service account and are flagged in the reconciliation report.

Accolade tracks quantitative metrics against projects such as budget consumed, schedule variance, and custom KPIs. These are numeric time-series values that we export as structured key-value records and map to Jira custom fields (Number, Date, or Text depending on metric type). KPI dashboards in Accolade do not migrate; we deliver a written inventory of every tracked KPI for the customer to rebuild as Jira dashboard gadgets or a reporting tool.