Migrate from Deltek Project Portfolio Management to Jira

Deltek Projects (the top-level container with project status, billing type, and project manager assignment) map directly to Jira Projects. We use the Deltek project_code as the Jira project key prefix and project_name as the project name. Project Manager assignment maps to the Jira Project Lead. If the Deltek portfolio spans multiple business units, we create separate Jira Projects or a Jira Project hierarchy depending on the Jira plan tier.

Deltek WBS elements are the core work breakdown hierarchy. We split the WBS into Jira's issue hierarchy: top-level WBS items become Jira Epics, second-level items become Stories, third-level items become Tasks, and fourth-level items become Subtasks. Numeric WBS identifiers (e.g., 1.2.3.4) are preserved in the Jira issue Summary prefix and in a custom WBS identifier field for traceability. WBS-level rollup data (hours, costs) is not natively supported in Jira; we carry forward planned hours as a Story Points or Hours custom field and deliver a WBS rollup table as a supplementary export.

Deltek Resources (employees, consultants, equipment) export via Planning Data CSV with utilization and rate data. We map Deltek Resource IDs to Jira User accounts by email address. Any Deltek Resource without a matching Jira user goes to a reconciliation queue for your Jira admin to provision. Equipment or non-human resources are added as Jira users with system accounts or as Labels on the relevant issues.

Task-to-resource assignments from Deltek planning CSV migrate to Jira Issue Assignee. Assignment hours and dates map to the Jira Issue's Due Date and to a custom Estimated Hours field. Deltek's effort-driven vs. duration-driven scheduling nuances are not preserved as Jira does not have an equivalent scheduling engine model; we flag the scheduling assumption in the mapping notes.

Deltek published baseline schedules are stored as distinct plan snapshots. We carry forward the current published baseline as a Jira Fix Version named with the baseline name and date. Baseline start and finish dates map to the Fix Version's release date fields. If multiple baselines exist (original, current, target), we create multiple Fix Versions. Note that Jira Fix Versions do not store the full baseline schedule curve; we deliver a separate CSV of baseline task dates for import into Jira or a BI tool.

Deltek planned labor hours, expense amounts, and consultant costs are budget line items per WBS element. Jira does not have a native budget schema. We migrate planned hours as a custom Estimated Hours field on Jira Issues. Planned expenses and consultant costs are delivered as a separate reconciliation CSV keyed on the WBS identifier, which your finance team loads into a BI layer (Power BI, Tableau, or Deltek's own reporting tools) rather than into Jira directly. Custom Deltek cost codes map to Jira Labels for tagging.

Deltek milestones (with dates, names, and deliverables) map to Jira Issues of type Task with a milestone flag label and the milestone date as Due Date. If the milestone is portfolio-level, we attach it to the relevant Fix Version as a release-blocking issue. Flagged milestones and constraint types (As Soon As Possible, As Late As Possible, Must Finish On) migrate as custom fields.

Deltek User-Defined Data fields (text, number, date, picklist) export with the Project List Export. We create equivalent Jira custom fields using the Jira REST API, matching field types (text fields to Jira Text Field, picklists to Jira Select List, dates to Jira Date Picker). Picklist values require explicit mapping from Deltek's UDD value set to Jira's option set during scoping. Text fields with formatting are imported as plain text.

Deltek Risk registers export as structured data. Jira does not have a native Risk object, so we import risks as Jira Issues with a Risk label and type Task. Risk score, probability, impact, and mitigation plan migrate to custom fields (Risk Score, Probability, Impact, Mitigation). The Jira admin can optionally install a Marketplace app (e.g., Structure, BigPicture, or Exalate) for enhanced risk and portfolio visualization post-migration.

Deltek PIM exports documents in a folder structure. We extract the archive, reconstruct the project-relative folder tree, and attach files to their parent Jira Issue. If a PIM document maps to no single issue (e.g., a project-level deliverable), we attach it to the top-level Jira Project's description or a designated project-level issue. File binaries rely on Deltek FileStream being enabled; if it is not, we extract PIM URLs and document that file retrieval requires a manual step.