Migrate from OmniPlan to Trello

Each OmniPlan .omniplan file maps to one Trello board. We extract the project name, start date, and baseline metadata as board description fields. Because Trello boards do not have a native start date, we write project_start and baseline_set fields into a Board-custom Power-Up or as a pinned card with this metadata for admin reference. Multi-project portfolios create multiple boards, optionally grouped within a Trello Workspace.

OmniPlan tasks and subtasks (outline level >1) map to Trello cards. Task Name becomes the card title. Start/Finish dates migrate as a custom Start Date field and the card Due Date respectively. Subtasks become Trello checklist items on the parent card, preserving the hierarchical relationship. Milestones (zero-duration tasks) receive a Milestone label and are placed in a dedicated Milestones list for visual distinction.

OmniPlan's Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish dependencies with lead/lag time cannot map 1:1 to Trello's Card Connections (which only support a basic blocking relationship). We model all dependencies as Trello Card Connections using a pre-migration Power-Up such as Planyway or a custom script. The dependency type (FS, SS, FF, SF) and lead/lag time are written as custom fields on the blocking card for admin reference. Lag time expressed in work-time or elapsed-time carries the same duration-type flag we extract from OmniPlan.

OmniPlan named resources (people, equipment, materials) with Max Units and hourly cost are mapped to Trello Members. We match by resource name to an existing Trello Workspace member or invite the resource as a new member during migration. Resource cost rates do not have a native Trello home; we write them to a custom Resource_Cost_Rate__c field if the customer requires budget tracking. Max Units (e.g., 0.5 for a half-time resource) cannot be represented natively in Trello; we document the allocation percentage in a Resource_Units__c field for manual scheduling reference.

OmniPlan resource assignments (linking a resource to a task with an allocation percentage) map to Trello card assignees. A task with three assigned resources creates one Trello card with up to three Member assignments. The allocation percentage is written to a custom Assignment_Pct__c field on the card. If a resource has an allocation above 100 percent in OmniPlan (over-allocation), we flag the card with an Overallocated label and include the violation in the pre-migration resource report.

OmniPlan milestones are zero-duration tasks. We create a Trello card titled with the milestone name, set a Milestone label, and write the milestone date to the card's Due Date. The milestone is placed in a dedicated Milestones list within the board. We preserve the milestone's predecessor information as Card Connections if applicable.

Hammock tasks derive their duration from child task start/finish dates in OmniPlan. We calculate the actual start (earliest child start) and finish (latest child finish) at migration time and write a fixed-duration card in Trello. The hammock designation is preserved in a custom Hammock_Task__c checkbox field. Trello has no native hammock calculation; the customer rebuilds this logic manually or via a Power-Up if the hammock relationship must stay live.

OmniPlan work calendar settings (standard hours per day, holidays, exceptions) affect how work-time duration is calculated. We extract the work calendar and write non-standard working time as Trello custom fields (e.g., Holiday_Override__c) on affected cards. Full work calendar rebuild (standard hours, exception rules) requires a Trello Power-Up such as Planyway or a manual calendar reconfiguration by the customer's admin.

OmniPlan Pro custom data fields (text, number, date, currency, dropdown) map to Trello custom fields of the corresponding type. We extract the field name, type, and all values from the OmniPlan export and create matching Trello custom fields on the destination board before card import. Picklist values from OmniPlan become Trello dropdown custom fields with the same options.

OmniPlan baselines store dated snapshots of task start/finish and duration. We extract the baseline name, date, and per-task baseline values and write them as custom fields on each card: Baseline_Start__c, Baseline_Finish__c, and Baseline_Duration__c. Trello has no native baseline view; the customer compares planned vs. actual dates manually in the card detail view or via a reporting Power-Up.

OmniPlan recurrence rules (daily, weekly, monthly, annual) are parsed and expanded into individual task instances at migration time. Trello does not have a native recurrence feature in Standard or Premium tiers. We generate one representative card per recurrence series with a Recurrence_Rule__c field documenting the original pattern, and the customer's admin rebuilds recurrence via Butler automation or a dedicated Power-Up if needed.

Critical path is a computed analysis result in OmniPlan, not stored data. It recalculates based on task dependencies and durations. Trello has no native critical path feature. We do not migrate critical path as a distinct object. After migration, the customer uses a Trello Gantt Power-Up (e.g., Chrono Gantt, TeamGantt) or a separate tool to recompute critical path from the migrated dependencies and durations.

OmniPlan's earned value metrics (CPI, SPI, EV, PV, AC) are calculated from task cost and progress data at runtime. The raw task, resource, and cost data migrate to Trello; the derived EVA figures do not because they require a schedule-based calculation engine that Trello does not have. We preserve the cost and effort data so the customer can re-enter EVA figures in a spreadsheet or a dedicated EVA tool post-migration.

OmniPlan split tasks have discontinuous work segments. We represent each split segment as a separate Trello card with a shared custom field Split_Group_ID__c linking them. The cards are placed in the same list to signal their relationship. The customer rebuilds split task visualization in a Gantt Power-Up or documents the splits manually.