Migrate from Planisware Orchestra to monday Work Management

Planisware Orchestra Projects map directly to monday.com Boards. The Project name becomes the Board name, project start and end dates map to the Board's Date range column if configured, and project status maps to a Status column on the Board's primary group. We extract any project-level custom attributes as custom columns on the destination Board. Active vs archived status is preserved by setting the destination Board to Active or moving archived Projects to an Archive Board structure.

Orchestra Activities map to monday.com Items within the destination Board. Start date, end date, duration, and dependencies migrate to monday.com Date columns, Duration columns, and Dependency columns respectively. Activity-level custom attributes become custom columns on the Item. The parent Activity hierarchy (parent-child activity breakdown) is preserved by mapping top-level Activities to Groups and sub-Activities to Items within each Group, or by using a Subitems structure if nesting depth is required.

Orchestra Resources (human assets with capacity, calendars, and cost rates) map to monday.com Person columns on Items. We extract the resource master including role, department, and calendar availability. Resource capacity in FTE or hours per period maps to a Number or Workload column on a Resource board if the customer needs capacity visibility in monday.com, since monday.com's native workload view requires Pro tier and does not support cross-project aggregation without manual configuration.

Orchestra Programs aggregate cost, time, and resource data from contributing Projects with program-level targets and roll-up reporting. Monday.com has no native Program object. We offer two migration strategies: Group-based (Programs become top-level Groups in a Portfolio Board with contributing Projects as Groups within them, using formula columns for roll-up) or cross-board Link (Programs become a Program board, Items represent each Program, and cross-board Links connect to the contributing Project boards. Roll-up formulas require manual configuration in monday.com since it lacks native aggregation across boards.

Orchestra Risks tracked at project and portfolio levels with probability, impact, and mitigation fields migrate to Items in a dedicated monday.com Risk board. Probability and impact values map to Number or Slider columns. Risk status (Open, Mitigating, Closed) maps to a Status column. Cross-project risk registers are consolidated into a single Risk board with a Project Name column identifying the originating project, since monday.com does not have a native risk object. Mitigation actions and owners migrate as text and person columns respectively.

Orchestra financial data (budget, forecast, actuals, and variances at project and portfolio level) migrates to monday.com Number columns and Formula columns. Budget, forecast, and actuals migrate as Number columns. Variance is computed in monday.com using Formula columns (Forecast minus Actuals for cost variance, for example). We flag that monday.com does not support multi-period financial modeling, ERP sync, or native currency conversion; customers needing these capabilities should configure a third-party financial integration or accept column-based tracking as the destination model.

Timesheet entries and actuals logged against Orchestra Activities migrate to monday.com Time Tracking columns on Items. We extract the date, hours logged, and resource reference for each timesheet entry and write them as time records linked to the corresponding Item. Orchestra's timesheet approval workflow history (approval chain and workflow validation records) does not export as discrete API objects; we migrate the submitted and approved time data only and recommend documenting the current approval workflow configuration separately for reconstruction in monday.com automations.

Orchestra Deliverables tied to phase-gate workflows with status, associated checklist items, and approval records migrate to monday.com Items within a Deliverables board or as Items within each Project board. Deliverable status maps to a Status column. Checklist items migrate as Subitems or as a Checkboxes column on the Item. Approval records are not structurally available in Orchestra's API; we extract deliverable status and note the approval flag as a text field.

Orchestra What-if scenarios and baseline snapshots are live-plan alternatives stored as business-rule-driven calculated values. Monday.com has no scenario planning or baseline management feature. We extract active scenario data (resource allocations, schedule changes, financial projections) as of the migration date and write it to a Scenarios board as read-only Items for reference. The customer's admin can use board duplication as a manual scenario-building workaround, but no comparison or rollback capability exists in monday.com natively.

Orchestra documents are accessible only through the Orchestra interface and cannot be retrieved as standalone files via the API. We extract document metadata (filename, upload date, associated project or activity reference) and perform a parallel file-level extraction if the customer has file-level access. In monday.com, files attach to Items via the File column. We re-associate file metadata to the corresponding Items during migration. Document access-control settings from Orchestra do not transfer and must be reapplied manually in monday.com's sharing settings.

Orchestra custom object schemas vary per deployment and require pre-migration schema profiling. Custom objects migrate to monday.com Items in dedicated boards. If the customer is on monday.com Enterprise, we can use monday.com Custom Objects (developer-built via the Developer Center) for schema-persistent entities that need to exist outside a board context. Standard custom attributes (text, number, date, dropdown) map to equivalent monday.com column types. Complex business-rule-driven calculated fields in Orchestra do not migrate; we document the logic for manual reconstruction in monday.com formula columns or automations.

Orchestra Agile artifacts (user stories, Kanban boards, burndown charts) export via the API, but Kanban board layouts, swimlanes, and WIP limits are platform-specific view configurations that do not transfer. We migrate user stories as Items in an Agile board using the Story point or Effort column for sizing. The Kanban view is enabled manually in monday.com (it is a view option on any board, not a separate object). Burndown charts require manual setup via monday.com's Chart view or a third-party widget. SAFe or hybrid delivery framework artifacts have no native monday.com equivalent.