Migrate from Alian Hub to Trello

Alian Hub Projects map directly to Trello Boards. Each Project's name, description, and creation timestamp migrate as the Board name, description, and create date. Board visibility (public vs private) maps from Alian Hub's project-level visibility settings. Alian Hub's Board, Table, Calendar, and Gantt view preferences are not transferable — we configure the destination Board with a standard List layout and note that the customer can enable Calendar or Timeline Power-Ups post-migration.

Alian Hub Tasks map to Trello Cards within the destination Board. The Task title becomes the Card name, the Task description (rich text) becomes the Card description, the assignee maps to the Card member assignment, the due date maps to the Card due date, priority maps to a Card label (High, Medium, Low, or custom labels matching Alian Hub's priority levels), and the status maps to the Card's List position within the Board. Custom status labels used in Alian Hub map to existing Trello Lists or new Lists created during migration.

Alian Hub Subtasks map to Trello Checklist items within the parent Card. The parent-child relationship is preserved by placing all Subtasks from a given Task into a single Trello Checklist named 'Subtasks'. Subtask ordering (position within the parent) migrates as checklist item sequence. Completion status (checked vs unchecked) maps directly. Trello does not support nested checklists — any Subtask that itself has Subtasks is flattened to one level of checklist items with the nested Subtask title prefixed by a dash or indent notation in the checklist item name.

Alian Hub custom fields defined via the Custom Field Manager migrate to Trello Custom Fields using the free Custom Fields Power-Up. We detect all active custom field definitions during scoping, map field types (text, number, date, dropdown, checkbox) to their Trello Custom Field equivalents (text, number, date, select, checkbox), and create the custom field definitions on each destination Board before Card migration begins. Multi-select dropdown values in Alian Hub map to Trello select custom fields with one option per value. Custom field values on each Card are populated during the Card import phase.

Alian Hub time entries do not have a native Trello equivalent. We map time entries to a structured notation in the Card description (format: '[HH:MM - HH:MM] Duration: Xh Ym - Note: description') and flag the customer for a Power-Up recommendation. For ongoing time tracking, we recommend TimeCamp, Toggl Track, or Planyo based on the customer's reporting requirements. If the customer has a time-tracking Power-Up already in use, we map time entries to that Power-Up's structure. Historical time data is preserved in the Card description; future time tracking relies on the selected Power-Up.

Alian Hub user accounts map to Trello workspace Members. We resolve by email address match during migration. Each user's display name, email, and Alian Hub role (Admin, Member) map to Trello's workspace member roles (Admin, Normal, Guest). The Alian Hub permission model (User Permissions feature gated on paid tiers) translates to Trello Board-level permission roles. If the destination Trello workspace uses Single Sign-On (Google or Atlassian account), we flag any Alian Hub users without matching SSO accounts for manual provisioning.

Alian Hub Tags on Tasks and Projects map to Trello Labels on Cards. Tag names migrate as Label names; tag color (if assigned in Alian Hub) maps to a Trello Label color. If the customer uses tag categories or tag groups in Alian Hub, we map each category to a Trello Label color family. Label names are preserved verbatim. Tags used across multiple Projects map to Labels accessible on all destination Boards if the customer uses a Trello workspace with shared Labels.

File attachments associated with Alian Hub Tasks migrate as Card attachments in Trello. We extract attachments via direct database query or the Data Import/Export feature (Team tier or higher), transfer files via secure bandwidth to Trello's attachment API, and attach them to the corresponding Card. Large attachment volumes (over 50 GB total) require bandwidth planning; we flag this during scoping and exclude it from the base migration fee. Attachment comments and version history do not migrate.

Alian Hub Channels (project or topic-based chat rooms) and One-to-One Chat do not have a native Trello equivalent. Trello Cards support comments but not real-time chat rooms. We do not migrate Channel content as business records. During scoping, we inventory the Channel structure and deliver a written map recommending which Channels could become Trello Boards (for persistent topic-based collaboration) or could be archived as reference documents in a linked Confluence space. The customer implements the Board recreation post-migration.

Alian Hub Task comments migrate to Trello Card comments. Each comment's author (User), timestamp, and body text transfer directly. Rich text formatting in Alian Hub comments is simplified to plain text for Trello compatibility. Comment reactions and emoji reactions do not migrate. If comments reference other Tasks by ID, we flag these as broken references for manual resolution.

Alian Hub's built-in AI Assistant (paid tier feature) has no Trello equivalent. Trello does not include native AI capabilities in its standard plans; Atlassian's AI features (Atlassian Intelligence) are available in Atlassian platforms but not as migratable content. We document the AI Assistant usage patterns observed during scoping as a reference for the customer to evaluate Trello AI Power-Ups or Atlassian Intelligence availability post-migration.

Alian Hub workflow rules (triggered by task events on paid tiers) do not migrate to Trello. Trello Butler offers rule-based automation but uses a different trigger-and-action model. We deliver a written inventory of every active Alian Hub workflow rule with its trigger conditions, actions, and recommended Butler equivalent. The customer rebuilds automations in Trello Butler or a third-party automation tool (Zapier, Make, Power Automate) post-migration. This item is explicitly out of migration scope.