Migrate from ITM Platform to Jira

ITM Platform Portfolios are top-level containers grouping Programs and Projects. We map each Portfolio to a Jira Project Category for organizational grouping, or to a dedicated Jira Project with an Epic structure if the customer requires portfolio-level reporting in Jira Dashboards. The choice depends on how many Jira Projects the migration generates and whether Advanced Roadmaps is licensed.

ITM Platform Programs group related Projects under a Portfolio. We map Programs to Jira Projects where the Program has more than 20 child Projects and warrants its own Jira project, or to Epics within the parent Jira Project where the Program maps to a Portfolio Category. Strategic alignment tags from the Program migrate to Jira labels or a custom Program__c field.

ITM Platform Projects map directly to Jira Projects. Each Jira Project is created with the appropriate project type (Team-managed or Company-managed) based on the customer's chosen Jira governance model. Project dates, status, budget, and owner migrate to Jira Project properties or custom fields. ITM Project methodology (Agile or Waterfall) determines the initial Jira Board configuration.

ITM Platform Tasks map to Jira Issue types. We map based on the ITM Platform task type and the customer's configuration: standard work tasks become Jira Task, deliverables with acceptance criteria become Jira Story, and defects found during execution become Jira Bug. The mapping is configurable during scoping based on the customer's existing Jira issue type scheme.

ITM Platform Subtasks map to Jira Subtask issues, linked to the parent Jira issue via the Parent Link field. Where the destination Jira project uses a Team-managed project without Subtask enabled, we flatten Subtasks into a structured checklist field or as separate Jira Tasks with a parent relationship label. Task dates, status, assignee, and estimated hours migrate directly.

ITM Platform Milestones are date-driven markers belonging to Projects or Tasks. We map milestone dates to Jira Fix Version (Releases) where milestones represent deliverable checkpoints, or to the Issue Due Date where a milestone maps to a specific task. The migration is configurable per milestone during scoping, and we preserve the milestone name as the Fix Version name or as a custom milestone__c field on the issue.

ITM Platform Baselines capture schedule, cost, and revenue snapshots per project. Jira has no native baseline comparison feature outside of Advanced Roadmaps. We extract all baseline records as a structured JSON or CSV dataset and attach it to the Jira Project as a custom Baselines__c field or as a Confluence page linked from the Jira Project. The customer reconciles baselines post-migration using Advanced Roadmaps or a third-party plugin.

ITM Platform Risks are a distinct entity with probability, impact, owner, and mitigation plan. Jira Software does not have a native Risk object. We map Risks to Jira Issues using a custom Risk Issue type (if the customer's Jira scheme includes one) or to standard Jira Issues with custom fields: Probability__c, Impact__c, Mitigation__c, and Risk_Status__c. The customer configures the Risk issue type scheme during scoping.

ITM Platform entity-scoped custom fields (project, task, purchase, risk) map to Jira custom fields of equivalent data type. We extract the custom field definition (key, type, options) and create Jira custom fields with matching names in the destination Jira instance. Text, number, date, and select fields map directly. Multi-select and checkbox fields map to Jira multi-select or label fields. Custom field configuration (screens, default value, search template) is deployed via Jira REST API after schema validation.

ITM Platform time entries track hours logged against Tasks or Projects. We map these to Jira Worklog records linked to the corresponding Jira Issue. Each worklog preserves date, hours, user (resolved via email match), and description. Jira requires the user making the worklog API call to match the worklog author; we handle this by using the ITM Platform user email to resolve the Jira accountId before inserting each worklog record.

ITM Platform Users are referenced across Tasks, Risks, Assignments, and Time Entries. We extract the full user list (name, email, role) and match by email against the Jira destination site's user directory. Any ITM Platform user without a matching Jira accountId goes to a reconciliation queue for the customer's admin to provision before record import proceeds. We do not create Jira accounts via API without explicit admin authorization.