Migrate from MIndGenius Online to Microsoft Project

Each MIndGenius Online Project maps to a single Microsoft Project .mpp file. We map the project name, project start date, project finish date (calculated from the latest Timeline end date), and project calendar. Multi-project portfolios in MIndGenius Online produce multiple .mpp files, which we group under a shared folder structure. Project-level custom properties (project status, client name, project code) migrate as custom fields in the destination project if Project Standard or Professional is the target, or as columns in a supplemental CSV if the destination is Project Plan 3 cloud.

MIndGenius Online Mind Map branches form a hierarchical tree. We decompose each branch level into Microsoft Project Summary Tasks (top-level branches) and sub-tasks (nested branches), preserving the branch label as the task name and the visual indentation level as the WBS hierarchy depth. Branch-level properties (priority flag, colour tag, assignee) migrate as task fields. The Mind Map layout (radial, left-to-right, top-down) has no Microsoft Project equivalent and is not preserved; the WBS outline is the destination structure.

MIndGenius Online Taskboard cards derived from map branches carry a card name, status (To Do, In Progress, Done), assignee, due date, and optional description. We map card name to Microsoft Project Task Name, due date to Finish, assignee to Resource Names (resolving against a resource pool we create during migration), status to Percent Complete (Done = 100%, In Progress = 1-99% by elapsed time, To Do = 0%), and description to Notes. Card colour-coding and swimlane position do not transfer.

MIndGenius Online Timeline entries contain task name, start date, end date, and optional dependency arrows. We map these directly to Microsoft Project Task Start and Finish fields. Dependency arrows in the MIndGenius Timeline map to Microsoft Project Finish-to-Start predecessor links. Any named dependency type (FF, SS, SF) stored in the Timeline migrates as the named predecessor type; unnamed links default to FS. Lag time stored as a date offset in MIndGenius migrates as a predecessor link with a Days-lag value in Microsoft Project.

MIndGenius Online milestone markers are coloured endpoints on the Timeline view, not always stored as explicit record fields. We identify milestones by detecting tasks with zero duration and a milestone colour flag in the Timeline export data, then reconstruct them as Microsoft Project milestone tasks (Duration = 0, Milestone = Yes checkbox). Milestone naming and date migrate. Milestone colour-coding does not transfer.

MIndGenius Online does not have a named resource pool; assignees are stored as name strings on Taskboard cards and Timeline entries. We extract every distinct assignee name during scoping, deduplicate the list, and build a Microsoft Project Resource Sheet with each name as a Material or Work resource. Resource type (Material vs Work) is determined by the customer during scoping based on whether the assignee is a person or a consumable. Resource calendars and unit percentages are not present in MIndGenius Online and default to 100% allocation in Microsoft Project.

MIndGenius Online stores Finish-to-Start dependency links as visual arrows between Timeline bars. We extract every dependency pair from the Timeline export (source task and target task), resolve both tasks in the destination Microsoft Project outline by name and date range, and write the predecessor as a named predecessor link with FS type. Self-referencing or circular dependencies detected in MIndGenius Online are flagged and resolved with the customer before migration to avoid Microsoft Project scheduling conflicts.

MIndGenius Online stores branch comments as inline text attached to Mind Map nodes. These comments are not fully serialised in the standard MS Project export path; they may appear as truncated text in the Notes field for the corresponding task, but formatting, threading, and comment timestamps are not preserved. We warn customers during scoping and offer a PDF export of the Mind Map as a reference document that captures branch comment text alongside the visual layout.

File attachments on MIndGenius Online Taskboard cards and map branches are stored as blob references not accessible through the standard export pipeline. We do not migrate file attachments to Microsoft Project because the .mpp file format does not support inline file attachments and the intermediary export formats strip blob references. We provide a written inventory of every attachment by card and branch name, with a file path reference, so the customer's project manager can re-attach files manually in Microsoft Project after migration.

MIndGenius Online Dashboards aggregate KPIs and visual summaries across multiple projects in the Hub. Microsoft Project (Standard, Professional, Plan 3) does not have a multi-project dashboard feature; Project Online or Power BI is required for portfolio-level dashboarding. We deliver a written inventory of every MIndGenius Dashboard widget (widget type, included projects, KPI definition, refresh cadence) so the customer's PMO can rebuild the dashboard in Power BI or Microsoft Project Online if that platform is in scope.

MIndGenius Online Guest Users are external collaborators with read or comment access to a single shared project. Microsoft Project does not have a Guest access model. We map the Guest User list to a project stakeholder list in the migration output (as a CSV) so the customer's project manager can re-invite stakeholders via their chosen method (email distribution, SharePoint, or Microsoft Teams) after the .mpp file is published.