Migrate your Meisterplan data
Portfolio-first PPM software that prices by scheduled resources, not seats. Built for organizations planning medium-to-long-term capacity across project portfolios.
In its favor
Why people choose Meisterplan
The signal that keeps Meisterplan on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Resource-based pricing makes Meisterplan cost-predictable as headcount grows — organizations pay for schedulable capacity, not for every person who logs in.
Scenario Comparison mode lets portfolio managers model two versions of a plan side-by-side in the Gantt and integrated reports, a capability praised in G2 reviews.
Meisterplan's custom project fields support tailored data capture without requiring developer involvement, enabling organizations to adapt the schema to their process.
The platform integrates cleanly with other Meister apps (MeisterTask, MindMeister), giving existing ecosystem customers a familiar UX across planning and execution tools.
Responsive customer support is cited in multiple G2 reviews as a key factor in positive experiences, with quick resolutions to configuration questions.
Resource-centric pricing becomes expensive for large organizations — if most employees do not get booked to projects, the license cost per active resource climbs steeply.
Meisterplan is portfolio planning software, not task management — teams needing day-to-day execution tracking often find a gap between planning and doing.
The tool has a relatively narrow feature scope compared to all-in-one project management platforms, which can create a shadow-IT need for task or document management.
Financial tracking and scenario features require the Pro or Premium edition, making the Basic tier a limited capability product that some customers outgrow.
Some users report the learning curve for resource allocation modeling is steep, particularly when coordinating across multi-project portfolios.
Reasons to switch
Why people leave Meisterplan
The recurring reasons buyers give for replacing Meisterplan. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Meisterplan fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Meisterplan pricing overview
Meisterplan prices exclusively on the number of Resources (schedulable employees), not on the number of Users. Users are free and unlimited. Resources include active employees and planned future capacity. For organizations exceeding 1,000 Resources, custom quotes are available via [email protected]. The three tiers (Basic, Pro, Premium) gate features rather than capacity.
Basic
Tier 1 of 3
Resource-based (custom quote)
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Meisterplan's schedule — see our quote-based pricing →
What gets migrated
Meisterplan object support
Object-by-object support for Meisterplan migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the primary planning unit in Meisterplan. They carry system fields (Total Cost, Status, Approved Effort) and unlimited Custom Project Fields. We migrate all standard system fields and flag any custom fields for value-level mapping at import time.
Scenarios
Fully supportedScenarios represent what-if portfolio snapshots. Scenario Comparison mode (Pro/Premium) lets users compare two scenarios side-by-side. We preserve all scenarios as distinct portfolio states. If the destination lacks a scenario concept, we merge them sequentially with a scenario_label tag on each project.
Resources
Mapping requiredResources are the paid schedulable employees. The distinction from Users is critical: Resources are billable, Users are free and unlimited. We migrate the Resource roster including availability percentages and utilization figures, but we flag the resource-vs-user mapping for explicit customer confirmation before billing boundaries are set.
Users
Mapping requiredUsers are free and unlimited in Meisterplan. We migrate user accounts and their role assignments. Role-based access rights require mapping to the destination's permission model, as Meisterplan's role system is proprietary.
Custom Project Fields
Mapping requiredCustom Project Fields support text, number, date, and choice data types with documented size limits. We retrieve field definitions via the REST API, then perform value-level mapping for each field. Fields that cannot map directly to the destination are flagged for customer review.
Financial Data
Mapping requiredApproved Budget, Plan-Ist comparisons, CapEx/OpEx cost types, and actual financial events are stored per project. Financial Tracker and Cost Type Tracker are Pro/Premium features. We migrate financial figures but flag that Basic edition exports contain no financial data, requiring an edition upgrade before migration scoping.
Milestones
Fully supportedMilestones mark significant points in a project's timeline. We preserve milestone name, date, and associated project linkage. Milestones without a destination-system equivalent are migrated as custom date fields with a 'milestone' type label.
Risks
Mapping requiredRisks are a custom object type with their own set of custom fields. The risk data model is fully configurable per tenant. We retrieve the risk schema via the API, map each risk to the destination's equivalent object, and flag any unmapped custom risk fields.
Programs
Fully supportedPrograms group related projects in Meisterplan. We preserve the program hierarchy and the project-to-program assignments. If the destination has no program concept, we create a Program label on each grouped project.
Actuals
Mapping requiredActual time worked is recorded against projects and rolled up to resource utilization reports. Actual time entries migrate as time-entry records. If the destination does not support time entries, we flag the data for manual re-entry or summarize as a project note.
Finance Categories
Mapping requiredFinance categories allow breaking down costs and benefits by type. We preserve the category definitions and their assigned values. Category mapping to the destination's chart of accounts or cost codes requires customer sign-off.
Portfolio Views
Mapping requiredPortfolio views display projects in Gantt, table, and heatmap formats. We migrate the view configuration including column layout and grouping. Since views are UI artifacts, the migrated config is applied as a suggested starting layout in the destination.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the primary planning unit in Meisterplan. They carry system fields (Total Cost, Status, Approved Effort) and unlimited Custom Project Fields. We migrate all standard system fields and flag any custom fields for value-level mapping at import time. |
| Scenarios | Fully supported | Scenarios represent what-if portfolio snapshots. Scenario Comparison mode (Pro/Premium) lets users compare two scenarios side-by-side. We preserve all scenarios as distinct portfolio states. If the destination lacks a scenario concept, we merge them sequentially with a scenario_label tag on each project. |
| Resources | Mapping required | Resources are the paid schedulable employees. The distinction from Users is critical: Resources are billable, Users are free and unlimited. We migrate the Resource roster including availability percentages and utilization figures, but we flag the resource-vs-user mapping for explicit customer confirmation before billing boundaries are set. |
| Users | Mapping required | Users are free and unlimited in Meisterplan. We migrate user accounts and their role assignments. Role-based access rights require mapping to the destination's permission model, as Meisterplan's role system is proprietary. |
| Custom Project Fields | Mapping required | Custom Project Fields support text, number, date, and choice data types with documented size limits. We retrieve field definitions via the REST API, then perform value-level mapping for each field. Fields that cannot map directly to the destination are flagged for customer review. |
| Financial Data | Mapping required | Approved Budget, Plan-Ist comparisons, CapEx/OpEx cost types, and actual financial events are stored per project. Financial Tracker and Cost Type Tracker are Pro/Premium features. We migrate financial figures but flag that Basic edition exports contain no financial data, requiring an edition upgrade before migration scoping. |
| Milestones | Fully supported | Milestones mark significant points in a project's timeline. We preserve milestone name, date, and associated project linkage. Milestones without a destination-system equivalent are migrated as custom date fields with a 'milestone' type label. |
| Risks | Mapping required | Risks are a custom object type with their own set of custom fields. The risk data model is fully configurable per tenant. We retrieve the risk schema via the API, map each risk to the destination's equivalent object, and flag any unmapped custom risk fields. |
| Programs | Fully supported | Programs group related projects in Meisterplan. We preserve the program hierarchy and the project-to-program assignments. If the destination has no program concept, we create a Program label on each grouped project. |
| Actuals | Mapping required | Actual time worked is recorded against projects and rolled up to resource utilization reports. Actual time entries migrate as time-entry records. If the destination does not support time entries, we flag the data for manual re-entry or summarize as a project note. |
| Finance Categories | Mapping required | Finance categories allow breaking down costs and benefits by type. We preserve the category definitions and their assigned values. Category mapping to the destination's chart of accounts or cost codes requires customer sign-off. |
| Portfolio Views | Mapping required | Portfolio views display projects in Gantt, table, and heatmap formats. We migrate the view configuration including column layout and grouping. Since views are UI artifacts, the migrated config is applied as a suggested starting layout in the destination. |
Gotchas
What to watch for in Meisterplan migrations
Issues we've hit on past Meisterplan migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Resource-based licensing is not user-based
Financial data is absent on Basic edition exports
Custom Project Fields require value-level mapping
REST API lacks a bulk export endpoint
Scenario data structure is destination-dependent
| Severity | Issue |
|---|---|
| High | Resource-based licensing is not user-based |
| High | Financial data is absent on Basic edition exports |
| Medium | Custom Project Fields require value-level mapping |
| Medium | REST API lacks a bulk export endpoint |
| Low | Scenario data structure is destination-dependent |
Leaving Meisterplan?
Where Meisterplan customers move next
5 destinations Meisterplan can migrate to.
How a Meisterplan migration works
Four steps, Meisterplan-specific
Connect
Not publicly documented in the CSV into Meisterplan. Scopes limited to read-only on the data we move.
Map
We translate Meisterplan-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Meisterplan quirks before production.
Migrate
Full migration with Meisterplan rate-limit handling. Rollback available throughout.
FAQ
Meisterplan migration FAQ
Answers to the questions buyers ask most during Meisterplan migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Meisterplan migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Meisterplan.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Meisterplan setup and destination — written quote back within a business day.