Migrate from OnePlan to monday Work Management

OnePlan Plans map to monday.com Boards. Each Plan type (Program, Project) becomes a separate Board with its own Groups and column structure. The migration must provision destination Boards before migration begins because the OnePlan-monday.com integration explicitly cannot create new boards; we handle board creation via monday.com API during the setup phase. Plan metadata (description, start date, target date) maps to Board-level fields.

OnePlan Work Plans map to Groups within monday.com Boards. A single Plan containing multiple Work Plans splits into multiple Groups on the target Board. We preserve the Work Plan name as the Group name and use the WBS field from OnePlan to populate Group Position for ordering. Empty Work Plans are excluded per OnePlan's documented behavior.

OnePlan Tasks migrate to monday.com Items within their parent Group. Task name, description, start date, due date, assignee, priority, and status map to corresponding monday.com column types. Subtasks in OnePlan map to Subitems on the parent Item. We note that imported Items do not auto-reschedule in monday.com the way OnePlan schedules recalculate in its UI.

OnePlan task dependencies migrate to monday.com Dependencies, but are restricted to Finish-to-Start relationships per monday.com API constraints. Dependencies of type Start-to-Start, Finish-to-Finish, or Start-to-Finish cannot be represented and are flagged in the pre-migration field mapping document for the customer's admin to resolve manually post-migration or accept as lost constraint logic.

OnePlan Resources map to monday.com Workspace Members. We resolve by email match against the monday.com destination workspace. Any OnePlan Resource without a matching monday.com User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

OnePlan Resource Allocations represent capacity assignments against tasks. We map the allocation percentage to a numeric column on the Item and the assigned resource to the monday.com Assignee field. Time-phased resource allocation over time (Resource Plan Data) is not natively representable in monday.com and is flagged as a gap in the mapping document.

OnePlan's financial plan data (budget, actuals, forecast by period) has no direct monday.com equivalent. We map budget amounts to numeric columns and advise grouping by period in a separate Board view or dashboard rather than as time-phased rows. The customer chooses between a budget summary Board or external financial reporting integration during scoping.

OnePlan Risks migrate as monday.com Items with a Status column value of Risk or a tag applied. Risk-specific fields (probability, impact, mitigation) map to available column types (number for probability/impact, text for mitigation notes). monday.com does not have a native Risk object; the mapping is representational.

OnePlan Issues migrate as monday.com Items with a Status column value of Issue or a tag applied. Issue-specific fields (priority, owner, resolution) map to available column types. Like Risks, Issues are represented as tagged Items rather than a native entity.

OnePlan custom fields of type Text, Date, Number, Currency, Yes/No, and Choice map to equivalent monday.com column types (Text, Date, Numbers, Currency, Checkbox, Dropdown). We validate each custom field against monday.com's supported column types before mapping and flag any that require type conversion.

OnePlan custom fields of type User (referencing a person) map to monday.com People columns. We resolve the user reference by email against the monday.com workspace members. If the referenced user does not exist in monday.com, the field is left blank and flagged in the reconciliation report.

OnePlan Plan Details form data attached to a Plan migrates as columns on the Board-level or as Item columns depending on whether the form applies per-plan or per-work plan. Custom form layouts are not migratable; we document the field mapping and the customer recreates the layout in monday.com Board settings.

OnePlan Areas (top-level organizational units) map to monday.com Workspaces. If the customer uses multiple Areas to segment portfolios, we create corresponding monday.com Workspaces and nest Plans within them. The customer may alternatively choose a single Workspace with Board-based segmentation depending on team structure.

OnePlan document attachments are outside the scope of the Migration Tool and have no direct monday.com equivalent. We flag this gap and recommend a separate document migration using SharePoint file storage or monday.com's native file upload (Files column type) as a parallel workstream. No attachment records are migrated.

Stage Gate workflow configurations are system-level settings in OnePlan and are not exportable via the CSV Migration Tool. monday.com's automation model is different (trigger-action rather than gate-based), so these cannot be mapped as code. We deliver a written inventory of each Stage Gate configuration with its stages, gates, and conditions for the customer's admin to rebuild in monday.com Automations.