Migrate from MIndGenius Online to monday Work Management

MIndGenius Online Projects map directly to monday.com Boards. Each project carries its name, description, settings, and member list. We create the board in monday.com first so that board ID is available for resolving item and group references during the branch migration phase. Projects without any Mind Map branches are created as empty boards with just the project metadata.

Each MindGenius Online branch becomes a monday.com Item. The branch label maps to the item name. Branch colour coding is preserved in a custom Status column or text column. Child branches become subitems of the parent item, maintaining the hierarchical tree structure as a monday.com parent-subitem hierarchy. Root branches map to top-level items within a default Group in the destination board.

MIndGenius Online Map Properties (branch-level metadata like custom properties, dates, assignees) are mapped to monday.com item column values. We create typed custom columns on the destination board before migration: date properties become Date columns, assignee references become Person columns, and text properties become Text or Number columns. Branch-level properties without a visible custom fields UI in MIndGenius Online are captured as text metadata and mapped to a Long Text column in monday.com.

MIndGenius Online Taskboard cards (which are derived from map branches) carry Status, Assignees, Due Date, Priority, and Description. We map Status to a monday.com Status column, Assignees to a Person column, Due Date to a Date column, and Description to the item Description column. Taskboard card layout, swimlanes, and card colour formatting do not transfer 1:1; we document these as post-migration manual steps for the customer's admin.

MIndGenius Online Timeline entries surface start date, end date, duration, and dependency relationships. We map start date and end date to monday.com Date columns, or to a Timeline column if the board plan supports it. Gantt dependency links are reconstructed using monday.com's Dependency column type, which creates predecessor-successor relationships between items. Milestone markers from the Timeline view become items with a milestone indicator (checkbox or Status label) rather than a native milestone object, as monday.com does not expose a Gantt milestone as a distinct object type.

MIndGenius Online Guest accounts grant free external access to one shared project per guest. We identify all Guest accounts during scoping and reassign ownership of any project content they own to full (paid) user accounts so that project history is preserved under a permanent owner. monday.com guest access (Standard and above) uses a different permission model; we document which guests should receive board-level view or edit access post-migration.

MIndGenius Online Hub Dashboards aggregate KPIs and visual summaries across multiple projects. monday.com Dashboards aggregate widgets across boards but use a different widget model. We capture dashboard configuration (widget types, layout, included projects) as a written specification document that the customer's admin uses to rebuild equivalent dashboards in monday.com. We do not migrate dashboard configurations as code because the widget model is not directly portable.

MIndGenius Online does not expose a visible custom fields UI, so custom branch-level properties are captured as text metadata during export. We create matching typed columns in monday.com before migration and populate them from the extracted metadata. Any branch property that cannot be typed from the export data defaults to a Text column. The customer validates column types and converts to appropriate types (dropdown, number, formula) post-migration.

MIndGenius Online branch comments are stored as blob references not fully serialised in standard export formats. We do not migrate comments because the intermediary export path cannot reliably extract the comment text and associate it with the correct branch. We document this data loss during scoping so the customer can decide whether to export comments separately before migration begins. monday.com item updates can be manually recreated post-migration if needed.

MIndGenius Online file attachments on branches are stored as blob references not fully serialised in standard export formats. We do not migrate attachments as a standard migration step. We flag attachments that can be extracted from PDF exports and document their location so the customer's admin can re-attach them manually in monday.com. monday.com file attachments are supported natively on items after migration.

MIndGenius Online Hub groups multiple projects under a single dashboard view. monday.com Workspaces serve a similar grouping function, containing multiple boards with workspace-level settings and member management. We map each Hub to a monday.com Workspace and include all contained Projects as boards within that Workspace. Workspace-level settings (billing, member roles, integrations) are documented for manual configuration post-migration.

MIndGenius Online does not include a native automation builder, so there are no MIndGenius Online automations to migrate. monday.com automations are not migrated as code. We deliver a written inventory of every monday.com automation currently configured (if any were set up before scoping) with its trigger, conditions, and actions for the customer's admin to review. The monday.com automation infrastructure transitioned to a new builder with an April 30, 2026 sunset date for legacy automation creation, which is documented in the FAQ section.