Migrate from Planisware Orchestra to Trello

Orchestra Projects map to Trello Boards. Each Orchestra project becomes a Trello board with the project name and description transferred. Program-to-Project roll-up relationships from Orchestra have no Trello equivalent; we document the parent Program for each project in the migration manifest so the customer can reference program groupings externally. Project-level budget, forecast, and variance data are exported and listed in the financial-data handoff document for manual re-entry.

Orchestra Activities map to Trello Cards. Each activity maps to a card with the activity name as the card title, start/end dates as the card due date, and the activity description as the card description. Activities with a WBS parent-child hierarchy are flattened: child activities become cards in the same list or a designated child list, with the parent-child relationship preserved in the card name prefix (e.g., '1.2.1 - Activity Name') for manual reorganization into Trello lists if needed.

Orchestra Resources map to Trello Board Members by email match. Resource name, capacity (FTE), and cost rate are exported to a resource-mapping CSV. Trello has no capacity planning or utilization reporting; we map the Orchestra resource cost rate to a Card label (e.g., 'Resource: Senior Developer') so that teams can visually associate work with the original resource. Competency and skill-based assignments from Orchestra do not transfer because Trello only supports member assignment, not competency profiles.

Orchestra Programs aggregate quantitative data from contributing projects and compare them against program-level targets. Trello has no portfolio or program level above Board. We map Programs to Trello Workspaces, creating a workspace per Program and placing the corresponding project boards inside it. Program roll-up financial data (aggregated cost, time, resources against targets) cannot migrate; we export it as a CSV attached to the workspace handoff document for the customer's financial team to reference.

Orchestra Risks with probability, impact, and mitigation fields map to Trello Card Labels. We create a risk-label set (e.g., 'Risk: High', 'Risk: Medium', 'Risk: Low') and apply labels to the cards representing the affected activities. Risk-specific fields (probability percentage, financial impact, mitigation owner) are exported to a risk-register CSV linked from the card description for audit traceability. Cross-project risk aggregation at the program level does not have a Trello equivalent.

Orchestra cost and budget data (budget, forecast, actuals, variances at project and portfolio levels) has no Trello equivalent. Trello has no cost fields, financial tracking, or budget vs. actual comparison. We export the full financial data set as a CSV and deliver it alongside the migration as a financial-data handoff document. The customer re-enters budget and actuals in a spreadsheet or a separate financial tool. We flag which Orchestra cost entries correspond to which migrated cards via a project-activity-cost join key.

Orchestra timesheet entries and actuals flow through the timesheet module and can synchronize with HR and ERP systems. Trello has no timesheet or time-tracking module beyond card checklists. We export timesheet data (hours logged, date, resource, activity) as a CSV and deliver it alongside the migration. The customer can optionally use a Power-Up integration with a time-tracking tool or re-enter actuals manually. Approval workflow history is not accessible as discrete records in Orchestra and cannot be preserved.

Orchestra supports what-if scenario planning and baseline snapshots. Trello has no scenario, baseline, or what-if planning features. We export the active scenario and baseline data as a CSV for the customer's reference. Scenario plan alternatives cannot be represented in Trello; we document the current live plan as the baseline and note any alternate scenario values that should be reviewed post-migration.

Orchestra documents uploaded to the document module are accessible only through the Orchestra interface and cannot be extracted as standalone files via the OData API. We perform a parallel file-level extraction using Orchestra's document download interface, then re-associate files to cards in Trello by matching the document's linked project and activity identifiers to the corresponding board and card. File access-control settings and versioning from Orchestra do not transfer and must be reapplied in Trello manually. Trello enforces a 10MB attachment limit per file.

Orchestra custom object schemas vary per deployment and require pre-migration schema profiling. We identify each custom object, extract its records, and map them to Trello. If the destination is Trello Standard or above (Power-Up enabled), custom fields become Power-Up custom fields. On the Free tier, custom object data becomes card labels with a naming convention (e.g., 'Custom: Vehicle ID - ABC123'). We document the full custom object schema and field type mapping in the schema handoff document.

Orchestra Deliverables tied to phase-gate workflows map to Trello Cards with a checklist sub-structure. Each deliverable becomes a card; phase-gate checklist items become card checklist items with the approval status noted in the card description. Deliverable approval records are exported separately as a CSV because Trello has no native approval workflow. The deliverable-to-activity linkage is preserved via card naming conventions (e.g., 'DEL-001 | Activity Name').

Orchestra supports Agile delivery with user stories, boards, and burndown charts. Trello is natively Kanban-first. Orchestra Agile boards, swimlanes, and WIP limits are platform-specific visualization settings that do not transfer. We export user stories as Cards with labels indicating story points (if used), and we create lists matching the Orchestra board columns (e.g., To Do, In Progress, Done) as the initial board structure. WIP limits and swimlanes are documented for manual configuration post-migration.