Migrate from MindGenius to Asana

MindGenius Projects (containers holding maps, taskboards, and timelines) map 1:1 to Asana Projects. Project name and description migrate directly. Created date and owner email migrate as custom fields on the Asana project for audit traceability. We create Asana team membership during migration scoping so the project is accessible to the right team immediately after import.

Each MindGenius Mind Map is exported as an MS Project XML file representing the full branch tree. We parse the XML to extract the root node (map title) and all child branches as a flat task list with parentId references. We then split the map into an Asana Project where top-level branches become Sections and second-level branches become Tasks. Deep branches (level 3+) become subtasks nested under their parent task. The original branch order from the mind map is preserved as the task sort order in Asana.

MindGenius root-level branches (the primary topic nodes of the mind map) have no parent in the mind map tree. We map these to Asana Sections at the project level. Section names preserve the original branch label. Branch colour, priority flag, and notes are stored as custom fields on the section for future reference by the customer's admin.

MindGenius child branches with a parent branch map 1:1 to Asana Tasks. Branch label becomes task name. Branch notes migrate as task description (rich text). Start date and due date on the branch migrate as the task start_date and due_date. Priority flag (High/Medium/Low) maps to Asana Custom Field (enum). Assignee resolves by email match against the destination Asana workspace members list.

MindGenius branches nested more than two levels deep are difficult to represent in Asana's single-level subtask model. We promote level-3 nodes as subtasks under their level-2 parent task. Level-4 and deeper nodes are flattened as additional subtasks of the level-3 parent. The original nesting depth is preserved as a custom field original_depth__c on each subtask for customers who want to reconstruct the hierarchy in a reporting tool.

MindGenius Taskboard converts map branches into Kanban-style task cards with status, assignee, and due date. Each task card maps 1:1 to an Asana Task. Status (Not Started, In Progress, Complete) maps to task completed field. Assignee and due date transfer directly. If the Taskboard has a status column not represented in the original map export, we create a custom field taskboard_status__c and populate it during import.

MindGenius Timeline items with a duration (start date and due date) map to Asana Tasks with start_date and due_date. Zero-duration markers (MindGenius milestones) map to Asana Milestones. Milestone name preserves the MindGenius milestone label. We configure the Asana project to include milestone tracking during migration scoping if any milestones are detected in the source export. Milestone completion status maps from the MindGenius milestone state.

MindGenius custom fields on branches (text, number, date, dropdown) map to Asana Custom Fields of equivalent type. Enum/dropdown custom fields in MindGenius map to Asana enum Custom Fields with the same choice values. We pre-create all destination custom fields before record import using the Asana Custom Fields API, and then associate them with the relevant projects. Custom field values migrate as key-value pairs on the corresponding Asana task.

MindGenius branch attachments (PDFs, images, Office files) are not included in standard MS Project XML, OPML, or CSV exports. We generate a manifest of every attachment reference encountered in the export (file name, original path, size, associated branch/task label) and provide this as a CSV to the customer. The customer re-uploads attachments manually in Asana or provides an alternative upload pipeline. We do not attempt automated binary extraction from the MindGenius web UI.

MindGenius branch assignees are referenced by display name or email. We extract all unique assignees from the export, match by email against the Asana workspace member list, and assign the Asana User as task assignee during import. Any MindGenius assignee without a matching Asana user is flagged in the reconciliation report and held in a queue for the customer's admin to provision before record import resumes.

MindGenius Subscription tier includes Guest Access with read-only or limited permissions on a project. We export guest email and permission level. Permissions do not map cleanly to Asana's permission model. We add guest emails as Asana Guest users to the relevant workspace and assign them to the migrated projects. The customer's Asana admin reviews and adjusts guest permissions post-migration.

MindGenius branch colours and icons are visual metadata used to categorise or prioritise branches in the map view. Asana has no native branch-colour concept. We store the original branch colour (hex value) and icon name as custom fields on each task (branch_colour__c and branch_icon__c) so that the customer's admin can reference them for reconstruction in Asana's custom fields UI or a third-party integration.