Migrate your Kantree data

Workspaces are the top-level container in Kantree. Each workspace holds projects, card types, views, and automations independently. We export workspace configurations, color themes, and automation rule sets intact. When copying to a destination without workspace parity, we map workspace hierarchies to project folders or organizations and flag which access-control settings require manual reapplication.

Projects sit inside workspaces and own their card collections, groups (columns), and per-project views. We preserve project metadata, card group structure, and any project-level custom fields. Projects that span multiple workspaces (Business tier) are handled by mapping them to a flat destination project list and noting the workspace membership for downstream automation reconnection.

Cards are the atomic work unit. They carry a card type, a set of custom field values, assignees, dates, attachments, comments, and relationship links to other cards. We migrate cards 1:1 with all standard fields preserved. Custom field values are mapped to equivalent fields at the destination, with a field-mapping matrix generated during scoping.

Card types define the available field schema per card category (e.g. Bug, Feature, Invoice, Patient). They are workspace-scoped and can be arbitrary. We export the full card-type schema including field names, types, options, and required flags. At the destination, we either map to existing object types or create new ones, preserving the type-to-field relationship.

Kantree supports 20+ field types including text, number, date, rating, single/multi-select, user reference, card reference, and formula fields. Formula fields compute dynamic values from other fields using KQL-like expressions. We export field definitions and values; formula fields require re-evaluation at the destination since computed values do not persist as static data.

Views are saved configurations of Kanban, Table, Matrix, List, Timeline, Calendar, and Gantt that display filtered and grouped card subsets. We export view definitions including filters, sort orders, column configurations, and grouping rules. Gantt view is Business-tier only — we flag its presence during scoping so the destination plan accommodates the feature set.

Automations consist of triggers (card events, schedule, form submission), KQL-based conditional branches, and action chains (set field, move card, post comment, copy card, etc.). We export automation rule definitions as structured JSON. At the destination, we reconstruct the logic in the target platform's automation engine, noting any unsupported KQL expressions that require manual recreation.

Comments are timestamped text entries attached to cards. They support 2-hour editable windows for authors and permanent moderation access for users with comment-moderation roles. We export full comment history with author attribution and timestamps. Mentions (@user) and card references are preserved as plain text links during migration.

Attachments are files uploaded directly to cards via drag-and-drop or the image toolbar. We export file metadata and download URLs from Kantree's storage layer and re-upload to the destination's attachment system, preserving original filenames and upload timestamps.

Kantree supports one-to-one, one-to-many, and many-to-many card relationships defined at the workspace level. Relationship fields are exported as structured link records. At the destination, we map these to equivalent relation/link fields or custom objects, handling directional and multi-card relationship chains.

Kantree distinguishes between organization members (billable), project-level observers (free but read-only), and external guests. We export user records with role assignments, workspace memberships, and observer status. At the destination, we map billable members to paid user seats and flag observers for read-only account creation.

Roles define workspace and project-level permissions (card edit, comment moderation, field visibility, view sharing). We export role definitions and per-user assignments. Role semantics differ across platforms, so we generate a permission-matrix mapping and flag cases where a single Kantree role must split into multiple destination roles.

Forms are public-facing input interfaces that create cards on submission. They capture submitted field values, submitter info, and timestamp. We export form definitions and, optionally, submission records as card entries. Form-to-card field mapping requires manual validation due to conditional form logic.

Kantree Reports display aggregated workspace and project statistics. They are configuration artifacts rather than stored datasets. We export report definitions (filters, groupings, displayed fields) and reconstruct them in the destination's reporting layer where equivalents exist.