Migrate your OmniPlan data

Each .omniplan file is one Project. We extract the project-level metadata (name, start date, calendar, baseline set) as the root container for all child objects during migration.

Tasks map directly as rows with Name, Start/Finish dates, Duration (work-time or elapsed), Predecessors, and custom properties. Subtasks are child tasks with an Outline Level > 1. We preserve the full hierarchy and dependency chain.

Named resources (people, equipment, materials) are extracted with their Max Units, Hourly Cost, and calendar. We preserve resource cost rates for budget calculation in the destination PM tool.

Assignments link a resource to a task with an allocation percentage and effort. The destination PM tool may represent this differently (e.g., Asana tasks vs. MS Project assignments); we map allocation and units to the target's assignment model.

Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish dependencies with lead/lag time are preserved. Lag time is expressed in the same duration format as the task itself.

Milestones are tasks with zero duration. We flag them explicitly in the export so the destination system renders them correctly rather than calculating a default duration.

Hammock tasks derive their duration from child tasks. We flatten this by calculating the actual start/finish dates at migration time and writing a fixed-duration task, since few destination tools support the hammock calculation natively.

Recurrence rules (daily, weekly, monthly, annual) are parsed and expanded into a series of individual task instances. Not all destination tools support recurrence natively; we generate a representative sample and flag remaining instances for manual setup.

OmniPlan Pro supports custom data fields per task or per resource. We extract all custom field names and values and map them to equivalent custom fields in the destination, applying value-type conversion (text, number, date, pop-up) as needed.

Multiple baselines are stored as dated snapshots of the entire schedule. We extract the baseline set name and date and write the baseline task start/finish/duration as custom comparison fields in the destination tool.

Work calendar settings (standard hours per day/week, holidays, exceptions) are extracted and mapped to the destination calendar. Non-standard working time exceptions require explicit re-entry in most destination systems.

Critical path is a computed analysis result, not stored data. It is not migratable as a distinct object; it is recalculated by the destination tool based on task dependencies and durations.

Earned value metrics (CPI, SPI, EV, PV, AC) are calculated from cost and progress data at runtime. The raw task and cost data are migratable; the derived EVA figures are not.

Split tasks have discontinuous work segments. We represent each split segment as a separate task row with a shared grouping identifier, so the destination tool can display them together or reconstruct the split structure.

Cost and effort per resource per task interval are exported from OmniPlan. We map these to the destination's cost tracking model, which may use a different interval granularity or cost-entry mechanism.