Migrate from Alian Hub to monday Work Management

Alian Hub Projects map to monday.com Boards at the Workspace level. We create a monday.com Workspace per Alian Hub Project when the customer uses multi-workspace organization, or we create a single monday.com Workspace with separate Boards per Alian Hub Project when board-level separation is preferred. Board names, descriptions, and icon/color preferences migrate from Alian Hub Project metadata. View preferences (Board, Table, Calendar, Gantt) stored per Project in Alian Hub do not transfer; we recommend selecting the Board view as the default and enabling Table and Calendar as secondary views post-migration.

Alian Hub Tasks migrate to monday.com Items within the target Board. The Task title maps to Item name, description migrates as the Item's Updates/Activity summary, due date maps to the Date column, assignee maps to the Person column, and priority maps to a Status column with priority labels. Custom status labels used within each Alian Hub Project are preserved as Status column options on the corresponding monday.com Board.

Alian Hub Subtasks exist as hierarchical children under Tasks and map to monday.com Subitems attached to the parent Item. Parent-child linkage is preserved by resolving the Alian Hub task_id against the newly created Item ID at migration time. Subtask ordering is preserved via the Subitem position field. Alian Hub's custom status and priority on subtasks map to Subitem Status and Priority columns on the Subitem level.

Alian Hub's Custom Field Manager definitions migrate to monday.com column types: text fields map to Text columns, numbers to Numbers columns, dates to Date columns, dropdown selections to Status columns, person lookups to Person columns, and URL fields to Link columns. We detect all active custom field definitions during scoping, infer the appropriate monday.com column type from the stored data format, and create columns in the target Board before Items are imported. Multi-select custom fields map to multi-select Status columns in monday.com.

Alian Hub time entries (task association, user attribution, duration, and notes from the Timesheet Management feature) migrate to monday.com Items. For Standard and Pro plans with native Time Tracking columns, we create Time Tracking entries linked to the migrated Item using the Alian Hub duration and timestamp. For Free or Basic plans without Time Tracking, we create a separate Time Log Board with Items representing each time entry, linked to the project Item via a Connect Boards column.

Alian Hub user accounts map to monday.com User accounts by email match. Role and permission structures from Alian Hub (Admin Insight, User Permissions features) are translated to monday.com Workspace roles: Admin, Member, or Viewer. Alian Hub deactivated or archived accounts (due to license downgrade from Enterprise to Team) are flagged in a reconciliation queue for the customer to confirm active status before user provisioning.

Alian Hub Channels (project or topic-based) and One-to-One Chat content migrates as Notes attached to the relevant Board or Item in monday.com. We extract channel metadata (name, created date, member list) and message history where the database export is available. Channel membership is not a monday.com native concept; we document the member list for manual group assignment post-migration. Chat history volume and the self-hosted hosting configuration determine whether message content is included in scope.

Alian Hub tags and labels on Tasks and Projects map to the monday.com Tags column type. Tag arrays migrate as flat tag values. Alian Hub tag count and naming are preserved. Tags used for categorization across multiple Boards map to a shared Tags column if the customer configures the same tag taxonomy in monday.com.

File attachments associated with Alian Hub Tasks and Projects migrate via URL reference where attachments are hosted externally, or via direct file transfer where the self-hosted instance storage is accessible. We flag large attachment volumes (exceeding 10 GB total) for bandwidth planning during scoping. monday.com File columns accept direct uploads during migration; files exceeding monday.com storage limits on the destination plan route to cloud storage with a link reference on the Item.

Alian Hub view preferences stored per Project (Board, Table, Calendar, Gantt) map to monday.com Board view types. We configure all four view types on each migrated Board as secondary views. The default view is set to Board (kanban-style) as the closest Alian Hub equivalent. Gantt view requires no additional configuration in monday.com; the Timeline column drives Gantt rendering automatically.

Alian Hub's CRM module stores Contacts and Companies as separate entities with a relationship. These migrate to monday.com CRM Contacts and Companies as separate item types on their respective boards. The Alian Hub Contact-Company relationship maps to the monday.com CRM relationship link between Contact and Company records. If the customer does not activate monday.com CRM, Contacts and Companies migrate as Items on a dedicated Address Book Board with a Connect Boards column for the relationship.

Alian Hub HR module data (departments, roles, employment status) does not have a direct monday.com equivalent. We map active Alian Hub user records to monday.com User accounts and preserve department and role information as custom columns on the People Board or as Tags. Employment status and HR-specific data is delivered as a CSV export for the customer's HR admin to maintain in a separate system.

Alian Hub's Finance module (invoices, expense tracking) migrates to a separate monday.com Finance Board with Items representing invoices and expenses. Numeric columns handle amounts, Status columns handle payment status, and Date columns handle due dates. Finance-specific data does not integrate with monday.com's native reporting; we recommend a dedicated accounting tool for financial reporting post-migration.