Migrate from Conceptboard to Asana

Each Conceptboard Project becomes an Asana Team (if multi-team governance is needed) or a top-level Project within an existing Asana Team. We extract project name, creation date, and member list during scoping. Starter-tier customers are limited to 5 active projects; archived projects must be accessed separately in Conceptboard's UI. We query the full project list during discovery including archived projects to ensure no boards are missed before migration begins.

Each Conceptboard Board maps to an Asana Project. We export the board via PDF and PNG, extract the board title and any section labels visible in the export, and create an Asana Project with the same name. The PDF and PNG exports are stored as file attachments on the Asana Project description or as pinned attachments for reference. Sections within the board map to Asana Sections in the corresponding project.

Conceptboard Sections subdivide a board and can be exported individually. We create corresponding Asana Sections within the target Project, preserving the section outline hierarchy when visible in the export. Section-level per-export captures are stored as section-level PDF attachments in the corresponding Asana Section.

Canvas elements do not have a structured export path. We parse the PDF export for text content and approximate layout positions, then create individual Asana Tasks representing each sticky note or text block cluster. The task name carries the extracted text. Sticky notes that were spatially grouped are sometimes represented as subtasks under a parent task representing the group. This is lossy by necessity: connectors, arrows, and spatial relationships are not structurally preserved.

Conceptboard Tasks (milestones, deadlines, and assignees within boards) map to Asana Tasks. We extract task name, due date, assignee (by email lookup), and any subtask structure from the board export and create matching Asana Tasks with the same due date and assignee. Custom fields on Conceptboard tasks require manual field mapping during scoping.

Conceptboard file attachments are downloaded individually from the Attachments dialog and re-attached to the equivalent Asana Project or Task. We preserve original filenames and upload them via the Asana API with the appropriate workspace and target gid. Asana API enforces a 100 MB per-file attachment limit; files exceeding this threshold are flagged for manual handling.

Conceptboard licensed users are mapped to Asana Users by email address. We separate licensed users (per-seat billing) from guest accounts (free in Conceptboard). Guest users without Conceptboard accounts are invited to the Asana workspace as Guests or Members depending on their intended role. User mapping is validated before record migration to avoid orphaned assignments.

Conceptboard personal and team templates are exported as boards and migrated as Asana Projects. Template organisation (personal vs team-shared) is preserved in Asana as private vs team projects. If the customer uses Advanced tier template features, we note template groupings for the customer to rebuild as Asana project templates manually.

Board history (Advanced+ feature) tracks version snapshots of board changes over time. This is an audit artifact with no structurally equivalent schema in Asana's activity log. We do not migrate version history. We document whether boards had active history so the customer understands what governance capability is not preserved.

Approval workflows (Corporate and Government tier) represent process state rather than content data. There is no Asana equivalent for board-level approval workflows. We flag whether any boards had active approval states at migration time and document the review cycle for the customer's admin to re-implement manually in Asana if required.

Audit logs are a Corporate and Government tier feature recording administrative actions. These are not user content and are not migratable. We note their presence as a data governance indicator and recommend the customer exports audit logs from Conceptboard before decommissioning.

Conceptboard comments on board elements are captured in the board-level PDF export but are not available as structured data. We note the comment count per board as a quality indicator and, where comments were exported as visible text in the PDF, add them as Asana Task comments on the corresponding reconstructed task. This is lossy: author attribution and thread context are not preserved.