Migrate from Kantree to monday Work Management

Kantree Workspaces map directly to monday.com Workspaces as the top-level container. We preserve workspace-level settings including color themes, default notification preferences, and member rosters. Each monday.com Workspace is created before any child Boards to ensure the workspace context is established for board-level permissions.

Kantree Projects map to monday.com Boards with board type preserved (Standard, Shareable, Private). Project metadata including description, status, and dates migrate as board-level fields. Groups (columns) inside a Kantree Project map to monday.com Groups. Project-level custom fields that are not card-specific become board-level columns.

Kantree Cards map 1:1 to monday.com Items. All standard card fields (title, description, assignees, dates, status) migrate directly. Card-level custom field values map to monday.com column values with type equivalence applied: Kantree single-select becomes monday.com Status or Dropdown; multi-select becomes monday.com Tags; date fields become monday.com Date columns; user references become monday.com People columns.

Kantree card types (Bug, Feature, Invoice, Patient, etc.) define the field schema per card category. monday.com does not have a native card-type equivalent at the workspace level; we model card types as named board templates or as sub-board structures where each card type gets its own board. We export the full card-type schema including field names, types, and validation rules and deliver a written board-design guide mapping each card type to a monday.com board configuration.

Kantree's 20+ field types map to monday.com column types with type equivalence: text to Text, number to Numbers, date to Date, rating to Numbers (1-5), single-select to Dropdown or Status, multi-select to Tags, user reference to People, card reference to Link to Item, and formula to Formula (Pro tier) or static Numbers column. Formula fields are exported with their last-known computed values as static columns at migration time; the customer chooses whether to rebuild as monday.com Formula columns post-migration.

Kantree formula fields compute dynamically from related field values at read time. We export the formula definition and the last-known computed value as a static Numbers column at migration time. On monday.com Pro ($19/seat) and Enterprise, we can recreate formula logic using monday.com's Formula column type. On Standard ($12/seat), formulas are not available and the migrated static value remains as a Numbers column.

Kantree's seven native views (Kanban, Table, Matrix, List, Timeline, Calendar, Gantt) map to monday.com equivalents: Kanban to Board view, Table to Table view, List to Group view, Timeline to Timeline view, Calendar to Calendar view, Gantt to Dashboards (Gantt widget), and Matrix to Table view with grouping. We export view definitions including filters, sort orders, and visible field selections as written board-configuration instructions because view definitions are not fully accessible via monday.com API.

Kantree KQL-powered automations (triggers, conditional branches, action chains) do not migrate as executable code. We extract every automation rule with its trigger events, KQL conditions, and action chain steps and deliver a written automation inventory that maps each Kantree automation to a monday.com automation recipe. monday.com Standard ($12/seat) includes 250 automations/month; Pro ($19/seat) includes 25,000. Automations relying on cross-card KQL queries may require restructuring as board-level triggers.

Kantree supports one-to-one, one-to-many, and many-to-many card relationships defined at the workspace level. monday.com does not have a native cross-board relationship model. We resolve relationships using a combination of monday.com's Dependencies column (for hierarchical parent-child), Subitems (for one-to-many child items within a board), and Link to Item columns (for lateral cross-board references). The relationship type is preserved in a text column on the destination item.

Kantree Comments migrate to monday.com Updates. Author, timestamp, and 2-hour editable window are preserved. Rich text content transfers as-is. Comments from users who do not have monday.com accounts are migrated with author name preserved but linked to a migration-system account pending user provisioning.

Kantree attachments (files uploaded via drag-and-drop or image toolbar) are downloaded from Kantree's storage layer with their original filenames, MIME types, and upload timestamps preserved. Files are re-uploaded to monday.com's file storage as Items are created, with the attachment linked to the correct Item via the Files column.

Kantree organization members (billable) map to monday.com team members with email as the dedupe key. Project-level observers (free in Kantree) map to monday.com Guests if the destination plan includes guest access (Standard+). The migration flags any Kantree member who was granted edit access by converting a guest to a full member, since that account carries a licensing cost that was previously avoided.

Kantree workspace and project-level role definitions (card edit, comment moderation, field visibility, view sharing) map to monday.com workspace-level permissions and board-level sharing settings. monday.com's permission model is less granular than Kantree's field-level visibility controls; we deliver a written permission-mapping document noting any capability gaps where a Kantree field-level restriction cannot be reproduced in monday.com's model.

Kantree public-facing Forms that create cards on submission export form definitions and optionally submission records. monday.com Forms are available on Standard ($12/seat) and above. We map Kantree form field labels to monday.com Form question text and migrate form submission records as Items created on the target board with submission timestamp preserved.