Migrate from Huly to monday Work Management

Huly workspaces map to monday.com workspaces as the top-level container. Each Huly workspace becomes a monday.com workspace with the same name and member list. Workspace-level settings (visibility, billing owner) are translated to monday.com workspace admin assignments. Teams with multiple Huly workspaces map each to a separate monday.com workspace or consolidate under one monday.com workspace using Board-level team assignments.

Huly spaces map to monday.com Boards. The Classic project space type is the default mapping target. Space configuration including space type settings, default task type, and visibility translate to Board settings. Huly's space membership is preserved as Board owners and members in monday.com. Groups within the board replicate Huly's sub-group structure if used.

Huly issues map directly to monday.com items on the target board. Issue properties map to columns: assignee to People column, priority to Priority labels or Status column variants, labels to Tags column, due date to Date column, and custom fields to the equivalent monday.com column type. Huly process states (Backlog, Todo, In Progress, Done) map to monday.com Status column values configured per-board.

Huly's Pull Request task type, created when connected to GitHub, has distinct properties from issues: PR number vs. issue number, merge state vs. completion state, reviewer list, and branch references. We migrate PR records as items on a dedicated monday.com board with GitHub Integration columns (PR number, repo, author, merge status). The actual GitHub commit graph does not migrate; monday.com connects to GitHub directly for live PR status after cutover.

Huly allows custom task types beyond Issues and PRs, each with its own process states and custom properties. Each custom task type becomes a monday.com Board with a Status column customized to match the task type's state values. Custom properties migrate as monday.com column types: text fields, numbers, dates, dropdowns, and formulas. We enumerate all task types during discovery and build per-type mapping tables before execution.

Huly wiki pages migrate to monday Docs as structured documents. Content blocks, headings, lists, code blocks, and embedded links transfer to monday Docs format. Embedded images and attachments migrate as Files attached to the Doc. Collaboration metadata (last editor, version history) is noted as a limitation; monday Docs does not preserve full revision history from Huly. If the customer uses Huly docs heavily, we recommend a pre-migration audit to identify docs that need active version tracking.

Huly Inbox messages are conversation-based and often contextual to a task or space. We extract message text, sender metadata, and timestamps. Messages tied to a specific issue or space are mapped as Item Updates on the corresponding monday.com item. Standalone chat messages not linked to a record are mapped to Updates on a dedicated board or retained as Notes if the customer prefers a static archive over the activity feed format.

Huly milestones group issues toward a common goal or deadline. We create a monday.com Timeline column or Date column on the target board, or use Groups named after the milestone with due dates. Milestone metadata (description, progress calculation) translates to a Description field or Doc link on the board. Multiple milestone boards can be consolidated into a single roadmap board using Group naming conventions.

Huly action items are task fragments captured within conversations. They carry text, assignee, and completion status. We map action items to monday.com Subitems on the parent item representing the originating issue or discussion. Subitem text, assignee, and status transfer. Due to the contextual nature of action items in Huly, we recommend during scoping that customers identify which action items require Subitem migration versus which can be archived as completed.

Huly labels with color metadata migrate to monday.com Tags column values. The tag names and colors transfer directly. Tags applied to issues are reapplied to the corresponding migrated items. Tags used for multi-dimensional classification can alternatively map to monday.com dropdown columns if the customer prefers structured filtering over freeform tagging.

Files attached to issues, wiki pages, or chat messages migrate as monday.com file attachments. We reattach each file to the parent Item or Doc at the destination. Storage consumption is inventoried during scoping because Huly's free tier includes 10GB of attachment storage while monday.com Basic ($9/seat) includes 5GB; customers with heavy attachment volume may need to upgrade to Standard (50GB) or Pro (100GB) before migration.

Huly workspace members and their role assignments (owner, member) migrate as monday.com Team members. Email addresses and display names map to monday.com user accounts. Active vs. archived status in Huly determines active vs. deactivated status in monday.com. Owner-level roles map to monday.com workspace admin. Users are provisioned before board migration so that OwnerId references resolve on items.

Teams using Huly for CRM-style workflows (hiring pipelines, candidate tracking) store this data in custom fields or document objects rather than a native accounts object. We identify these patterns during discovery and create dedicated monday.com Boards for candidate tracking with Status columns mapping to pipeline stages (Applied, Screening, Interview, Offer, Hired). Custom candidate fields map to monday.com columns.