Migrate from Alian Hub to Asana

Alian Hub Projects map directly to Asana Projects. We use the Alian Hub project name as the Asana project name and preserve the created_at and updated_at timestamps in custom fields. Project-level view preferences (Board, Table, Calendar, Gantt) are stored per-project in Alian Hub; Asana's view model differs and these preferences are not transferred as display settings. Team assignments in Alian Hub map to Asana Teams if the destination uses the Teams workspace structure.

Alian Hub Tasks map 1:1 to Asana Tasks. We transfer title, description (rich text preserved), due date, priority, assignee, and status. Alian Hub's custom status labels (beyond the default Open/In Progress/Completed) map to Asana Custom Fields of type Dropdown so the customer's naming convention is preserved. The Alian Hub task gid maps to a custom field ali_hub_task_id__c for audit trail and cross-reference.

Alian Hub Subtasks map to Asana Subtasks. We preserve the parent-child linkage and original ordering sequence using the Alian Hub sort_order field mapped to Asana's insertion index. Subtasks without a parent task in the source are flagged as orphaned and held in a reconciliation queue for the customer's admin to assign before final import.

Alian Hub Custom Field Manager definitions map to Asana Custom Fields. We detect field type during scoping (text, number, date, dropdown, checkbox, URL) and create the equivalent Asana field type before migration begins. Multi-select dropdown fields in Alian Hub map to Asana enum fields with multiple enum values. Dropdown options with special characters are sanitized per Asana's API character restrictions.

Alian Hub Time Entries (from the Timesheet Management module and desktop time tracker) are migrated as Asana Tasks tagged with a Timesheet project or as notes attached to the relevant task. Native Asana time tracking requires the Timesheets add-on (available on Premium and Enterprise). We document whether the customer has this add-on during scoping and configure the appropriate destination. If the add-on is absent, time entry data is preserved as structured notes with duration, user, and task reference in a machine-readable format.

Alian Hub user accounts map to Asana workspace members by email address. We extract all active users from Alian Hub (accounting for any deactivated accounts due to license downgrade on lower tiers) and match by email to Asana users. Users in Alian Hub without a matching Asana account go to a provisioning queue for the customer's admin before record assignment migration begins.

Alian Hub Channels (project-scoped or topic-based) and 1:1 Chat messages export as structured text. We transform this into Asana Conversation entries attached to the relevant project. Channel message threading is flattened into a single conversation thread per channel because Asana's Conversation model does not support nested sub-threads. Attachments referenced in chat messages are migrated as project attachments with the original message text preserved.

Alian Hub Tags and Labels on tasks and projects map directly to Asana Tags. We preserve the tag name and count exactly. Tag color assignments in Alian Hub do not map to Asana's tag model and are not transferred. Tags used across many records are bulk-created in Asana before the task import phase to avoid tag creation rate-limit errors.

File attachments on tasks and projects are migrated via direct file transfer for self-hosted Alian Hub instances or URL reference mapping for cloud-hosted exports. We flag attachment volume during scoping because large file transfers require bandwidth planning. Image attachments are re-uploaded to Asana's attachment storage; documents are uploaded as file attachments linked to the task or project. The original attachment filename and content type are preserved.

Alian Hub task comments map to Asana Stories on the Task object. We preserve the comment text, author (mapped to Asana User by email), and timestamp. Rich text formatting in Alian Hub comments is converted to Asana's limited HTML subset supported in Stories. Mentions of other users in comments are flagged for manual review because Asana does not auto-resolve cross-system @mentions.

Alian Hub's User Permissions feature (paid tier-gated) defines Admin Insight, Project Manager, and team member roles. We map these to Asana roles: Admin Insight maps to Asana Organization Admin, Project Manager maps to Asana Member with project-level Admin rights, and team member maps to Asana Member. Workspace-level permissions in Asana are set during user provisioning after the role mapping is confirmed by the customer's admin.

Alian Hub notification preferences and history are transient system state and are not migrated. Notification inboxes reset on login to a new system. We document the notification structure in Alian Hub for the customer's admin to use when configuring Asana notification settings post-migration.

Workspace and project settings in Alian Hub are configuration state, not business data. We document the Settings structure during scoping and provide a written configuration guide for reapplying settings in Asana. Examples include default task view preferences, timezone settings, and notification defaults.