Migrate from MIndGenius Online to Trello

Each MIndGenius Online Project becomes a Trello Board. Project name becomes Board name, and project-level settings (sharing, visibility) map to Trello Board visibility (Public, Workspace, Private). If the source account is freemium, only one project can exist — we flag this during scoping and confirm with the customer that all intended Projects are in scope before migration begins, so no paid-tier Projects are missed.

MIndGenius Online Mind Maps are hierarchical trees of branches. We flatten each Mind Map into a Trello Board structure: top-level branches become Lists, and each nested sub-branch becomes a Card under the corresponding List. Branch labels, colours, and the map-level Map Properties migrate as Card names, Card cover colours, and List names. The hierarchical parent-child relationships between branches are not preserved as nested structure in Trello (standard Trello does not support card-in-card nesting) — we document the hierarchy in a Card description or label so the relationship is visible in Card detail.

MIndGenius Online Taskboard cards (derived from map branches) carry status, assignees, start date, due date, and priority. These map directly to Trello Cards with status becoming the List the card lives in, assignee mapping to Trello member assignment, start date preserved as a custom date field (or Card description entry), due date mapped to Card due date, and priority mapped to a Card label, a Custom Field, or Card description depending on the customer's chosen Trello tier. Card colours from the Taskboard map to Card cover colours.

MIndGenius Online Timeline phases and tasks carry start date, end date, milestone flags, and dependency links. We map the start date to a Card start date (Custom Field or description) and the end date to the Card due date. Milestone markers from the Timeline do not have a native Trello equivalent — we convert them to a milestone Card label or a flag in the Card description so the customer can identify them. Dependencies (finish-to-start links) are noted in Card description or label; Trello does not enforce dependency chains natively. Timeline views in Trello (Premium and Enterprise Power-Up) can then be configured to visualise the card due dates as a Gantt-style chart.

MIndGenius Online multi-project Dashboards aggregate KPI widgets and visual summaries across the Hub. Trello does not have a native dashboard feature. We do not migrate Dashboard configurations as they cannot be represented in Trello. We deliver a written inventory of every Dashboard widget (widget type, included Projects, data source) so the customer's admin can decide whether to rebuild using a Trello Power-Up, a connected reporting tool, or a spreadsheet.

MIndGenius Online Guest accounts provide free read or edit access to one shared project per external user. Trello has no Guest role — all collaborators are full members of a Board. We identify all Guest-owned cards and tasks during scoping, reassign them to a designated full MIndGenius Online member (or a named Trello member account provided by the customer), and document the reassignment so Guest contributions are preserved under a traceable account after migration.

MIndGenius Online branch comments are stored as blob references not fully serialised in standard export formats. We do not migrate branch comments directly because the intermediary export path does not preserve comment text reliably. We warn customers during scoping and offer two options: (1) export branch comments to a separate CSV for manual re-entry in Trello Card descriptions, or (2) add comments as checklist items within each Card if the comment count is low. The chosen approach is confirmed before migration begins.

MIndGenius Online file attachments on map branches are stored as blob references that are not fully serialised in standard export formats. We do not migrate file attachments because the intermediary export path does not extract the binary files reliably. We flag every branch with attachments during scoping and provide the customer with a list of attachment filenames and their source branch locations so that the customer's team can manually re-upload the files to the corresponding Trello Cards post-migration.

MIndGenius Online does not expose a visible custom field UI — branch-level properties and metadata are captured internally. We map any captured custom properties to Trello Custom Fields (available on Standard, Premium, and Enterprise tiers) or to Card labels if the customer is on the free Trello tier. We flag which fields cannot be represented in Trello without a paid tier upgrade and confirm the customer's preferred approach during scoping.

MIndGenius Online branch colours encode category, priority, or status in the Mind Map view. We map branch colours to Trello Card cover colours, preserving the visual encoding as Card covers. If the customer uses colour to represent something Trello handles with Labels (e.g., priority), we map colour to the corresponding Label as well. Cards without a colour encoding in MIndGenius Online receive no cover in Trello.

Each MIndGenius Online Mind Map carries Map Properties (map name, description, owner, created date, modified date). We extract the map name as the Board name and the map description as the Board description. Created and modified timestamps are preserved in the Board description as metadata. Map Explorer state (collapsible branch tree) has no Trello equivalent and is not migrated.

The MIndGenius Online Hub Taskboard aggregates cards across all Mind Maps within a Project. We decompose the Hub Taskboard into the constituent Boards (one per Mind Map) with their Cards placed in the correct Lists based on the card's original Taskboard status column. Card ordering within each List is preserved by the API insertion order during migration. Hub-level aggregation across multiple Mind Maps is handled by the customer using Trello Power-Ups or a separate reporting tool post-migration.