Migrate from Hive to Trello

Hive projects map 1:1 to Trello boards. The Hive project name becomes the board title, project description maps to the board description, and the project's public or private visibility setting determines whether the Trello board is public or private. Each Hive workspace maps to a Trello workspace, and projects within that workspace become boards within the corresponding Trello workspace. If the destination Trello workspace does not yet exist, we create it via the Trello API before board creation.

Hive tasks map to Trello cards. Task title becomes the card name, task description becomes the card description, due date maps to the due date field, start date maps to the start date field if the Trello plan supports it, and priority (low, medium, high, urgent) maps to a label color on the card. Assignee emails are resolved to Trello workspace members and added to the card membership record during migration. Each Hive task becomes a Trello card with its full metadata preserved as card fields or checklist items. Sub-actions migrate as checklist items under the parent card.

Hive's nested action hierarchy (action, sub-action, sub-sub-action) does not map to Trello's flat card structure. We flatten the hierarchy by creating the top-level Hive action as a Trello card and converting all sub-actions to checklist items on that card. We preserve the sub-action title and any completion status. If a sub-action itself has children, we create nested checklist items or attach the full hierarchy as a text file listing the complete action tree.

Hive custom fields on tasks (text, number, date, dropdown, checkbox, rating) map to Trello's Custom Fields Power-Up, which supports these types natively on Standard ($5/user) and Premium ($17/user) plans. We create field definitions in the destination Trello workspace before migration and populate values on each card during replay. Trello Free does not support custom fields; we flag this limitation during scoping and advise on plan requirements before migration begins.

Hive labels are flat tag strings applied to tasks. We extract the complete label set per workspace, deduplicate across projects, and create equivalent labels in the destination Trello workspace. Label colors are mapped to Trello's standard color palette. We apply label assignments during task replay by matching the Hive label name to the created Trello label.

Hive workspaces define custom status sets per project. Trello does not have named status fields per card; instead, Lists act as column headers within a board. We create a List for each distinct status value in the Hive project and map each task to the List matching its Hive status. Tasks with statuses that have no direct equivalent go to a fallback List (typically the first List or a designated 'In Progress' column). Status color mapping carries over if the destination workspace has label-based status indicators.

Hive task assignees are referenced by user email. We resolve each assignee email against the destination Trello workspace members. If a Trello member does not exist with a matching email, we flag the unresolved assignee during data audit and give the customer the option to provision the member in Trello before migration or map to an existing member. Orphaned assignees without a match in the destination are attached as a card comment noting the original Hive assignee.

Attachments on Hive tasks and projects export via Hive's file reference API. We download files to staging storage, then re-upload to Trello as card attachments via the Trello API, preserving original filenames and attachment timestamps. Trello has a 10MB per-file limit on Free and 250MB on Standard and Premium. Files exceeding the destination plan limit are flagged separately and the customer decides whether to migrate them manually or exclude them.

Hive task comments and activity stream entries become Trello card comments. Author display name and comment timestamp migrate with each comment. If the comment author does not have a matching Trello workspace member, we post the comment under the migrating admin's account and note the original author in the comment body. Comment threading in Hive flattens to sequential comments in Trello since Trello does not support threaded replies natively.

Hive's built-in time tracking produces time entries linked to tasks with hours logged, date, and user attribution. Trello has no native time-tracking feature in core; Standard and Premium plans can use third-party power-ups. We convert time entries to checklist items on the relevant card with the format '[hours]h [date] - [user]' as the item text, or we attach a card description note listing the complete time log. The customer chooses the preferred format during scoping, and we document which format was applied.

Hive Notes are collaborative documents attached to projects or workspaces. We export them as text files with the note title, body, author, and last-modified date and attach them to the relevant project board in Trello. If a Hive Note references multiple tasks, we attach it to the primary project board and add a card comment linking to it.

Hive shareable forms capture submissions that create tasks. Each form submission becomes a Trello card on the designated project board with the submission field values preserved in the card description or mapped to custom fields if the destination plan supports them. Attachments submitted through the form migrate as card attachments with the same file-size constraints noted above.