Migrate from Planisware Orchestra to Asana

Orchestra Projects map directly to Asana Projects. The project name, description, start date, target end date, and status migrate as text and date fields. Parent-child project hierarchies (subprojects within a master project) map to Asana Portfolio membership or to a parent Project with nested subprojects depending on the depth of the hierarchy. We resolve the Portfolio association at migration time using Orchestra's Program membership data.

Orchestra Activities map to Asana Tasks within the corresponding Project. Start date, end date, duration, and assigned resources migrate to Asana task fields. Dependencies between Orchestra Activities map to Asana dependencies (Finish-to-Start, Start-to-Start) using the Tasks API. Sub-activities map to Asana Subtasks nested within the parent task. Milestone flags in Orchestra map to Asana Milestones.

Orchestra Resources (human assets with capacity, calendars, and cost rates) map to Asana Users by email match. Resource calendars and capacity percentages migrate to custom fields on the User record since Asana does not have a native resource capacity model. Cost rates from Orchestra migrate to custom fields for reporting but are not used in Asana's native calculations. Resources assigned by competency in custom fields map to Asana custom fields that the customer can use for filtering and assignment.

Orchestra Programs aggregate cost, time, and resource data from contributing projects. Asana Portfolios aggregate Project status and progress but do not natively roll up financial data. We migrate the Program-to-Project membership relationship and configure the Asana Portfolio to show contributing Projects by status and timeline. Financial roll-up values from Orchestra (budget vs actuals) are documented in a custom Portfolio-level custom fields table that the customer's admin can populate manually or via a reporting integration.

Orchestra Risks (probability, impact, mitigation) at the project level map to Asana Tasks with custom fields for risk probability (select), impact (select), and mitigation status (text). Cross-project risks stored at the portfolio level map to a dedicated Risk Portfolio Project with tasks representing each risk. The RAID log structure (Risks, Actions, Issues, Decisions) from Orchestra V8 is mapped to a Project with task sections for each RAID type; Asana does not have a native RAID object.

Orchestra financial data (budget, forecast, actuals, variance) has no native Asana equivalent. Asana has no cost, expense, or financial tracking fields. We extract the full financial dataset from Orchestra's OData API, produce a structured CSV of budget vs actuals by project and cost type, and deliver this as a supplemental data export. The customer's admin can import this into a connected BI tool (Power BI, Looker, Google Sheets) for financial reporting. We document the financial object structure so that any future Asana financial integration can reference the correct schema.

Orchestra timesheet entries and actuals migrate to Asana's Time Tracking add-on if the customer has licensed it, or to custom fields on tasks if not. Actual hours logged per activity map to task-level time entries with the date preserved. The approval chain and workflow validation history from Orchestra are not migratable as discrete records; we document the current approval workflow configuration in a written handoff for the admin to reconstruct in Asana Rules.

Orchestra Deliverables tied to phase-gate milestones map to Asana Tasks with Checklist items representing sub-deliverables and approval status. The deliverable approval record migrates as a task comment or custom field. Phase-gate workflow status maps to Asana task status values that the customer's admin configures in the project settings. Deliverable checklists grow to more than 50 items map to multiple Asana sub-tasks to avoid checklist overflow.

Orchestra What-if scenarios and baseline snapshots are live-plan alternatives stored in the in-memory server and do not export as discrete records. We extract the active scenario data and the most recent baseline snapshot and document them in a written scenario inventory that the customer's PMO can use to re-enter key scenario parameters in Asana or a linked planning tool. We flag that Asana does not support scenario comparison or baseline-over-actual tracking natively.

Orchestra document metadata (filename, upload date, associated project and activity) migrates to Asana task attachments. Document binary files are extracted in parallel with the metadata export and re-uploaded to the associated Asana task as file attachments. Access control settings on Orchestra documents do not transfer; we document the access-control configuration for the admin to reapply in Asana. Files stored outside the Orchestra document module (linked via URL) are preserved as URL attachments.

Orchestra custom objects vary per deployment and require pre-migration schema profiling. We extract the full custom object schema including all custom attributes, lookup relationships, and calculated fields. Since Asana does not support custom objects, we deliver a custom object schema document that describes each custom object, its fields, and the recommended Asana equivalent (custom fields on Projects or Tasks, or a separate project used as a registry). The customer's admin rebuilds the data model in Asana using custom fields before importing records.

Orchestra Agile user stories migrate to Asana Tasks within the relevant Project. Story points, acceptance criteria, and story status migrate to custom fields. Orchestra Kanban board layouts, swimlanes, and WIP limits are platform-specific visualization settings that do not export. We migrate the user story content and status and configure an Asana Board view manually post-migration. Burndown chart data from Orchestra is extracted as a CSV for manual entry into Asana or a reporting dashboard.