Migrate from Project Central to Jira

Project Central Projects map directly to Jira Projects. The Jira Project is created first with the same name and key prefix (e.g., PROJ), and serves as the container for all descendant Issues. Jira Project permissions and notification schemes are inherited from the destination Jira site's defaults and configured by the customer admin post-migration.

Project Central Tasks map to Jira Issues. We apply a type-mapping rule during scoping: Tasks with a checklist or sub-task pattern become Jira Subtasks; Tasks representing deliverables become Jira Stories; Tasks representing defects become Jira Bugs; all others become Jira Tasks. Parent-child Project Central relationships map to the Jira Epic-Story or Epic-Subtask link depending on depth. The Jira Project key and Issue type are resolved at migration time.

Project Central Projects with a parent-child Project structure map to Jira Epics within a target Jira Project. The Epic becomes the top-level container, and all child Tasks become Stories or Subtasks linked to the Epic via the parent link. This translation requires the Jira Premium or Enterprise plan if Epic management is not already enabled on the destination site.

Project Central Status values (e.g., Not Started, In Progress, On Hold, Complete) map to Jira Status records within the target project's workflow. The Jira Status Category (To Do, In Progress, Done) is assigned based on the logical grouping of the source status. Status transitions from Project Central become Jira workflow transitions, documented as a written workflow map for the admin to configure in Jira's workflow editor.

Project Central Tags migrate to Jira Labels as string values on the parent Issue record. Labels are flat (no hierarchy) in Jira, so any hierarchical tag structure in Project Central is flattened into a colon-delimited convention or split into separate labels per the customer's preference during scoping.

Project Central task Owners are resolved by email against the destination Jira site's user directory. Jira users must exist and have project membership before issue import begins. Any Owner with no matching Jira user is placed in a reconciliation queue for the customer's Jira admin to provision before record import resumes. Inactive Jira users are not assigned; records are held rather than imported with a null assignee.

Project Central does not store file attachments natively; it stores SharePoint Online links on tasks. These links migrate to Jira as URL attachment records pointing to the original SharePoint document library location. The Jira admin configures SharePoint access permissions for the migrating team post-migration. We do not download and re-upload blob data.

Project Central custom fields map to Jira custom fields of equivalent type. Text fields map to Jira Free Text Field; number fields map to Jira Number Field; date fields map to Jira Date Picker. Jira custom fields are pre-created via the Jira REST API before data import begins. Fields are scoped to the relevant Issue types and screens during the schema setup phase.

Project Central custom fields with picklist-style values map to Jira Select List (cascading if hierarchical) or Multi-select custom fields. The allowed values are created as Jira field options during schema setup. Any Project Central custom field values that do not map cleanly to Jira's option model are preserved as Free Text as a fallback.

Project Central task due dates migrate to the Jira Issue Due Date field. The original timestamp is preserved without time-zone conversion unless the source data includes a time component, in which case the Jira admin configures the appropriate time-zone handling for the site.

Project Central Views (configured list, board, or timeline views) are inventoried as written documentation including the view name, filter criteria, sort order, and grouping logic. Jira Filters are created from these specifications by the customer admin post-migration. Jira Boards (Scrum for sprint-based, Kanban for flow-based) are documented separately as a configuration guide for the admin to set up against the migrated Issues.

Project Central comments on tasks migrate to Jira Issue Comments via the Jira REST API. @mentions in comments are translated to Jira user mentions using email-based matching against the Jira user directory. Rich text formatting in comments is preserved as Jira's Wiki-style markup where possible.