Migrate from KANNA to monday Work Management

KANNA Projects map directly to monday.com Boards. We preserve the Project name, status, date range, and client/property association as Board metadata. KANNA's Project-level custom input fields (template-bound fields configured via Settings) map to custom columns on the target Board. Each Board is created in a monday.com Workspace that corresponds to the customer's operational grouping.

KANNA Tasks map to monday.com Items. The task name, description, due date, assignee, and status migrate directly. We preserve the parent-child hierarchy by placing each Item in the appropriate Group (derived from the parent Sub-project if present) on the Board. KANNA task status values map to monday.com Status column values, and we flag any KANNA custom status that requires a new Status option to be added to the destination Board.

KANNA Sub-projects allow work to be split into phases or multi-site work within a parent Project. We map Sub-projects to monday.com Groups on the corresponding Board. The Group name carries the Sub-project title, and all child Tasks land inside that Group as Items. If monday.com's Group naming conventions conflict with the Sub-project naming (e.g., if the Sub-project name is unusually long), we truncate to monday.com's Group name limit and note the original name in the Item description.

KANNA custom fields are configured per project template via Settings > Customize Settings and are not global fields. We capture the field definition (name, type, required status) and the stored values on each Project record. In monday.com, we create matching custom columns on the target Board using the closest available column type (text, number, date, dropdown, or checkbox). If the KANNA field is a multi-value field, we use monday.com's multi-select column type.

KANNA Photo Reports are a first-class export in KANNA's Data Import/Export feature. We extract photos and their captions and attach them to the corresponding Item in monday.com using the native image upload or file attachment feature. The caption becomes a text note on the attachment or a column value on a dedicated notes column. Photo metadata (date taken, uploader) migrates to a custom text column if the customer requires it.

Documents associated with Projects and Tasks in KANNA migrate as file attachments on the corresponding Item in monday.com. Document content itself is not extracted or transformed; the file is preserved in its original format and attached to the Item. We log the original document name and any KANNA-specific folder path as a text note for traceability.

KANNA's in-platform chat and reporting threads on Projects and Tasks are not listed as a named export category in KANNA's Data Import/Export documentation. We extract them where they appear in the export format or UI, but this is a known gap. We flag any Project or Task with missing thread history before migration begins and advise the customer to manually archive critical threads. Threads that are extractable migrate as monday.com Item Updates with author, timestamp, and text content preserved.

KANNA separates customer information and property information as distinct data types in its Data Import/Export feature. We map KANNA Clients to monday.com contacts if the customer uses monday CRM, or to a text column on the Board if Work Management is the destination product. KANNA Properties map to a text or link column capturing the property name, address, and reference. The mapping type depends on the customer's monday.com product tier and intended use of property data post-migration.

KANNA displays project timelines as a Gantt Chart derived from task start dates, end dates, and dependencies. We extract the underlying task date fields from KANNA and reconstruct the timeline in monday.com using the Timeline column (available on Standard and above). KANNA task dependencies map to monday.com Dependency columns. We note that monday.com's Gantt view renders the same Timeline data in a Gantt-style visual; the underlying data structure is identical.

Project and Task statuses in KANNA are configurable per workspace. We capture the full status taxonomy during scoping and create matching Status column values on the destination Board. KANNA's status color coding maps to monday.com's Status color options. If the customer uses KANNA's Pro Plus approval flow, the approval statuses (pending, approved, rejected) map to specific Status values that we configure before migration begins.

KANNA user accounts and task assignments export separately. We map each KANNA user to a monday.com user by email address. If a monday.com account does not exist for a KANNA assignee, we flag that assignee in the reconciliation report and the customer provisions the account before migration resumes. Assignees without a destination account after provisioning are set to the board admin or a designated fallback user.

KANNA's Pro Plus approval flow feature does not have a direct monday.com equivalent as a migration artifact. We capture the approval chain structure (approver list, approval stages, notification triggers) as a written specification and deliver it to the customer's admin to rebuild using monday.com's automation recipes. The customer may also consider monday.com's built-in approval workflow feature if available on their plan.