Migrate from Planisware Orchestra to Microsoft Project

Orchestra Projects map directly to Microsoft Project plan files. The Orchestra project hierarchy (parent-child) translates to Summary Tasks in Microsoft Project with WBS numbering preserved. Project-level fields (name, description, start date, finish date, status) migrate as project summary task fields. We handle the XML namespace differences between Orchestra's OData export format and Microsoft Project's expected .mpp XML schema during the transform phase. Active/inactive status from Orchestra does not map to Microsoft Project task flags natively; we document this as a post-migration configuration step.

Orchestra Activities are the scheduling unit and map directly to Microsoft Project Tasks. Start/end dates, duration, effort, and dependencies migrate. The Orchestra activity ID becomes the Microsoft Project Task ID; the WBS code translates from Orchestra's hierarchical activity numbering. Dependencies between Activities map to Microsoft Project predecessor/successor links with the dependency type (FS, SS, FF, SF) preserved. Milestone activities in Orchestra become milestone tasks in Microsoft Project with zero duration.

Orchestra assigns resources by type rather than by individual competency, which is a known limitation in the source platform. Microsoft Project uses a generic resource pool with assignment units per task. We translate Orchestra resource types into named generic resources in Microsoft Project, creating a mapping table during migration. If the destination requires named individual resources, the customer's admin must provision Microsoft Project resource records and map the generic names to individual assignments post-migration. This translation step is the primary source of post-migration effort in this migration pair.

Orchestra Programs aggregate quantitative data (cost, time, resources) from contributing projects and compare them against program-level targets. Microsoft Project does not have a native Program object. We handle this by creating a master project file (.mppx) or summary task structure that rolls up program-level costs and milestones. The financial roll-up values (budget, forecast, actuals at the program level) migrate as cost fields on the summary task but require manual verification because Microsoft Project does not auto-calculate program-level aggregates from child project costs.

Orchestra tracks budget, forecast, actuals, and variances at the project and portfolio level. Microsoft Project supports cost fields per task (Task Cost, Fixed Cost) and resource rate tables (Resource Standard Rate, Cost Per Use). We map Orchestra cost data to Microsoft Project cost fields, preserving the cost category labels in a custom field. Variance tracking (Budget vs. Actual) maps to Microsoft Project Cost Variance fields if the destination uses earned value tracking. Note that Microsoft Project does not have a native variance dashboard; variance analysis requires manual formula setup or export to Excel.

Orchestra Risks are tracked at project and portfolio levels with probability, impact, and mitigation fields. Microsoft Project has no native risk object. We map Risks to custom Task-level fields (Text or Flag fields) or to Notes attached to the relevant task or summary task. Risk probability and impact values migrate as numeric custom fields. The customer chooses risk visualization strategy during scoping: custom fields with conditional formatting, or a separate risk register maintained outside Microsoft Project.

Actual time logged against Orchestra Activities flows through the timesheet module. We export timesheet entries and map them to Microsoft Project Actual Work and Actual Cost fields on the corresponding task. Actuals at the project level map to project summary task cost fields. Note that timesheet approval chain history (who approved what and when) does not export from Orchestra because it is stored as system-state records; we export the submitted and approved time data only. Post-migration, actuals must be reconciled against the source system before cutover to avoid duplicate entries.

Orchestra Deliverables are tied to phase-gate workflows and represent tangible outputs at project milestones. We map Deliverables to Microsoft Project tasks with milestone markers (zero duration) and a custom field (Text1) carrying the deliverable status (Pending, In Review, Approved). The approval checklist items associated with deliverables do not migrate; we deliver a written inventory of each deliverable's checklist items for manual reconstruction in the destination.

Orchestra supports what-if scenario planning and baseline management at the project level via the Timeshift view. We extract active scenarios and baseline snapshots. Since scenarios in Orchestra are live-plan alternatives (not just a comparison view), and Microsoft Project baselines are simple snapshots of task Start/Finish/Cost at a point in time, we migrate the most recent baseline as a Microsoft Project baseline. Additional scenarios are not transferable; we deliver a scenario inventory document listing each Orchestra scenario with its schedule and resource assumptions for manual reconstruction.

Orchestra document module files cannot be accessed outside the Orchestra interface. We export document metadata (file name, upload date, associated project/activity) and links. Actual binary files require a parallel file-level extraction from Orchestra's document storage and re-association to records in Microsoft Project or a connected SharePoint library. Document access-control settings do not transfer and must be reapplied manually post-migration. We deliver a document manifest listing each file, its original location in Orchestra, and its target location in the destination.

Orchestra allows custom objects and attributes beyond the standard data model, with schemas varying per deployment. We profile the source schema during discovery, map known custom object fields to Microsoft Project custom fields (Text, Number, Date, Flag types) on the appropriate task or resource record. Custom objects that cannot map to Microsoft Project's flat field model are documented in a custom object inventory with recommended SharePoint list or Power Apps backing store as a parallel system.

Orchestra supports Agile delivery with user stories, boards, and burndown charts. Kanban board layouts, swimlanes, and WIP limits are platform-specific visualization settings that do not transfer. We export user story text as tasks with a custom field (Text1) set to User Story. The Agile board configuration is not portable; we deliver a written inventory of board structure, column definitions, and WIP limits for reconstruction in Microsoft Project's task board view or a connected Planner/Teams integration.