Migrate from Huly to Microsoft Project

Huly Issues map to Microsoft Project Tasks with the task name, description, assignee (mapped to resource), start date, due date (mapped to Finish), priority, and labels preserved. Huly's process states (Backlog, Todo, In Progress, Done) map to Project's Status field or to custom fields if the customer uses custom status values. We extract the full task hierarchy as a WBS structure, preserving summary tasks and subtasks as Outline Level in the export. Parent-child relationships in Huly become Project summary tasks.

Huly workspaces with custom task types (each with independent process states and custom properties) require per-type mapping tables. We enumerate all task types during discovery, extract each type's state machine, and map the states to Project Task.Status values or to a custom multi-select picklist field in Project. Custom properties per task type migrate as Project custom fields (Text, Number, Date, or Dropdown based on the Huly property type). Task type labels persist in a custom field TaskType__c for filtering in Project views.

Huly Milestones map directly to Microsoft Project Milestone tasks. The milestone name, target date, and associated issues (as a bulleted list in the task Notes field) migrate. If Huly milestones contain document attachments, we export them to SharePoint and link the URL in the Project task Notes. Milestone hierarchy from Huly (nested milestones) maps to summary task groupings in Project.

Huly's Pull Request task type (created when GitHub integration is active) has properties that have no direct Project equivalent: PR number, merge state, branch name, and reviewer list. We export PR metadata as structured text in the Task Notes field, preserving the GitHub PR URL, state (Open/Merged/Closed), and author. The actual commit graph and GitHub review history do not migrate; those remain in GitHub. We flag these records during scoping so the customer can decide whether to include them in the project plan or treat them as external references.

Huly wiki pages are collaborative rich-text documents that have no native Microsoft Project equivalent because Project does not have a document management layer. We export wiki page content (as HTML or Markdown) and upload it to the customer's designated SharePoint site or OneDrive for Business, preserving the original space hierarchy as a folder structure. We create a mapping table linking each Huly wiki page to its SharePoint URL, and we document this as a SharePoint link in the relevant Project task Notes field. Embedded images are extracted and uploaded to the same SharePoint library.

Huly Spaces map to individual Microsoft Project files (MPP) or Project for the Web projects. Each space's issues, milestones, and task hierarchy become a standalone project plan. If the customer wants a consolidated portfolio view, we create a master project in Project Desktop or use Project for the Web's portfolio features. Space-level settings (default task type, visibility) do not map directly but are documented for the admin to configure in Project.

Huly Workspaces are top-level containers holding multiple Spaces. We map each Workspace to a corresponding Project Online Project Web App (PWA) site or a SharePoint site collection at the destination. Workspace members with roles (Owner, Member) map to Project resource pool entries with role-based Resource Type (Work, Material) and max units. Active versus archived status on members maps to Resource Active flag in Project.

Huly Action Items extracted from chat conversations carry task text, assignee, and completion status. They map to Project Tasks with the source conversation thread referenced in the Notes field. We do not preserve threading structure because Microsoft Project does not support threaded task discussions. Action items are included in the task import only if they represent discrete planned work; conversational context is documented in Notes.

Huly Labels (with color metadata) migrate to a Project custom text field, either as Keywords (the built-in field) or as a custom Label__c field if the customer uses multiple label sets. Color metadata is preserved as a hex value in the field value or in a secondary custom field Color__c. We inventory all distinct labels during discovery and configure the custom field with the allowed values during schema setup.

Huly file attachments (images, PDFs, documents) are extracted from the Huly workspace storage and uploaded to the customer's SharePoint document library or Project-attached file storage. We preserve the file name, original upload date, and uploader. In the Project task Notes, we insert a hyperlink to the SharePoint file. Huly's storage quota (10GB free, 100GB on Rare, 1TB on Epic) does not map to a Project equivalent because Microsoft Project does not manage storage; SharePoint does. We flag attachment-heavy spaces during scoping so the customer can provision appropriate SharePoint storage.

Huly workspace members map to Microsoft Project Resources. We extract member email addresses, display names, and roles (Owner, Member). Each member becomes a Resource entry in the Project resource sheet with Max Units = 100%, Material Label = Work, and the member's email as Resource Initials for identification. Inactive or archived Huly members map to Resources with the Active flag set to No. Huly's role-based workspace access does not map to Project permissions; those are handled separately through Microsoft 365 group membership.