Migrate your InLoox data

Projects are the top-level container. We pull name, description, status, start/end dates, custom fields, and the full phase/task tree via the web API. Outlook-stored project references are reconciled against the web API response to avoid duplicates.

Phases are sequenced sub-containers within a project. We preserve phase order, milestone flags, and milestone due dates and map them to the destination's equivalent stage or milestone object.

Tasks and subtasks carry assignees, due dates, priority, completion status, and checklist items. We flatten the subtask hierarchy and reconstruct it in the destination using parent-task ID linkage.

Resources are user assignments on tasks and projects. The mapping depends on whether the destination uses a flat user list or a role-based resource pool. We match by email and flag unmatched assignments for manual resolution.

Billable and non-billable time logs are tied to tasks or projects. We preserve the logged hours, date, user, and optional description. Rate-based billing fields require field mapping to the destination's time entry schema.

InLoox links to SharePoint Online document libraries or file server paths. We export the document URLs and metadata, but file content migration depends on the destination's document management system and access permissions.

Budget data lives in a structured budget section scoped to the project. Not all destination PM tools model budgets identically, so we map budget totals and line items to available custom fields or financial objects in the target system.

InLoox allows custom fields on budgets, documents, line items, and mind maps. Custom field schemas vary by project, so we extract the full field map per project and apply field-level mapping during load.

Gantt task dependencies and date ranges are stored as part of the task object. We extract predecessor/successor relationships and reconstruct the dependency chain in the destination Gantt or schedule view.

Kanban column definitions are project-specific. We export column names and card positions as a structured list and map them to the destination's board columns, noting where column counts differ.

Mind maps are stored as a proprietary structured format in InLoox. No standard export endpoint exists and the format is not publicly documented. We do not migrate mind map nodes; we flag their existence and recommend exporting as a screenshot before migration.

Inline checklists on tasks are stored as structured list items. We extract every checklist entry, its completion state, and parent task association and map them to the destination's checklist or to-do sub-object.

Departments and departmental permissions control visibility. We extract the department tree and permission mappings but permission structures often do not translate directly to other platforms and require manual post-migration configuration.

Custom project roles (up to 10 on Enterprise/Unlimited) define what a user can do within a project. Role definitions vary significantly across PM platforms; we map named roles to the closest available role in the destination or fall back to a generic contributor role.

Risk management objects include risk title, description, probability, impact, and status. We extract all risk fields and map them to the destination's risk or issue object, noting where probability/impact rating scales differ.