Migrate from Zenkit to monday Work Management

Zenkit Collections map to monday.com Workspaces. Tier-based Collection limits are migration-critical: Zenkit Personal caps Collections at 100, Plus at 1,000, Business at 5,000, Enterprise unlimited. We validate the target Monday.com plan's workspace limits during scoping. Enterprise customers with hundreds of Collections may need to consolidate before migration to avoid workspace sprawl in Monday.

Zenkit Lists map to Monday Boards as the primary container. For Lists with internal sub-sections, we map each sub-section to a Group within the same Board. The List's native view configuration (Kanban, Gantt, Table) becomes the default Board view, with additional view types configured manually post-migration. We note the primary view type in the migration specification for the customer's admin to set up.

Zenkit Items map directly to Monday Items. Standard fields (name, due date, assignee, priority) map to Monday Name, Due Date, Person, and Priority columns. We pre-create the destination Board columns before Items are imported so that all field mappings resolve without schema errors.

Zenkit Sub-items are first-class nested records with their own field schemas. Monday.com Subitems are lightweight checklist items without independent field schemas. We flatten Zenkit Sub-items with custom fields into Monday Subitems, preserving the name and checked/unchecked state. Any Sub-item custom field data beyond name and status is documented as a manual-rebuild item for the customer's admin to handle in Monday's Column settings.

Zenkit Reference fields create bi-directional links between Items in different Lists, acting as a lightweight relational database. Monday.com has no native equivalent Reference field; we resolve this by extracting the full Reference graph from the Zenkit JSON export, mapping each reference to a Connect Board or Connect Column in the destination. Circular references are detected and collapsed to a single link. We produce a Reference Resolution Map as a migration artifact for the customer to configure Connect Boards post-migration.

Zenkit select and multi-select fields map to Monday.com Status (for single-select) or Dropdown (for multi-select) columns. The option values are extracted from the Zenkit JSON export and recreated as column options. If a Zenkit multi-select has more than 50 options, we map to a Text column and note the option list as a manual-rebuild item for the admin to configure in Monday's column settings.

Zenkit number and currency fields map to Monday.com Numbers columns. Currency symbol preservation depends on whether the target Monday.com plan supports the currency formatting option. We note any currency fields that require manual formatting adjustment in Monday's column settings.

Zenkit date and datetime fields map to Monday.com Date columns. Time-of-day data is preserved in the Date column's timestamp when supported by the destination plan. We handle timezone normalization by storing all dates in UTC and noting the original timezone for the customer to verify post-migration.

Zenkit checkbox fields map directly to Monday.com Checkbox columns with the checked/unchecked state preserved. Boolean true/false logic maps cleanly.

Zenkit Formula and Aggregation fields are computed values with no native Monday.com equivalent. Monday Pro offers Formula columns but with a different function syntax and no support for cross-record aggregation like Zenkit's collection-wide rollup. We document every Formula and Aggregation field with its Zenkit definition and recommend the Monday.com Formula equivalent (or the closest approximation) as a manual-rebuild item. The original formula field is not data-carrying and does not need a data migration pass.

Zenkit Label fields (flexible tag systems) map to Monday.com Tags. We extract the full tag taxonomy as a flat list of strings and recreate it in Monday's Tags feature. Tags are not board-specific in Monday and can be applied across the workspace, matching Zenkit's label behavior.

Zenkit Comments migrate to Monday.com Comments attached to Items. Comment body, author name, and timestamp are preserved. Rich text and HTML content from Zenkit's JSON export is stripped or escaped to plain text during field mapping. We use the JSON export for comment-heavy Items to avoid the malformed CSV cell issue that arises from Zenkit's 'Keep rich text' CSV option.

Zenkit Checklist fields (a specific field type containing checklist items) map to Monday.com Subitems with the checked/unchecked state preserved. If the destination Board does not have Subitems enabled, we map Checklist items to Text column values with a checkbox prefix notation for manual conversion by the admin.

Zenkit file attachments are downloaded to local storage from the Zenkit ZIP export. We do not host files; we re-upload attachments to Monday.com via the Monday.com integration (Dropbox, Google Drive) or as hosted links in a URL column. We recommend the customer configure a Dropbox or Google Drive integration before migration so that files can be linked natively rather than stored as text URLs.

Zenkit archived Items migrate to Monday.com Items in an Archive group or with an inactive status column value. The migration scope document notes whether archived Items are included or excluded, as the decision affects record count and board structure.

Zenkit Automations have no export mechanism and do not migrate. We capture the automation configuration during the discovery phase, document each automation trigger-action pair with its conditions, and produce an Automation Inventory specification that maps each Zenkit automation to its Monday.com Automation equivalent. The customer implements automations manually post-migration.

Zenkit's Global Search index and saved global filters are UI-layer constructs with no export mechanism. We migrate the underlying data (Items, Fields, Comments) but not the search index or saved filters. The customer re-establishes saved filters in Monday's Board view configurations post-migration.