Migrate from Edison 365 to Jira

Edison 365 Ideas migrate as Jira Issues under a designated Ideas project using a custom issue type. Title, description, category, submitter email, submission date, and status all map directly. Edison 365's category taxonomy becomes Jira labels or a custom select field depending on the customer's preference. Submitter resolves to Jira assignee or reporter by email lookup.

Edison 365 Projects with standard delivery scope map to Jira Projects or to Epic-type Issues within a designated Jira project, depending on the customer's chosen portfolio structure. Name, description, owner, start date, end date, and budget all migrate. Edison 365's project-level budget becomes a custom currency field in Jira. Owner resolves to Jira User by email for assignment.

Edison 365 Business Cases have no direct Jira equivalent. During scoping, we design either a custom Business Case issue type in Jira or an Epic with custom fields capturing cost, benefit, and approval status. Custom financial fields in Edison 365 map to typed Jira custom fields (number, currency, date). Approval status from Edison 365 becomes a custom select field in Jira. We document the chosen representation in the schema design deliverable before migration begins.

Edison 365 Resources associate a person with a Project or Portfolio with allocation percentage and date range. Jira's Issue assignee field is single-value. We extract the primary allocation (highest percentage per person per project) and set it as the Jira Issue assignee. Secondary allocations and percentage details migrate as custom fields (e.g., allocation_pct__c and allocation_start__c). Portfolio-level rollup cannot be automatically recalculated in Jira; we note the requirement for manual portfolio-level rollup reporting.

Edison 365 Portfolios aggregate Projects and track KPIs and budget rollups. Jira does not have a native portfolio object at the free or standard tiers. We migrate portfolio metadata as a custom Jira project named with the Portfolio label and document the portfolio hierarchy for the customer's admin to configure through a Jira portfolio app or manual project grouping post-migration. Total cost and benefit rollup fields are preserved as custom fields on the portfolio project metadata issue.

Edison 365 pipeline stage names, ordering, and transition rules export from the workflow configuration and map to Jira Status values and workflow transition rules. Each Edison 365 pipeline maps to a Jira workflow. Stage probabilities migrate to a custom field for reference. We capture the full stage gate sequence so the customer's Jira admin can assign a corresponding workflow to each imported project.

Edison 365 Benefits attach financial or KPI targets to Projects or Business Cases as entity-specific records. We preserve each benefit row as a custom field value on the parent Business Case or Epic issue. Benefit types and names migrate as typed custom fields. Because Edison 365 stores benefits per-entity rather than globally, cross-project benefit rollup requires recalculation in Jira; we flag this as a post-migration reporting task.

Edison 365 custom fields on Ideas, Projects, and Business Cases are enumerated per entity type during discovery and created in Jira as typed custom fields before data import. Edison 365 key-value pairs with type metadata map to Jira field types: text fields, select, multi-select, number, date, and URL. Dropdown and multi-select custom fields in Edison 365 become Jira select and multi-select fields. Custom field options are bulk-created before the first record import.

Edison 365 documents are stored in SharePoint and referenced by URL. We export the full file inventory (URLs, filenames, file types, modified dates, and parent record associations) and offer a parallel file-migration track that transfers files to a designated Jira-connected storage location or Confluence Space. We do not automatically re-link the documents inside Jira; we deliver a mapping table of original SharePoint URLs to destination file locations for the customer's admin to update or we include the re-link step as an add-on scope item.

Edison 365 user records (display name, email, role, department) export in full. We match users by email address to Jira accounts. Inactive Edison 365 users are included but flagged for deactivation review in Jira. Any Edison 365 user without a matching Jira account goes to a reconciliation queue for the customer's admin to provision before record migration proceeds.

Edison 365 workflow transition rules (e.g., which roles can advance a stage, required approvals) do not have a direct Jira workflow equivalent at the rule level. We capture the transition configuration as a written workflow specification document. The customer's Jira admin rebuilds these as Jira workflow conditions, validators, or post-functions using Jira's workflow designer post-migration.