Migrate from Hive to Microsoft Project

Each Hive project maps to a single Microsoft Project file (MPP) or Project Online task plan. Hive project metadata including name, description, start date, and public/private visibility is extracted from the Hive API. If the destination is Project Online, we create a PWA task plan; for desktop, we generate an MPP-compatible XML structure for import. Projects with restricted private visibility require the Hive source account to have appropriate access rights during the export phase.

Hive tasks map to MS Project tasks with Name, Start, Finish, Duration, and Priority fields. We reconstruct the WBS outline from Hive's folder and sub-task nesting structure, mapping parent-child relationships to MS Project Summary tasks. Tasks without a start date in Hive receive a provisional start date based on the parent project's start date and a placeholder duration of 1 day; customers confirm or adjust these during sandbox validation. Milestone tasks in Hive (tasks with a milestone flag or zero duration) map to MS Project milestone tasks with the Milestone field set to Yes.

Hive Actions are standalone checklist items or quick-capture items not tied to a project. We group orphaned Actions by their creator and date, then create a dedicated MS Project task list or attach them to a designated summary task in the destination. The customer specifies during scoping whether standalone Actions should become tasks in the primary project plan or a separate catch-all project.

Hive custom fields on tasks (key-value pairs with type: text, number, date, dropdown) map to MS Project custom fields (Text1-30, Number1-10, Cost1-10, Flag1-10). We extract the per-project custom field schema from Hive and create matching custom fields in the destination MS Project file or Project Online before data import. Dropdown-type custom fields map to Dropdown (Enterprise) custom fields in Project Online; text fields map to Text custom fields.

Hive labels are flat tag strings applied to tasks. We preserve all label assignments and map them to an MS Project Text custom field (e.g., Text1 labeled as Hive_Labels) using comma-separated strings. If the destination is Project Online and the customer requires hierarchical categorization, we can map labels to Outline Code fields instead.

Hive allows each project to define its own custom status set, meaning a status value in one Hive project may have a different meaning in another. We extract the per-project status schema and map each project's statuses independently. MS Project tasks have a fixed Status field (Complete, On Schedule, Late, Future Task, Marked For Deletion) or a custom status picklist. We either map to MS Project's standard status values or create a custom Text field to preserve the original Hive status label verbatim.

Hive task assignees map to MS Project resource assignments. We extract all distinct assignees from Hive and build a resource pool in the destination. For Project Online, resources must exist in the PWA resource center; we provision them before task import. If a Hive assignee email has no matching user in the destination, we flag the assignment for the customer's admin to resolve and either map to a generic resource or reassign to an existing user.

Hive's time-tracking entries linked to tasks map to MS Project Assignment Actual Work fields. We extract time entries with hours, date, and user attribution and replay them as Actual Work on the corresponding task assignment. MS Project Desktop expresses work in hours or minutes depending on project settings; we use the customer's specified default. Time entries without a matching destination resource are held in a reconciliation queue.

Hive file attachments are exported via Hive's file reference API, downloaded to staging storage, and re-uploaded to the destination. For Project Online, attachments are stored in the associated SharePoint document library and linked via a Hyperlink custom field on the task. For Project Desktop, we store file references as Hyperlink fields pointing to the staging URL for manual re-attachment by the customer after migration.

Hive Notes attached to projects or tasks are exported as standalone text and mapped to the MS Project task Notes field. If a Hive Note contains rich formatting, we preserve it as plain text with preserved line breaks; images embedded in Hive Notes are extracted as file references and added as Hyperlink fields.

Hive workspace members with Admin, Editor, and Viewer roles map to resources in MS Project. We extract all members from the source workspace, deduplicate by email, and provision resource records in the destination. Role information is preserved in a custom Text field on each resource (e.g., Text1 labeled as Hive_Role) for audit. Members without an email match in the destination are flagged during reconciliation.