Migrate from MindGenius to Microsoft Project

Each MindGenius Mind Map maps to one Microsoft Project file or Project Online project. The Mind Map name becomes the MS Project project name; the project start date is set from the Mind Map's Timeline start if available, or from the earliest branch date. We use the MindGenius MS Project export as the primary import mechanism, supplemented by OPML parsing for maps where the export loses branch colour or custom field data.

The MindGenius root node of each map maps to the MS Project Summary Task at Outline level 1. The branch label becomes the task name; any branch notes become the task notes. Visual metadata (branch colour, icon) is preserved as a custom text field on the task since MS Project custom fields are the only available metadata channel beyond standard task fields.

MindGenius branch children map to MS Project tasks with Outline level reflecting their depth in the tree. We traverse the branch hierarchy recursively and assign Outline level = branch depth. Branch labels map to Task Name; branch dates (start/due) map to Start and Finish fields; branch priority markers map to a Priority custom field (1-500 numeric scale in MS Project). Deep hierarchies (over 10 outline levels) may display awkwardly in MS Project; we chunk very deep maps into separate sub-projects linked by summary task names during scoping.

MindGenius Taskboard task cards (Kanban-style) export as individual tasks. The Taskboard status (e.g. Not Started, In Progress, Done) maps to the MS Project Task Status field (Complete, In Progress, Not Started) and is reflected in the % Complete field. Assignee, due date, and priority from the Taskboard card migrate directly to the MS Project task resource assignment, Finish date, and Priority custom field respectively.

MindGenius Timeline view bars (branches with date ranges) map to MS Project tasks with Start and Finish fields preserved from the MindGenius date range. Duration is computed as Finish minus Start in working days. The Timeline bar colour and icon are stored as custom text fields on the MS Project task since no native visual property exists in MS Project at the task level.

MindGenius milestones (zero-duration markers in the Timeline view) map to MS Project Milestone tasks with Duration set to 0 days. The milestone name maps to Task Name; the milestone date maps to both Start and Finish. In MS Project desktop, milestones are marked with the Milestone flag (diamond shape) automatically by setting Duration to 0.

A MindGenius Project holding multiple maps, Taskboards, and Timelines maps to an MS Project file or Project Online project container. Project-level metadata (name, description, created date, owner) becomes the project-level properties in MS Project. If multiple Mind Maps exist within one MindGenius Project, each Mind Map becomes a separate sub-project or a separate MS Project file, determined during scoping based on the customer's preference.

MindGenius branch and Taskboard assignees are referenced by display name or email. We map each distinct assignee to an MS Project Resource record with the name and email preserved in the Resource Name and Email Address fields. Resource type defaults to Material unless the assignee represents a named person in which case it is set to Work. Resource cost rates do not exist in MindGenius and are left blank or populated from the customer's input during scoping.

Each MindGenius branch assignee creates an MS Project Assignment record linking the task to the Resource. Assignment units default to 100% unless MindGenius has a partial allocation indicator. Work hours are derived from the task duration and the resource standard rate if provided.

MindGenius custom fields on branches (e.g. custom dropdown, number, text) map to MS Project custom fields on tasks. We create the equivalent custom field in MS Project using the custom field definition dialog (Project > Custom Fields). Text-based MindGenius custom fields map to Text custom fields; numeric fields map to Number custom fields; date fields map to Date custom fields. Flag and currency custom fields are handled similarly. Custom fields on tasks are supported in MS Project desktop from 2016 onward and in Project Online at all tiers.

MindGenius branch attachments (PDFs, images, Office files) are not included in any standard export format. We generate a structured manifest listing each attachment: file name, original MindGenius branch path, and file type. The customer re-uploads these to SharePoint or a local directory and re-links them to the corresponding MS Project task manually or via a documented Power Automate flow. We do not scrape binary attachment data from the MindGenius web UI.

MindGenius Subscription-tier guest collaborators (read-only or limited permissions) have no MS Project equivalent. We export the guest email address and permission level as a text list and provide it to the customer's admin, who decides whether to provision the guest as a SharePoint viewer or Project Online viewer after migration.