Migrate from MIndGenius Online to Jira

MindGenius Online Projects map to Jira Projects as the root container. We extract the project name, description, and creation timestamp. Jira project type (company-managed or team-managed) is chosen during scoping; company-managed is the default and supports the widest workflow and issue type configuration. The Jira project key (e.g. PROJ) is generated from the MindGenius project name.

MindGenius mind map branches are a hierarchical tree with unlimited depth. We flatten the tree into Jira's three-level issue hierarchy: top-level branches become Jira Epics, second-level branches become Stories or Tasks depending on whether they have children, and leaf-level branches become Subtasks. Branches exceeding four levels are collapsed into the nearest Jira-compatible level with child branches re-parented. Branch labels, colours, and map properties migrate as Jira custom fields (mg_branch_label__c, mg_branch_colour__c) for reference.

MindGenius Taskboard cards carry title, description, status (To Do, In Progress, Done), assignee, due date, and priority. These map directly to Jira Issue fields: Summary, Description, Status, Assignee, Due Date, and Priority (Highest, High, Medium, Low). Taskboard swimlane groupings do not have a Jira equivalent and are dropped; we document the grouping as a Jira label or component so the customer can manually reassign if needed.

MindGenius Timeline entries with start date, end date, and duration map to Jira Issues with the same start and target dates preserved as custom date fields (mg_start_date__c, mg_target_date__c). Milestone markers become Jira Milestones (if the Jira Product Discovery or Advanced Roadmaps add-on is present) or Jira Issues flagged with a Milestone label. Gantt dependency arrows (Finish-to-Start, Start-to-Start) become Jira Issue Links (Blocks / Is blocked by). Jira Sprints are created to cover the Timeline date range.

MindGenius milestones are date-bound markers on the Timeline. In Jira without Advanced Roadmaps, milestones are not a native concept. We represent them as Jira Issues with zero story points, a Milestone label, and the target date migrated as a custom date field. If the destination Jira includes Advanced Roadmaps, we create native Milestone records and link the relevant issues. The milestone name and colour migrate as custom fields.

MindGenius Timeline dependencies (Finish-to-Start arrows) between tasks become Jira Issue Links of type Blocks or Is Blocked by. We resolve the destination issue key at migration time by matching the dependent task name to the newly created Jira Issue summary. Circular dependency chains are flagged and escalated during scoping since Jira does not natively support circular issue links.

MindGenius Hub Dashboards aggregate KPIs across projects. Jira Dashboards are configurable gadget-based dashboards. We map KPI widgets to Jira gadget equivalents (Created vs Resolved chart, Pie Chart by Status, Sprint Burndown if Sprints exist). Dashboard layout mapping is approximate; Jira's gadget grid does not replicate MindGenius card-widget layouts exactly.

MindGenius Guest access grants free external users view access to a single shared project. Jira's free tier includes up to 10 users; external stakeholders map to Jira users with Viewer or Member roles. We extract the guest email list from MindGenius and provision corresponding Jira user invitations during migration.

MindGenius branch-level custom properties (text fields, date fields, numeric fields) migrate to Jira custom fields on Issue. Field type mapping: MindGenius text to Jira Text Field, date to Jira Date Picker, number to Jira Number Field. Custom fields that have no Jira equivalent in the current plan tier are documented for the customer's admin to add post-migration.

MindGenius branch comments are stored as inline text associated with map branches. We extract comment content and author timestamps from MindGenius exports and map them to Jira Issue Comments on the corresponding Jira Issue. Comment thread nesting is flattened to Jira's flat comment structure. Attachments on comments are not preserved in standard MindGenius exports; we warn customers and recommend re-attaching any critical files post-migration.