Migrate from Hive to Asana

Hive Projects map to Asana Projects. Project metadata including name, description, start date, due date, and visibility (public/private) migrate as Project fields. Hive's workspace-level permission structure maps to Asana's team membership model where the project owner is set as the project lead in Asana. Projects with restricted access are scoped during discovery to confirm the migrating user has read access to all project records.

Hive Tasks migrate to Asana Tasks with title, description, start date, due date, assignee, priority, and sub-task hierarchy preserved. Hive's nested task trees are flattened to Asana's single-level subtask structure where the parent Task in Hive becomes the parent Task in Asana and child Tasks become Asana subtasks. The original task creation timestamp and last-modified date are preserved as custom fields for audit.

Hive Actions are standalone checklist items or quick-capture items not tied to a project. We map these to Asana Tasks grouped by assignee. Actions without an assignee are mapped to a dedicated Asana project for unassigned items. Actions that belong to a task-level checklist in Hive become Asana subtasks under the corresponding parent task.

Hive's nested folder structure (folders containing sub-folders and projects) cannot map directly to Asana because Asana has no folder concept above the project level. We extract the folder hierarchy, map the top-level folder to an Asana Project, and convert sub-folders to Sections within that project. Projects originally nested under sub-folders become tasks within the corresponding section.

Hive Custom Fields (text, number, date, dropdown) on projects and tasks map to Asana Custom Fields. We extract the field definition and all field values per project, create matching Custom Fields in the destination Asana project, and replay values during task migration. If a Hive custom field type has no Asana equivalent (e.g., complex calculated fields), we flag it during scoping and convert it to a text Custom Field in Asana.

Hive Labels are flat tag strings applied to tasks. We preserve all label assignments and create equivalent Tags in Asana. If a label name already exists in the destination Asana workspace, we reuse it; otherwise we create it during migration. Label color is not preserved because Asana assigns colors automatically to tags.

Hive's per-project custom status schemas are the most complex part of this migration. We extract the full status set per project during scoping, build a mapping table for each project, and apply it during task replay. For Asana Board view, statuses map to columns. For List view, we create a single Custom Field of type Status with the mapped values. We flag any statuses that have no clear Asana equivalent and work with the customer to define an acceptable mapping before migration begins.

Hive time-tracking entries include hours, date, task association, and user attribution. In Asana Business tier and above, time tracking is native and entries map directly. For Asana Premium or lower tiers without native time tracking, we create a custom time-tracking section as task-level custom fields (date, hours, notes) and include a handoff document for the customer to evaluate a third-party time-tracking integration post-migration.

Hive file attachments on tasks and projects are downloaded to our staging storage and re-uploaded to Asana via the Asana Attachments API. We preserve the original filename and link the attachment to the correct task in the destination. Files exceeding 100 MB are flagged and skipped per Asana's API upload limit, with a list of skipped files provided in the migration report.

Hive Workspace Members (Admin, Editor, Viewer roles) map to Asana workspace members by email address. We extract all member assignments on tasks and projects and resolve them against the Asana destination workspace's user table. Members without a matching Asana account go to a reconciliation queue for the customer's admin to provision before the record import phase begins.

Hive shareable forms capture submissions that create tasks. We export form submissions as task records with all submitted field values preserved as task properties and custom field values in Asana. The original submission timestamp and respondent information are stored as custom fields on the task.

Hive Notes are collaborative documents attached to projects or workspaces. We export them as text and either embed the content in the project or task description (for short notes) or attach as a formatted text file (for longer documents) in the Asana task or project. The original note's creation date and author are preserved as metadata.

Hive Workflows define status progression rules and automation triggers. We do not migrate Workflows as code because Asana's Rules engine uses different trigger and action models. We capture the full workflow configuration—including triggers, conditions, and actions—as a written reference document for the customer's admin to rebuild in Asana Rules post-migration. Active workflows are listed with their expected behavior and the recommended Asana Rule equivalent.

Hive analytics dashboards and reports are computed from live Hive data and do not export as independent records. We do not migrate analytics. The customer rebuilds reports in Asana's native reporting tools (available from Business tier) or connects a BI tool to Asana's API. We provide a list of all Hive report configurations during discovery for reference.