Migrate from InLoox to Asana

InLoox projects map to Asana projects as the top-level container. We extract name, description, status, start/end dates, and project-level custom fields. InLoox project privacy and department visibility settings are noted during discovery and mapped to Asana team membership and project sharing rules. Projects with no explicit team assignment default to the migration workspace.

InLoox phases (sequenced sub-containers with milestone flags) map to Asana sections. Phase ordering is preserved as section sequence order within the project. InLoox milestones with due dates map to Asana milestones with the milestone checkbox enabled. Phase-level custom fields migrate as section custom fields if supported by the destination tier, otherwise noted as a post-migration gap.

InLoox tasks map to Asana tasks with assignees, due dates, priority, and completion status preserved. Subtasks are flattened and reconstructed in Asana using parent-task ID linkage. Task-level custom fields map to Asana custom fields scoped per project. Gantt predecessor/successor dependencies from InLoox migrate as Asana dependencies (finish-to-start, start-to-start, finish-to-finish, start-to-finish); see the gotcha on Asana dependency bugs with complex chains.

Billable and non-billable time logs (hours, date, user, description) migrate as custom number or duration fields on the parent Asana task. If the destination Asana workspace is on Business or Enterprise, we configure the native time tracking add-on and map time entries to that model. Rate-based billing fields require custom field mapping to a currency or number field. Time entry totals per project are aggregated into a project-level custom field.

InLoox budgets are structured budget sections scoped to the project with totals and line items. Asana has no native budget object, so we map budget totals to a project-level custom number field and individual line items to task-level or section-level custom fields. The customer specifies during scoping whether budget data should be visible on individual tasks or only at the project summary level. Budget metadata (currency, cost center, fiscal period) maps to additional custom text or date fields.

InLoox custom fields are defined per project and optionally scoped to specific areas (budgets, documents, line items). We extract the full per-project custom field schema during discovery, build a field map for each project individually, and apply field-level mapping during load. Asana custom fields are created per project (or as workspace-level fields) to match the InLoox definitions. Field type mapping: InLoox text, number, date, dropdown, and checkbox types map directly to equivalent Asana custom field types. Multi-select dropdowns map to Asana multi-select. Boolean fields map to Asana checkbox or enum depending on use.

InLoox Kanban column definitions are project-specific. We export column names and card positions as a structured list and map them to the Asana board view columns. Column count limits and WIP (work-in-progress) limit fields may not translate directly; we note these as configuration gaps for the customer's admin. Card order within columns migrates as task order within the mapped Asana section.

InLoox Gantt task dependencies (predecessor/successor) and date ranges are stored as part of the task object. We extract the dependency chain and reconstruct it in Asana using the dependency API (add dependency, predecessor, successor endpoints). The Asana timeline view renders the chain visually. Asana's timeline is not a traditional Gantt chart with built-in critical path calculation; we document this limitation in the migration report.

InLoox document links reference SharePoint Online document libraries or file server paths. We export the document URLs and metadata (filename, last modified, author). Asana attachments link to Google Drive, Dropbox, or uploaded files. SharePoint links migrate as URL custom fields rather than native attachments since Asana does not have native SharePoint integration. The customer may need to re-link documents if SharePoint permissions are not shared externally.

InLoox resources are user assignments on tasks and projects. We match by email against the Asana workspace member list. Unmatched assignees go to a reconciliation queue for the customer's admin to provision Asana accounts. InLoox project roles (up to 10 customizable roles on Unlimited) do not map directly to Asana's member-permission model; we document role definitions for the admin to reconfigure as project privacy settings and task-level assignees.

Inline checklists on InLoox tasks are stored as structured list items. We extract every checklist entry, its completion state, and parent task association. In Asana, we map these to either Asana checklist items (on the task) or subtasks, depending on whether the checklist items represent simple flags or sub-tasks with their own assignees and due dates.

InLoox departments control visibility and permissions at the project level. Asana uses Teams as the organizational unit, with project sharing rules determining access. We extract the department tree during discovery and map department hierarchies to Asana Teams and project-team assignments. Custom permission levels per InLoox department may require post-migration admin configuration in Asana.