Migrate from Huly to Asana

Huly's top-level Workspace maps to an Asana Organization. If the Huly workspace contains multiple independent business units, we create separate Asana Organizations or Teams within a single Organization based on the customer's preference. Workspace-level settings (visibility, member list) migrate as Organization settings and Team membership. The key migration decision is whether to preserve Huly's multi-workspace structure as multiple Asana Teams or consolidate into a single organization structure.

Huly Spaces map directly to Asana Projects. Space type settings (Classic project, any custom space types) are preserved in the project description or a custom project field. Space-level permissions migrate as Asana project team membership. Sections within the Huly Space map to Asana Sections within the destination project. If the Huly Space uses a custom process workflow, we create a custom field in Asana to capture the original process state names.

Huly Issues map to Asana Tasks within the corresponding project. Assignee, priority, labels, and custom field values migrate directly. Huly's process state (Backlog, Todo, In Progress, Done) maps to Asana's task completion status (completed or not) plus an optional custom field capturing the original state name. Custom properties attached to the issue migrate as custom fields on the Asana task. Due dates and start dates migrate as Due Date and Start Date on the task.

Huly's custom task types each carry their own set of process states and custom properties. We create a custom field in Asana capturing the original Huly task type name, and per-type custom fields map to Asana custom fields of equivalent type (text, number, date, single-select, multi-select). Process states unique to each task type migrate as custom single-select fields. The customer defines which task type becomes the default for each project during scoping.

Huly Pull Request task type records migrate to Asana Tasks with a custom field capturing the original PR number, PR URL, merge state (Open, Merged, Closed), and branch name. The GitHub commit graph itself does not migrate; GitHub remains the source of truth for PR history. We preserve the task-level PR metadata so that Asana tasks retain the GitHub context. If the team uses GitHub's native integration with Asana, we configure it post-migration and link the migrated tasks.

Huly wiki pages inside Spaces are rich-text collaborative documents. We export page content as structured HTML and attach it to the corresponding Asana project as a pinned description or as a document attachment. For wiki pages that represent project briefs, requirements, or specs, we create an Asana task with the page content in the description and the page title as the task name. Embedded images and attachments within wiki pages are extracted as separate files and reattached to the parent task or project.

Huly Inbox chat messages and threaded discussions are exported with sender metadata, timestamp, and message body. We attach each message thread as a comment on the corresponding Asana task (identified by topic association in Huly). Action items extracted from chat messages are created as separate tasks in the relevant project with the original assignee preserved. Message threading structure is flattened to chronological comment order since Asana comments do not support nested reply threads.

Huly Milestones group issues toward a common deadline or deliverable. We create an Asana task for each milestone with the milestone name and target date, marking it as a milestone task in Asana's milestone view. If the customer uses Asana Portfolios, we add the milestone task to the relevant portfolio. Milestone-to-issue associations migrate as subtasks or section labels under the milestone task so the grouping relationship is preserved.

Huly labels with color metadata migrate to Asana Tags with the same color assignments. Labeled issues are tagged in Asana with the migrated tag. If a Huly label represents a category used across multiple task types, the tag is applied universally in Asana. We inventory all label names during discovery to identify any naming conflicts with existing Asana tags in the destination organization.

Files attached to issues, wiki pages, or chat messages are downloaded from Huly's storage and reattached to their parent Asana task during migration. Huly's storage billing is based on attachment size (10GB on Common, 100GB on Rare, 1TB on Epic, maximum on Legendary); we inventory total attachment volume during scoping so customers can verify that their Asana plan storage allocation accommodates the migrated files. Attachments exceeding Asana's per-file size limits are flagged for alternative handling.

Action Items in Huly are workflow tasks captured within chat conversations. We extract action item text, assignee, and completion status and create corresponding Asana tasks in the relevant project. The original action item text and source message context are included in the task description. Completion status migrates as task completion in Asana. If the action item references a specific issue or document, we link the new task to that migrated record.

Huly workspace members and their role assignments (owner, member) are mapped to Asana Organization members. Email addresses and display names migrate to the Asana user profile. Archived members in Huly are created as inactive users in Asana or held in a reconciliation queue for the admin to resolve. Role-based access differences between Huly and Asana (Huly's owner/member model vs Asana's admin/member/guest model) are mapped during discovery and applied as the customer specifies.