Migrate from Hive to monday Work Management

Hive Projects map to monday.com Boards as the top-level container. We preserve project name, description, start and target dates, ownership (workspace member), visibility setting (public/private), and any project-level custom fields. Board creation in monday.com is the first migration step because Items reference their parent Board via boardId on insert.

Hive Tasks map to monday.com Items with title, description (migrated as text column), due date, start date, priority, and assignee preserved. The task status maps to the monday.com Status column, with a per-project mapping table built from Hive's custom status schema. Sub-tasks within a Hive task are migrated as monday.com Sub-items; deeply nested hierarchies (more than one level) are flattened into parent-child Item groups since monday.com supports only one sub-item level.

Hive supports unlimited sub-task nesting depth; monday.com supports one level of Sub-item below an Item. For Hive tasks with more than one level of nesting, we flatten the tree by maintaining a custom column (Parent_Task_ID) that preserves the hierarchical relationship and renders it in the destination as a grouped or linked structure. The customer's admin chooses between using monday.com's Sub-item feature or a linked-items approach based on board complexity.

Hive Actions are standalone checklist items or quick-capture items not tied to a project. We migrate these as individual monday.com Items in a dedicated Actions Recovery board, grouped by assignee or creation date, so teams can review and reclassify them into relevant project boards post-migration.

Hive custom fields (text, number, date, dropdown, checkbox) on projects and tasks map to monday.com column types: text to Text column, number to Numbers column, date to Date column, dropdown to Dropdown or Labels column, checkbox to Checkbox column. We extract the full custom field schema per workspace and pre-create all columns on the destination Board before data import to ensure column Ids are available for Item inserts.

Hive Labels are flat tag strings applied to tasks. We preserve all label assignments and create equivalent Tags in monday.com on the destination board, creating any missing labels as needed. Tags in monday.com are workspace-level, so label deduplication across projects happens during the schema audit phase.

Hive workspaces have custom status sets per project (or globally) with arbitrary display names. We extract the full status schema per project and create a mapping table: each Hive status value maps to a monday.com Status column value on the corresponding board. When Hive and monday.com have overlapping status values (e.g., To Do, In Progress, Done), we match by display name; new statuses are created in monday.com to accommodate arbitrary Hive status names.

Hive's built-in time tracking produces time entries with hours, date, user attribution, and optional notes linked to tasks. We extract these as time entry records and replay them in monday.com using either the Numbers column (hours as decimal) or the native Time Tracking column if the destination account is on a plan that supports it. Orphaned entries (where the Hive user does not exist in monday.com) are flagged for reassignment to an existing user or conversion to a note on the Item.

Attachments on Hive tasks and projects are exported via Hive's file reference API, downloaded to FlitStack AI staging storage, and re-uploaded to monday.com linked to the corresponding Item. We preserve filenames, file sizes, and the attached Item association. File uploads exceeding monday.com's storage limits per plan are flagged for customer decision before migration.

Hive workspace members with roles (Admin, Editor, Viewer) are extracted and matched by email address to monday.com workspace members. Any Hive member without a matching monday.com account is held in a reconciliation queue for the customer to provision before item import begins, because assignee fields require a valid monday.com UserId.

Hive Notes are collaborative documents attached to projects or workspaces. We export them as standalone text records and attach them to the relevant Board or Item in monday.com as a Text column with the note content, or as the Item description if the note is task-specific. Rich text formatting in Hive Notes is preserved as plain text in monday.com Text columns.

Hive shareable forms capture submissions that create tasks. We map each form submission to a monday.com Item with field values populating the corresponding column types. Form submission metadata (submission date, responder email if captured) migrates as additional columns on the Item.

Hive Workflows define status progression rules and automation triggers. monday.com's automation model differs structurally (trigger-action recipes versus Hive's rule-based progression). We capture workflow configurations and represent them as a reference document listing each Hive Workflow with its trigger, conditions, and actions. The customer's admin rebuilds equivalent automations in monday.com using the automation recipe builder; we do not migrate workflows as executable configuration.