Migrate from Meisterplan to Asana

Meisterplan Projects map directly to Asana Projects as the primary organizational unit. All standard system fields (Total Cost, Status, Approved Effort) migrate as custom fields on the Asana project. We resolve the Program hierarchy before importing so that each project is assigned to the correct Asana Team or Portfolio grouping. If the customer uses project type categorization, we map Project Types to Asana Custom Fields on the project.

Meisterplan Scenarios are named portfolio snapshots used for what-if comparison. Asana has no native scenario concept. We migrate each Scenario as a distinct tagged set of projects, adding a scenario_label custom field to every project in the set. If the customer requires side-by-side scenario comparison in Asana, we recommend copying each scenario's projects into a dedicated Asana Project Group and using the Portfolio view to compare across groups. The Scenario Comparison mode (Pro/Premium) does not migrate as a feature.

Meisterplan Resources are the schedulable paid employees. They map to Asana Users with their availability percentages and allocation assignments reconstructed as Asana task assignments in the Workload view. The critical migration variable is the Resource count: we identify every Resource in the source export, confirm which should become active Asana Users versus passive stakeholders, and flag the cost impact of each active seat in Asana. A Resource on Basic who is not a project assignee may not need an Asana seat.

Meisterplan resource allocations (percentage of capacity assigned to a project per time period) have no direct Asana equivalent. We reconstruct allocations as Asana task assignments with start dates and due dates, and populate the Asana Workload view with capacity estimates so that project managers can see utilization. If the customer requires exact percentage-based allocations, we store the allocation_percentage as a custom field on the relevant tasks. Utilization percentages from Meisterplan migrate as reference data in a custom number field.

Meisterplan Users (free and unlimited) map to Asana Users. Role-based access rights in Meisterplan (Viewer, Resource, Admin) map to Asana Member roles per Team. We match Users by email address and flag any Meisterplan User who has no corresponding Asana account for the customer's admin to provision. Note that Asana requires a paid seat for any User who needs to be assigned tasks or access the workspace.

Meisterplan Custom Project Fields (text, number, date, single-select, multi-select, checkbox, currency, URL) map to Asana Custom Fields on Projects. We retrieve the full tenant-specific field schema via the Meisterplan REST API and build a field-by-field mapping table during scoping, validated by the customer before import. Asana enforces a 100 Custom Field limit per organization, so we flag this constraint at scoping if the source schema exceeds it.

Meisterplan Milestones (named dates marking significant points in a project's timeline) map directly to Asana Milestones on the corresponding Project. We preserve milestone name, date, and project linkage. Milestones without a specific date in Meisterplan migrate as milestones with a placeholder date that the customer adjusts in Asana after migration.

Meisterplan Programs group related projects in a hierarchy. Asana has two applicable constructs: Asana Portfolios (Business tier) aggregate projects across Teams for portfolio-level visibility, and Asana Teams provide a grouping layer within a Workspace. We map Programs to Portfolios if the customer has Asana Business, or to Asana Teams if on a lower tier. Project-to-program assignments migrate as Portfolio membership or Team membership.

Meisterplan Risks are a configurable custom object with their own set of custom fields (risk_name, impact, probability, mitigation). Asana has no native Risk object. We migrate Risks as a custom field set on the relevant Project (risk_name, risk_impact, risk_probability, risk_status, risk_mitigation as custom text or select fields) or as tagged subtasks on a dedicated Risk Register task within each project. The customer chooses the strategy during scoping.

Approved Budget, Plan-Ist comparisons, CapEx/OpEx cost types, and cost-at-completion are Pro and Premium features only in Meisterplan. Asana has no native financial tracking. We migrate financial figures as custom number fields on each Asana project (approved_budget, plan_cost, actual_cost, capex_amount, opex_amount, variance). These are reference fields only; Asana does not trigger budget alerts or calculate Plan-Ist variance automatically. Customers relying on live financial reporting should maintain a financial system of record and treat Asana figures as static snapshots.

Actual time worked recorded against projects in Meisterplan Pro/Premium migrates as time tracking entries or as custom number fields on the relevant tasks. If the destination Asana workspace uses Asana's native time tracking (available via integrations or Asana's built-in time tracking beta), we populate the entries against the corresponding tasks. If not, we store total_actual_hours as a custom field on each task for reference.

Finance categories in Meisterplan allow breaking down costs and benefits by type (e.g., labor, materials, overhead). We migrate category definitions as custom select fields on projects and assign the relevant category values to each project. If the customer requires cost-code tracking, we map categories to Asana Tags for cross-project reporting in the Portfolio view.

Meisterplan Portfolio Views (Gantt, List, heatmap, resource utilization) are UI artifacts with column layouts and grouping configurations. We migrate the view schema — which fields appear in which column, grouping hierarchy, and sort order — as a written specification document for the customer's admin to rebuild in Asana. The actual view configurations do not transfer because Asana's view model is different.