Migrate from CONTACT Project Office to Jira

CONTACT Project Office Projects map to Jira Projects. Each Jira Project requires a unique Project Key (2-10 uppercase alphanumeric characters) that prefixes all Issues. We work with the customer during discovery to define Project Keys that avoid conflicts with any existing Jira projects in the destination org. Project metadata including description, lead, and default workflow migrate as project-level configuration.

CONTACT Project Office Tasks map to Jira Issues. The Task name becomes the Issue Summary field. Task description migrates to the Issue Description field, with formatting preserved where possible. Status mapping requires configuration: we inventory all source Task status values during discovery and map each to a Jira Status value that exists in the target project's workflow scheme.

CONTACT Project Office Subtasks map to Jira Sub-Tasks. Jira supports one level of Sub-Task nesting under a parent Issue. If the source data contains multi-level subtask hierarchies (Subtask of Subtask), we flatten to two levels by creating additional Issue records with a Parent Link rather than true subtasks, or we discuss with the customer whether to collapse the deepest level into comments on the parent Issue.

CONTACT Project Office assignees resolve by email address lookup against the Jira destination org's User table. We extract every distinct assignee across Tasks and Subtasks during discovery and check for Jira User existence. Assignees without a matching Jira User go to a reconciliation queue for the customer's admin to provision or map to an inactive placeholder User before migration proceeds.

CONTACT Project Office custom fields map to Jira custom fields of equivalent type. Jira enforces typed field schemas (text, number, date, datetime, single-select, multi-select, user picker, URL). We inventory all source custom fields during discovery, classify each by data type and value format, then pre-create the equivalent Jira custom fields before any record import. Multi-select values in CONTACT Project Office map to Jira multi-select options; date values must be normalized to Jira's ISO 8601 format.

CONTACT Project Office file attachments migrate to Jira as ContentDocument records attached to Issues via ContentDocumentLink. Jira Cloud enforces a 10 MB per-file attachment limit; attachments exceeding this threshold require separate transfer via a file transfer tool or cloud storage link stored in an Issue comment. We inventory all attachments during discovery to identify volume and size outliers before migration begins.

CONTACT Project Office Comments on Tasks and Subtasks migrate to Jira Issue Comments. Comment authorship and timestamp migrate as Jira Comment fields. Rich text formatting in source comments is converted to Jira Wiki-style markup or stored as plain text with formatting notes. Comments are imported after the parent Issue exists to maintain proper thread ordering.

CONTACT Project Office priority values (numeric or named) map to Jira Priority values. We inventory the source priority scale and configure Jira Priority to match the source semantics (Highest, High, Medium, Low, Lowest). If the source uses a numeric scale, we map to named Priority and store the original numeric value in a custom field for audit.

CONTACT Project Office Task status values map to Jira Status values within the target project's workflow. We inventory all source status values during discovery and configure the Jira workflow to include equivalent Statuses. Any source statuses that have no Jira equivalent are flagged during discovery, and the customer decides whether to map to a closest-match existing status or extend the workflow with a custom status.

Jira Issue Types (Story, Bug, Task, Epic, Sub-Task) are configured during Jira project setup. We set up the Issue Type Scheme to match the source data classification: Tasks from CONTACT Project Office map to Jira Task Issue Type by default, with Subtasks mapped to Sub-Task. The customer chooses whether to use Epics for high-level planning items during discovery.