Migrate your Zenkit data

Collections are Zenkit's top-level container, analogous to Workspaces in Asana or Boards in Monday.com. Tier limits cap the number of Collections (Personal: 100, Plus: 1000, Business: 5000, Enterprise: custom). We map Collections 1:1 and verify the destination tier supports the resulting count.

Lists live inside Collections and are the primary data container. Each List has its own schema of fields and can be viewed in multiple formats. We migrate Lists with their metadata intact and recreate field schemas in the target system.

Items are the core record type in Zenkit, analogous to Tasks or Cards. Standard fields include name, due date, assignee, status, and priority. Custom fields add any data type. We map Items 1:1 and preserve all standard fields; custom fields go through field-type mapping.

Items can contain Sub-items, creating a hierarchical structure. Sub-items have their own fields and can be nested. We flatten sub-items into the target system's equivalent (subtasks, child tasks) and preserve the parent-child relationship via a reference field.

Zenkit supports Kanban, Gantt, Table, Calendar, Mind Map, and other view types. Views are display configurations, not separate data. We migrate the underlying Items and note the primary view type in the destination; views are rebuilt based on the target system's equivalent view system.

Zenkit fields include text, number, date, checkbox, select, multi-select, reference, formula, and aggregation types. Field-type mapping is required: select fields map to enums, reference fields to foreign keys, and formula fields may need recalculation in the destination.

References connect Items across Lists, creating a relational database inside Zenkit. We resolve Reference fields to direct foreign-key pointers in the target system. Circular references are detected and handled gracefully.

Label fields are flexible tag systems that can represent priority, category, or any taxonomy. We migrate Labels as a flat list of strings and recreate them in the target system's equivalent tagging or label field.

Comments attach threaded discussions to Items. Zenkit's CSV export can include comments as a separate column; JSON export includes full comment objects. We preserve comment body, author, and timestamp in the target system's comment system.

Checklist fields create sub-tasks within an Item. We convert Checklist items to sub-tasks in the target system and preserve the checked/unchecked state. This mapping depends on whether the destination supports sub-task checkbox hierarchies.

Files can be attached to Items. Zenkit provides a ZIP export of all attachments and can include attachment references in CSV/JSON exports. We download attachments to local storage, re-upload to the target system, and preserve file names and associations.

Zenkit supports archiving Items, which hides them from default views. Export options let you include or exclude archived Items. We migrate archived Items as inactive or archived records in the target system, following customer preference.

Automations in Zenkit Projects (Business tier) trigger actions based on field changes or events. Automations do not have a standard export format. We document the automation rules during scoping and recreate them as workflow rules or integrations in the target system.

Global Search is a UI feature that indexes across all Collections. It is not a data object and has no export mechanism. Search configuration does not migrate; it is re-established by the customer in the destination tool based on their data.