Migrate from MindGenius to Trello

Each MindGenius Project maps to a Trello Board, or multiple Boards if the project contains distinct Mind Maps that function as separate workstreams. We create one Board per MindGenius Project by default and use the project name as the Board title. If the project contains more than one Mind Map with a distinct purpose, we split them into separate Boards linked by a naming convention (Project Name - Map Name). Project description migrates as the Board description. Workspace creation is optional and depends on whether the Trello destination org uses Workspace-level nesting.

A MindGenius Mind Map is the root object containing the branch hierarchy. We map each Mind Map to a Trello Board, using the map name as the Board title and preserving the map's creation date and owner. We extract visual metadata (branch colours, priority icons, node icons) as properties on the exported node JSON so they can be applied as Trello Labels during card creation. Board background colour is set to match the MindGenius map's primary branch colour where applicable.

MindGenius branches at levels 1 and 2 (top-level and second-level nodes) map directly to Trello Cards on the destination Board. The branch label becomes the Card title. Rich text in the branch note field becomes the Card description. Priority flags (High/Med/Low) and branch colours map to Trello Labels using a colour-matching table we build during scoping (e.g., MindGenius red = Trello red label). Start date and due date on the branch become Card start date and due date via the Card dueDate and start fields. Assignee resolves by email match against Trello Board members.

MindGenius branches at level 3 and deeper exceed Trello's two-level card nesting model. We convert these into Checklist items on the parent Card, preserving the branch label as the checklist text and the branch dates as checklist item due dates where the Trello Power-Up supports them. For branches with rich notes or sub-branches beyond level 4, we create a child Card linked via a Trello card link (Manual Card Linking Power-Up) or add a text note in the parent Card description referencing the sub-hierarchy. This is the primary hierarchy-flattening resolution strategy and is reviewed with the customer during scoping.

MindGenius Taskboard tasks are Kanban-style task cards with status, assignee, and due date. Each Taskboard task maps to a Trello Card. The MindGenius status column (To Do, In Progress, Done) maps to Trello Lists, which we create on the Board to match the Taskboard columns. Task assignee migrates to Card member by email match. Task due date migrates to Card due date. Task priority becomes a Label on the Card.

MindGenius Timeline items and milestones are exported as tasks with start_date, due_date, and a milestone flag. Milestones (zero-duration) become Cards with a due date set to the milestone date and the Card name prefixed with [Milestone]. Non-milestone Timeline items with a date range become Cards with the end date as the Card due date. Trello has no native Gantt display — if the customer holds a Premium Trello tier, we configure the Timeline Power-Up post-migration so that Cards with due dates render on a Gantt-style timeline. The milestone flag is stored as a custom Card label (Milestone).

MindGenius branch attachments (PDFs, images, Office documents) are not included in standard file exports (MS Project XML, OPML, CSV). We generate a manifest of every attachment reference — file name, original branch path, file size — during the pre-migration audit. This manifest is delivered to the customer with instructions for manual re-upload to the corresponding Trello Card. We do not attempt to extract binary attachment data from the MindGenius web UI without an authenticated session. If the customer uses MindGenius Online (cloud) and provides API credentials, we evaluate whether a custom export pipeline can retrieve attachments; otherwise the manifest is the deliverable.

MindGenius assignees are referenced by display name and email on branches and tasks. We extract every distinct assignee across all exported objects and attempt email-based matching against the Trello destination Board members. Board members must be added to the Trello Board before migration so that the Card member assignment can resolve at import time. Any MindGenius assignee without a matching Trello member is held in a reconciliation list for the customer admin to provision or reassign before the final import phase.

MindGenius custom fields on branches (key-value properties beyond standard fields) are exported as JSON properties on the node object. If the destination Trello workspace is on the Free or Standard tier, custom fields become Card Labels with a naming convention (CF: Field Name = Value). If the customer holds Trello Premium, we configure Card Custom Fields as typed fields (text, number, date, dropdown) and populate them during import. The field-type selection is made during scoping based on the destination Trello plan.

MindGenius Subscription tier includes Guest Access with read-only or limited permissions. Trello Free and Standard tiers have no true read-only observer role — all Board members can create and edit Cards. If the destination is Trello Premium or Enterprise, we assign MindGenius guests as Observers on the Trello Board for read-only access. If the destination is Free or Standard, guest permissions do not map cleanly; we flag them in the scope document and recommend that the customer manually configure Board-level permissions post-migration.

MindGenius branch colours (red, orange, yellow, green, blue, purple, grey) map directly to Trello Label colours using a colour-matching table. MindGenius priority icons (flag, star, exclamation) map to Label names (Priority: High, Priority: Medium, Priority: Low). This mapping preserves the visual prioritisation layer that MindGenius users rely on. The label taxonomy is created as a pre-migration step in the Trello Board settings.

Trello Lists represent workflow stages (e.g., Backlog, In Progress, Review, Done) and have no direct MindGenius equivalent unless the customer has used the Taskboard view. We create default Lists (To Do, In Progress, Done) on each migrated Board unless the customer has a specific List naming convention they want applied. List configuration is confirmed during scoping. Lists do not migrate from MindGenius — this is a destination-side configuration step performed by FlitStack AI before card import begins.