Migrate from iPlan to monday Work Management

iPlan Projects map directly to monday.com Boards. The project name, description, status, start date, end date, budget, and owner assignment transfer as Board metadata and column values. We preserve the portfolio hierarchy (which projects belong to which parent portfolio) by creating a Folder structure in monday.com that mirrors iPlan's portfolio grouping. Project status from iPlan (active, on-hold, completed, archived) maps to a Status Column with corresponding values on the destination Board.

iPlan Tasks map to monday.com Items within the target Board. Standard fields transfer as column values: name to Item name, description to Text Column, start/end dates to Date Column, priority to Priority Column (with numeric mapping: Critical=1, High=2, Medium=3, Low=4), and status to Status Column. Custom fields on Tasks map to monday Column types based on field type analysis during scoping: dropdown becomes List Column, numeric becomes Numbers Column, date becomes Date Column, text becomes Text Column.

iPlan Subtasks map to monday.com Subitems attached to the parent Item. The Subitem inherits the parent Item's Board context and can have its own columns, assignments, and due dates. We preserve the parent-child relationship by creating Subitems during migration in dependency-order sequence so the parent Item exists before the Subitem is attached. If the destination monday.com plan does not include Subitems (Basic plan), we flatten Subtasks into a flat Item list with a parent-reference Text Column populated with the parent Item name.

iPlan Milestones map to either a dedicated Status Column value (e.g., a milestone checkbox or milestone label) or a Timeline Column with a milestone marker. We evaluate during scoping whether iPlan's milestone interdependencies (milestones that depend on other milestones) require the Timeline Column approach for visual dependency arrows, or whether a simpler Status Column suffices. Any milestones with no linked tasks are flagged as standalone milestones requiring a separate Board or Group treatment.

iPlan's predecessor-successor dependency relationships map to monday.com's Dependency Column. Each dependency pair (Task A depends on Task B) creates a Dependency Column entry on Task A pointing to Task B. We must resolve Item IDs at migration time before inserting dependency relationships, which requires a two-pass approach: create all Items first with temporary IDs tracked, then update Dependency Column values in a second pass using the resolved Item ID mapping.

iPlan Resources (employees with name, role, and availability schedules) map to monday.com Workspace members. We extract the employee roster from iPlan's Resource table and create corresponding monday.com User accounts, matching by email address where available. Resource availability schedules (capacity percentages, availability calendars) cannot map directly to monday.com because monday lacks native resource management scheduling; we preserve this data as a structured export file for the customer's admin to reference when manually assigning work. Role information migrates as a Text or List Column on Items.

iPlan Timesheet records (hours logged, date, project association, task linkage) map to monday.com Time Tracking Column entries on the linked Item. Each timesheet row creates a Time Tracking entry with the logged hours, date, and user attribution. We resolve the user attribution by matching the timesheet owner to the monday.com User account created from the Resource mapping. Timesheet entries with orphaned project references (no matching monday.com Item) are flagged for manual reconciliation.

iPlan's automated earned-value metrics (planned value, earned value, cost performance index, schedule performance index) derive from timesheet completion and task status. These calculated values cannot migrate directly because monday.com has no native earned-value calculation. We preserve the most recent snapshot values as Number Columns and provide a Formula Column configuration guide for rebuilding the calculations in monday using the formula builder (Pro plan and above). The customer rebuilds the formulas post-migration based on the provided specification.

iPlan billing and financial tracking data exports with invoice amounts, payment status, and project association. These do not map to native monday.com objects because monday.com has no billing module. We preserve the billing data as Number Columns on the relevant Items and create a written reference document mapping each billing record to its source iPlan ID so the customer's finance team can cross-reference. For organizations requiring full billing functionality, we recommend integrating monday.com with a dedicated accounting tool post-migration.

iPlan Project-level custom fields map to monday.com Columns added to the destination Board. We analyze each custom field's data type during scoping: dropdown fields become List Columns, numeric fields become Numbers Columns, date fields become Date Columns, text fields become Text Columns, and checkbox fields become Checkbox Columns. Formula and rollup fields (calculated from other fields) cannot migrate because monday.com does not support calculated fields at the project level; we document the formula logic for manual rebuild in monday's Formula Column on the Items within each Board.

iPlan Task-level custom fields follow the same type mapping as project-level custom fields but attach to individual Items within a Board. We create Board-specific Columns and map the task-level custom field values to the corresponding Column entries for each Item. If multiple iPlan custom fields share the same name but have different types across projects, we flag this for the customer to resolve during scoping.

iPlan Knowledge Base articles export as structured text content. We migrate article text to monday Docs attached to the relevant Board or as Updates on the relevant Items. Article categories from iPlan map to Folder or Label structures in monday Docs. File attachments linked to Knowledge articles are extracted and uploaded to monday.com's file storage area. The inconsistent tagging taxonomy in iPlan's Knowledge Base is preserved as-is and documented for the customer to reorganize post-migration.

File attachments associated with iPlan Projects, Tasks, or Knowledge articles are extracted from the export and uploaded to monday.com's file storage. We attach files to the corresponding Item via the File Column type or as embedded attachments in Item Updates. File names and upload timestamps are preserved. If the destination monday.com plan has storage limits (Basic: 5GB, Standard: 20GB, Pro: 100GB), we flag any large file sets that may require the customer to purchase additional storage or archive historical attachments.

iPlan workflow automation rules encode business logic in a proprietary format that cannot be directly transferred. We extract the rule conditions and actions as human-readable specifications during scoping, documenting the trigger, criteria, and recommended monday.com Automation equivalent. Standard plan and above includes Automation recipes; monday Workflows (the newer infrastructure) is available on Pro and Enterprise. We do not create the automations inside the migration scope; we deliver the specification document for the customer's admin to build in monday's native automation builder.