Migrate from InLoox to Microsoft Project

InLoox Projects map directly to Microsoft Project project files or Project for the Web project records. We extract project name, description, status, start date, end date, and custom fields. InLoox project-level custom fields map to Microsoft Project enterprise custom fields (if using Project Web App) or project-level custom fields. Project grouping, if used (InLoox project groups), maps to a summary project or a folder convention in the destination.

InLoox phases are sequenced sub-containers within a project. We preserve phase order, milestone flags, and milestone due dates. Milestone-flagged phases map to Microsoft Project milestone tasks (zero-duration tasks with a milestone marker). Summary tasks are created using the InLoox phase name with the phase's child tasks indented beneath it. Phase-level custom fields map to summary task custom fields.

InLoox tasks and subtasks carry assignees, due dates, priority, completion status, and checklist items. We preserve the task hierarchy using WBS numbering and outline level in Microsoft Project. Subtask indentation reconstructs the parent-child relationship. Task-level custom fields migrate to the corresponding Microsoft Project task custom fields. Constraint dates from InLoox (Start No Earlier Than, Finish No Later Than) map to Microsoft Project task constraint types.

InLoox stores Gantt task dependencies as predecessor-successor properties within the task object. We extract every predecessor relationship (task ID, dependency type, lag or lead time) and reconstruct the chain in Microsoft Project using the Predecessors field with FS (Finish-to-Start), SS, FF, or SF dependency type notation. Lag time converts to the Lag field in days or hours. If InLoox constraint dates do not align with the calculated forward schedule from predecessor links, we flag the conflict for manual resolution.

InLoox resources (user assignments on tasks and projects) map to Microsoft Project resources. We match by email address. Resource name, email, and role (if present) migrate to the Resource Name, Initials, and Group fields in Microsoft Project. If InLoox resource rates or cost-per-hour values exist, these map to the resource Rates table in Microsoft Project. InLoox custom project roles (up to 10 on Unlimited) map to the Resource Group or Notes field as there is no direct role object in Microsoft Project desktop; Project Online PWA supports enterprise resource plan roles if that is the destination.

InLoox billable and non-billable time logs tied to tasks or projects migrate to Microsoft Project as assignment-level work values. The logged hours, date, user, and description map to the Assignment Work field. Microsoft Project does not have a dedicated time-entry object, so time logs appear as work hours against the task assignment in the Task Usage view. Billable rate fields from InLoox map to the Assignment Cost field if resource rates are set. We preserve the InLoox time-entry description in the Assignment Notes field.

InLoox links to SharePoint Online document libraries or file server paths migrate as hyperlinks in Microsoft Project. If the destination environment uses SharePoint or OneDrive (common with Project Online), we map the InLoox document URL to a SharePoint hyperlink on the relevant task or summary task. File content itself does not migrate; only the URL reference is preserved. Document metadata (version, author, date) migrates as task-level or project-level custom fields if the destination supports them.

InLoox budget totals and line items (scoped to the project) require field mapping to Microsoft Project because Project does not have a native budget object. We map InLoox budget totals to a project-level custom Cost field and individual budget line items to task-level cost fields where applicable. Currency fields from InLoox map to Microsoft Project's currency display settings. If the destination is Project Online with PWA, budget fields map to the Cost Type and Budget columns in the Project Web App.

InLoox risk objects include title, description, probability, impact, and status. These map to a set of custom fields on the relevant task (Risk Probability, Risk Impact, Risk Status) plus the task Notes field for the full risk description. Probability and impact numeric values migrate as integer or decimal custom fields. If the destination is Project Online with Project Web App, risks can be tracked in the built-in Issues and Risks feature of PWA, which we configure during schema setup.

InLoox inline checklists on tasks store each entry with its completion state. We extract every checklist item, its completion status, and parent task association. Completed items migrate as checked markdown in the Microsoft Project task Notes field. For open checklist items, we create a custom Text1 field with a delimited list of remaining items. The Notes approach preserves the human-readable structure; a structured custom field approach is available if the customer's PMO prefers column-based visibility.

InLoox Kanban column definitions are project-specific with column names and card positions. Microsoft Project (desktop and PWA) does not have a native Kanban view. If the destination is Microsoft Project for the Web / Planner Premium, we map Kanban column names to Planner bucket names and preserve card position as task order within the bucket. We document the column count and card distribution for the customer's admin to verify post-migration. Kanban does not migrate to Microsoft Project desktop.

Mind maps are stored in a proprietary structured format in InLoox with no public API endpoint and no standard export format. We detect mind map nodes during data extraction and flag their existence in the migration report. We do not migrate mind map nodes; we recommend the customer capture screenshots or exports manually before the migration window. This exclusion is documented in the handoff report.