Migrate from Huly to Trello

Huly workspaces map to Trello workspaces or organizations depending on the destination plan. Trello Free and Standard support workspace-level organization; Enterprise adds organization-level controls with advanced permission settings. We map the Huly workspace name to the Trello workspace name and preserve workspace-level member roles as Trello workspace admin or normal member roles.

Huly spaces are the equivalent of boards in Trello. Each space type (Classic project, Tracker, etc.) maps to a Trello board. Space configuration settings, including visibility and member access, become Trello board visibility (public/private) and permission settings. If the Huly space has multiple lists of its own, we evaluate whether to create multiple boards or a single board with custom lists during scoping.

Huly issues map to Trello cards. The issue title becomes the card name, the issue description migrates as the card description (markdown preserved where possible), assignee maps to the Trello card member, priority maps to a card label with color coding, and the process state (Backlog, Todo, In Progress, Done) maps to a Trello list. We use Huly's process state to select the target list during migration.

Huly allows multiple custom task types beyond the default Issue type, each with its own set of process states. We enumerate all task types during discovery and build a per-type mapping table. Each custom task type becomes a labeled card (Trello Free/Standard) or a card with a custom field set to the task type name (Trello Premium). The process states within each task type are mapped to distinct Trello list names if they differ from the default set, or to label color variations within a single list.

Huly's GitHub-synced Pull Request task type has properties not present on standard issues (PR number, merge state, branch name, review status). We migrate PR task data as a Trello card with a GitHub Power-Up link to the original PR. Merge state (Open, Merged, Closed) is stored as a card label. The actual GitHub commit graph and branch history do not migrate; the Trello card carries the PR metadata and a link back to GitHub as the source of truth.

Huly wiki pages are rich-text collaborative documents with embedded links and images. Trello cards contain a markdown-friendly description field but do not have native document management. We migrate wiki page content as card descriptions for standalone documents, with a link-back note indicating the original Huly page URL. Teams using wiki pages heavily should plan a Confluence workspace alongside Trello as the document destination; we flag this during scoping.

Huly milestones group issues toward a common goal or deadline. We migrate milestone metadata (name, target date) and attach the deadline to every migrated card that belongs to that milestone as a Trello due date. The milestone name becomes a Trello label on all member cards. Milestones without a date become labels only.

Huly labels with color metadata migrate directly to Trello labels on the corresponding cards. Label names and colors are preserved. Trello supports up to 50 labels per board, which is sufficient for most Huly workspaces; we flag boards approaching this limit during scoping.

Files attached to Huly issues, wiki pages, or chat messages migrate as Trello card attachments. Huly bills attachments against storage (10GB free, 100GB Rare, 1TB Epic) while Huly objects themselves are unlimited. We inventory all attachment-heavy spaces before migration and flag the total attachment size against the destination Trello plan's storage limits. Trello Free caps attachments at 10MB per file; Standard and Premium raise this limit significantly.

Huly workspace members with their roles (owner, member) migrate to Trello workspace members. Email addresses and display names map to Trello user records. Active vs. archived status is preserved; archived Huly members are invited as inactive or deprovisioned depending on the customer's preference. If a Huly user has no matching Trello account, they are added to a reconciliation queue for the customer to provision before migration.

Huly inbox chat messages and threaded discussions that are contextually linked to a specific issue can migrate as Trello card comments with the sender name and timestamp. This mapping applies only where the conversation context is clearly tied to a task. General workspace chat without a specific task reference does not have a direct Trello equivalent and is flagged during discovery for the customer's awareness.

Huly action items capture tasks within conversations with assignees and completion status. We extract action item text, assignee, and completion state and map them to Trello checklist items on the corresponding card. Action items that are not linked to a specific task are flagged for the customer to assign to a card manually post-migration.