Migrate from InLoox to monday Work Management

Each InLoox Project maps to one monday.com Board. The InLoox project name becomes the Board name; description, start date, and end date become Board-level fields. Project status (active, on hold, completed, archived) maps to a Board status column or Board archive state. We set up the Board structure (Groups, core columns) during the initial board creation mutation before loading any Items.

InLoox Phases within a Project map to monday.com Groups within the corresponding Board. Phase ordering is preserved by setting the Group's position index during creation. Milestone flags on InLoox Phases map to a dedicated Milestone status label on the Group's header or a separate Milestone checkbox column on the first Item in each Phase Group. Milestone due dates migrate to a Date column on the milestone Item.

InLoox Tasks map to monday.com Items within the appropriate Group. Task name becomes Item name; description migrates to the Item's Text column or Description field; due date maps to a Date column; priority maps to a Priority or Status column with label mapping (High, Medium, Low). We preserve the InLoox task status (open, in progress, completed) by mapping to a monday.com Status column with equivalent labels.

InLoox Subtasks nested under a Task map to monday.com Subitems on the corresponding Item. Subtask name becomes Subitem name; completion state maps to a checkbox or Status column on the Subitem. Subitems are created after their parent Item is confirmed in monday.com, using the Item's monday_id as the parent_id reference in the subitem mutation. InLoox's unlimited subtask depth flattens into monday.com's single-level Subitem nesting, which is a structural limitation the customer acknowledges during scoping.

InLoox Resources are named user assignments on Tasks and Projects. We extract all distinct resource email addresses from InLoox and resolve them against the monday.com workspace Members list. Matched users become Person column values on the corresponding Items. Resources without a matching monday.com user are held in a reconciliation queue for the customer's admin to provision before migration. InLoox's capacity and utilization fields (resource management on higher tiers) have no direct monday.com equivalent and are documented as a post-migration gap.

InLoox Time Entries (date, duration, billable flag, description, rate) map to monday.com's native Time Tracking column if available on the destination tier, or to custom Number and Date columns. The InLoox billable flag maps to a Checkbox column. We preserve the original hours, date, user, and description. If the customer requires detailed time reporting across multiple items, we recommend installing the monday.com Time Tracking integration app as part of post-migration setup.

InLoox custom fields are scoped per-project and per-area (budgets, documents, line items). We extract the per-project custom field definitions during discovery, map each InLoox field type (text, number, date, currency, dropdown) to the closest monday.com column type, and create columns on the destination Board before loading Items. This per-project field discovery adds iteration time compared to platforms with global field schemas. We document any InLoox custom field types that have no monday.com equivalent (e.g., multi-select from a budget-specific lookup) and propose a workaround column configuration.

InLoox Budget data (budget totals, line items with amounts, variance) is scoped to the project budget section. monday.com has no native budget object. We map budget totals to a Currency or Number column and budget line items to a separate sub-board or a linked Item group, depending on the customer's reporting requirements. Budget metadata (cost center, fiscal period) migrates as additional custom columns. The customer should evaluate whether a dedicated finance integration (e.g., a budget-tracking app from the monday.com marketplace) is needed post-migration.

InLoox Gantt task dependencies (predecessor/successor relationships) and date ranges map to monday.com's Timeline column (date range per item). Dependency arrows from InLoox have no native equivalent in monday.com; we document the dependency chain as a text field on each Item and recommend the monday.com Dependencies app (or a third-party Gantt integration) to reconstruct the dependency visualization in the destination. This is a known functional difference the customer accepts during scoping.

InLoox Kanban column definitions are project-specific. We export column names, column order, and card positions as a structured list and map them to monday.com Groups within the Board. If InLoox Kanban columns represent task status (not phase order), they alternatively map to a Status column on Items rather than separate Groups, which is the more common monday.com pattern. We clarify the customer's intended use during scoping to choose the correct mapping strategy.

InLoox document links to SharePoint Online or file server paths are stored as URLs. We export the document URLs and map them to a URL column or Files column in monday.com. Actual file content migration depends on SharePoint API access and is scoped separately. If InLoox documents are stored in SharePoint, we recommend a SharePoint-to-monday.com integration post-migration rather than attempting to copy file content during data migration.

InLoox inline checklists on Tasks are stored as structured list items with completion state. For short checklists (under 10 items), we map to monday.com Subitems with a checkbox column. For longer or more complex checklists, we recommend creating a separate Checklist app from the monday.com marketplace and document the setup as a post-migration configuration step.