Migrate from MIndGenius Online to Asana

MIndGenius Online Projects map directly to Asana Projects. Each project's name, description, status (active/archived), and creation date migrate as Project name, Notes, and Created_at. We map the project's default Hub Taskboard view by creating an Asana Board view within the migrated Project so teams retain the Kanban orientation on first load.

The central mind-map hierarchy (root branch and all child branches) maps to an Asana Project with a nested task structure. The root branch becomes the project name; top-level child branches become top-level tasks; second-level branches become subtasks, and so on. Branch labels, colours, and map properties are preserved as task names and in custom fields branch_colour__c and branch_depth__c for reconstruction reference. The visual layout (radial arrangement, spatial positioning) does not transfer because Asana uses list ordering rather than spatial placement.

MIndGenius Online Taskboard columns (default columns: To Do, In Progress, Review, Done) map to Asana sections within a Project. The Board view in Asana uses these sections as swimlanes. We transfer column card counts and column names. Card position within a column is preserved as task ordering within the Asana section. Card colours and swimlane groupings do not transfer 1:1 and are documented for manual reapportionment.

MIndGenius Online Taskboard cards (derived from map branches with assignees, status, due dates, and start dates) map to Asana Tasks. Card title maps to Task name, assignee maps to Asana assignee, due date maps to Due date, and the source branch status maps to the corresponding Asana section. Card labels and priority flags migrate as Asana custom fields card_label__c and card_priority__c. Subtasks on cards map to Asana subtasks.

MIndGenius Online Timeline entries carry start date, end date, duration, and dependency links between entries. We map these to Asana Tasks with Start date and Due date fields set from the Timeline entry. Gantt dependency arrows between entries translate to Asana Finish-to-Start dependency links (the default dependency type). Milestone markers in the Timeline map to Asana milestone tasks with zero duration. Gantt colour-coding and resource fields are not preserved and are flagged in the migration report for manual reapplication.

MindGenius Online stores branch parent-child relationships as hierarchical tree data. We represent these relationships in Asana either as subtasks (one-to-one child mapping) or as section nesting within the project, depending on the customer's preference during scoping. Deep hierarchies (more than four levels of branch nesting) are flattened to four Asana levels with a custom field original_depth__c recording the source depth for audit.

MIndGenius Online multi-project Dashboards aggregate KPIs and visual summaries across the Hub. We map the dashboard widget types, layout positions, and project inclusion list. Asana Dashboards and Portfolios are rebuilt manually post-migration because they involve configuration choices (widget types, chart styles, portfolio grouping) that are platform-specific. We deliver a written dashboard inventory documenting every widget's source configuration so the customer's admin can rebuild them in Asana.

MIndGenius Online Guest accounts grant free external access to one shared project per guest. We identify Guest accounts during scoping and flag them for the customer's admin to re-invite as Asana Guest members from the Asana Starter tier ($10.99/user). Guest role and permission scoping on MIndGenius Online does not map directly to Asana Guest permissions, which are more constrained. We document the permission gap in the migration report.

MIndGenius Online stores branch-level properties and map metadata as structured fields without a dedicated custom fields UI. We capture all non-system properties and map them to Asana custom fields of equivalent type (text, number, date, enum). Dropdown values on MIndGenius Online branch properties become Asana enum custom field options. Free-text branch properties become Asana text custom fields. The migration requires pre-creation of the custom field schema in the Asana destination workspace before import.

MIndGenius Online stores branch comments as blob references that are not fully serialised in standard export formats (Word, Excel, PDF, MS Project). We do not migrate Comments because the intermediary export path strips comment content. We document every comment's source branch location in the migration report so the customer's admin can manually re-enter critical comments post-migration or extract them from a MIndGenius Online PDF export before the account is closed.

MIndGenius Online file attachments on map branches are stored as blob references not serialised in standard exports. We do not migrate attachments. We provide a written inventory of every attachment with its source branch location and file type so the customer's admin can re-upload directly to the migrated Asana task. We advise customers to download attachments from MIndGenius Online before account closure.

Map-level properties in MIndGenius Online (Map Explorer state, map properties, branch creation timestamps, branch creator) are captured as custom fields on the migrated Asana Task. Creation timestamps and creator email address migrate as task-level custom fields created_date__c and created_by__c. Map Explorer state (filter and view settings) is not transferable and is noted in the migration report for manual reconfiguration.