Migrate from Conceptboard to monday Work Management

Conceptboard Projects are top-level containers that group Boards and enforce active-project limits on Starter tier (capped at 5 active). We map Projects to monday.com Workspaces at the account level, or to top-level monday.com Boards if the customer prefers a flatter structure. Project metadata (name, creation date, member list) migrates as Workspace or Board metadata. During scoping we query the customer's full project list including archived projects since Starter tier archives projects automatically beyond the 5-project limit.

Conceptboard Boards are the primary workspace and map to monday.com Boards. Because Conceptboard has no API, we export each Board via the Export Board feature to PDF and PNG, then reconstruct it in monday.com as a Board with Groups (mapped from Sections) and Items (extracted from task and milestone content). The visual layout of sticky notes, shapes, connectors, and comments cannot map to monday.com's item-column structure — we treat these as manual rebuild candidates documented in the migration handoff.

Conceptboard Sections subdivide a Board and can be exported individually. Sections map directly to monday.com Groups on the equivalent Board. Section-level ordering (the sequence of sections within a board) migrates as Group position in monday.com. Section-level permissions or access settings that exist on Advanced+ Conceptboard tiers require manual configuration in monday.com Board settings post-migration.

Conceptboard Tasks and Milestones created within boards map to monday.com Items. Task properties (name, description, assignee, due date, status) map to monday.com column types (Name, Description, Person, Date, Status). Milestones with specific due dates map to Items with a Date column set; teams that need Gantt-style dependency views use monday.com's Timeline column which requires Pro tier. We extract task content from the board export and recreate it as structured item records via monday.com's GraphQL API.

Conceptboard Milestones map to monday.com Items with a Date column set to the milestone date. If the customer uses Conceptboard's dependency feature to link milestones, we document the dependency pairs during scoping so the customer can rebuild them using monday.com's Pro-tier dependency column post-migration.

Conceptboard file attachments (accessible via the Attachments dialog on each board) are downloaded individually and re-uploaded to monday.com Boards as Files attached to the relevant Item. Filenames and folder structure are preserved. Large files or high-volume attachment sets may require chunking to stay within monday.com API rate limits and individual file size constraints.

Conceptboard templates (personal pre-built library on Starter; team templates on Advanced+) are recreated in monday.com as Board templates. We extract the template board content via export, create an equivalent monday.com Board, and save it as a monday.com template using the account's template library. The customer can then instantiate templates for new project launches.

Conceptboard licensed users map to monday.com User accounts. We resolve Conceptboard users by email match against monday.com User records. Any Conceptboard user without a matching monday.com account goes into a reconciliation queue for the customer's admin to provision before record migration resumes. Guest users (unregistered collaborators on Conceptboard who do not consume paid seats) are handled separately — they require monday.com seats and are flagged during scoping.

Conceptboard Guest accounts are free and do not consume paid seats. In monday.com, every active user requires a seat regardless of role. We separate licensed users from guest users during scoping so the customer can provision the correct number of monday.com seats before migration. If the customer has 10 licensed Conceptboard users and 15 guests, they need at minimum 25 monday.com seats post-migration. This is a cost-impact item disclosed during scoping.

Conceptboard Comments on board elements can be captured in the PDF board export as visual annotations, but they are not available as structured data via any API. We note comment counts per board as a quality indicator and include them in the migration handoff document. Comments are partially preserved if the board export PDF captures them as text or image elements, but monday.com Item Updates are the intended destination for comment content reconstructed as manual updates.

Conceptboard Board History (Advanced+ tier feature) tracks version snapshots of board states over time. This is an audit artifact, not content data. monday.com's Activity Log tracks item-level changes (who changed what column, when) but does not store board-level version snapshots. We do not migrate Board History as most destination platforms do not support equivalent schema. We document whether boards had Board History in use so customers understand the governance capability being left behind.

Conceptboard Approval Workflows (Corporate and Government tier only) are per-board process artifacts representing review and sign-off state. They have no equivalent in monday.com's standard feature set. We flag whether any boards had active approval workflows at migration time, document the board name and workflow step count, and deliver a written recommendation for rebuilding the process using monday.com's Approvals app (if the customer has the monday.com Approvals add-on) or a third-party approval tool.

Conceptboard's facilitator tools (freeze frame, voting, structured meeting/agenda mode) are session-level collaboration features that exist only while a board session is active. They do not produce data records that can be exported or migrated. We document which boards used facilitator tools so the customer can evaluate monday.com's retrospective meeting boards, polling integrations, or third-party facilitation tools as alternatives.

Conceptboard visual elements — sticky notes, shapes, connectors, frames, text boxes, embedded images — are spatial canvas objects with no direct task-management equivalent in monday.com. These elements can be partially preserved as static content if the board is exported as a high-resolution PNG and embedded in a monday.com Item as a file attachment, but they cannot be recreated as structured monday.com items. We document this loss in the handoff and give the customer the option to keep the exported PNGs as reference artifacts in a monday.com Board dedicated to migration reference.