Migrate from OmniPlan to monday Work Management

Each OmniPlan .omniplan file maps to a monday.com Board. The project name, start date, and finish date become the board name and the default timeline column values. We create one Board per OmniPlan project during migration. If the customer uses OmniPlan's multi-project dashboard (Pro feature), we create a monday.com Workspace containing all migrated Boards and note the cross-board portfolio grouping in a custom column for the customer's admin to organize into folders.

OmniPlan tasks map to monday.com Items with the full outline hierarchy preserved through Subitems. We preserve OmniPlan's outline level and WBS code in separate custom columns for traceability. Task Name becomes Item Name, Start and Finish dates map to the Timeline column, and Duration in days/weeks is written to a Number column. Work-time versus elapsed-time duration is preserved in a dedicated Select column (options: Work-Time, Elapsed-Time) so monday.com does not recalculate the schedule using only work-day calendars.

OmniPlan milestones (tasks with zero duration) are migrated as Items with the Status column set to a Milestone label (or a dedicated Select column if no Status exists). The milestone date is written to the Timeline Start and End fields. We flag milestones explicitly in the migration transform so the destination does not assign them a default duration, which is a common recalculation error when milestones are imported without an explicit zero-duration marker.

OmniPlan Resources (people, equipment, materials) map to monday.com workspace members. We extract the resource name, Max Units, and Hourly Cost. If the destination workspace already has members matching the resource names, we map by name. If no match exists, we create placeholder entries in a Person column on each relevant board and document the mapping so the customer's admin assigns the correct monday.com User account post-migration. OmniPlan's resource hourly cost rates are stored in a Number column for reference.

OmniPlan resource assignments (which resource is allocated to which task at what percentage) map to the monday.com Person column on the corresponding Item. Allocation percentage from OmniPlan is written to a custom Number column since monday.com's Person column does not natively store allocation percentages. We flag items with over-allocated resources (allocation percentage exceeding 100 percent) in a separate column so the customer's project manager can resolve the over-allocation in monday.com's workload view.

OmniPlan's Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish dependencies with lead and lag time are mapped to the monday.com Dependency column. Monday.com natively supports Finish-to-Start dependency chaining. Start-to-Start, Finish-to-Finish, and Start-to-Finish dependency types are represented using a workaround: a custom Number column holds the dependency type code (FS=0, SS=1, FF=2, SF=3) and lead/lag days are stored in a separate Number column. The customer's admin uses the Dependency column for primary scheduling and the auxiliary columns for reference.

OmniPlan hammock tasks derive their duration from the span between their earliest start and latest finish among child tasks. Monday.com does not support calculated hammock duration natively. We flatten hammock tasks by computing the actual start and finish dates at migration time from the child task data and writing a fixed-duration Item with the derived dates. The Item Name carries a [Hammock] prefix so the customer's admin can identify it. Recalculation after child task changes requires manual update in monday.com.

OmniPlan recurrence rules (daily, weekly, monthly, annual) are parsed and expanded into a series of individual Item instances representing the recurring occurrence pattern. We generate a representative set of occurrences (configurable, default 12 instances) and write each as a separate Item with the recurrence rule stored in a Text column for reference. The customer rebuilds native monday.com recurrences or automation-triggered item creation for ongoing recurring tasks post-migration.

OmniPlan split tasks have discontinuous work segments. We represent each split segment as a separate Item with a shared Grouping ID stored in a Text column. Items sharing the same Grouping ID represent the split task segments and are displayed together in the board using a group-by or filter. The customer can optionally rename or tag these segments for clarity in monday.com's task view.

OmniPlan Pro custom data fields per task are mapped to monday.com custom columns with type matching: text fields to Text columns, numeric fields to Number columns, date fields to Date columns, dropdown lists to Select columns, and checkbox fields to Checkbox columns. We extract all custom field names and values during the export parse and create matching columns in the destination Board before any Item data is written. Multi-select checkbox fields from OmniPlan map to multi-select columns in monday.com.

OmniPlan baseline sets store named snapshots of the schedule (baseline start, finish, and duration per task). We extract the baseline name, date, and the baseline start/finish/duration per task and write them as parallel custom columns in monday.com (e.g., Baseline 1 Start, Baseline 1 Finish, Baseline 1 Duration). Up to three baseline sets are migrated as column groups; additional baselines beyond three require customer admin review to select which to preserve. Monday.com has no native baseline comparison feature; the customer uses chart views or third-party reporting for variance analysis.

OmniPlan work calendar settings (standard hours per day/week, holidays, exceptions) are extracted as structured data. These cannot be written to monday.com because monday.com does not expose a work-calendar API or a per-resource calendar model. We document the work calendar configuration (working days, exceptions, and daily hour bands) in a Text column on the Board for reference, and the customer's admin rebuilds working day settings in monday.com's Board Calendar view manually for each board.

OmniPlan interval cost and effort per resource per task are extracted from the Pro export and written to monday.com as Number columns on the relevant Items. The resource name and interval date are stored alongside the cost and effort values so the customer can reconstruct a cost breakdown in monday.com's chart views. Monday.com does not have a native earned value analysis model; the migrated cost data is informational and requires manual integration with a financial reporting tool for budget tracking.

OmniPlan Pro earned value metrics (CPI, SPI, EV, PV, AC) are runtime calculations derived from task progress, cost, and schedule data. These are not stored as independent records and therefore cannot be extracted and migrated. The underlying task progress and cost data are migratable as custom columns; the customer rebuilds earned value formulas in monday.com using formula columns or connects to a BI tool for EVA reporting.

OmniPlan's critical path is a computed analysis result, not stored data. It recalculates dynamically based on task dependencies and durations. Monday.com does not expose a critical path calculation natively. The customer uses the Dependency column and workload view to identify scheduling constraints and routes critical path analysis through monday.com's chart view or a third-party project analytics integration.