Migrate from Meisterplan to Jira

Meisterplan Projects map to Jira Epics within the destination Jira Project. Project name becomes Epic summary, start and end dates migrate to Epic start and due date fields (custom date fields), and Total Cost migrates as a custom number field. Status mapping (In Planning, Active, On Hold, Completed) translates to Epic status workflow states. If the portfolio has multiple Jira-target systems, we use JQL queries to scope which epics land in which Jira Project during migration.

Meisterplan Scenarios are named portfolio snapshots used for what-if comparison and have no direct Jira equivalent. We flatten each Scenario into a distinct set of epics tagged with a scenario_label property (Epic Label or Component). For example, a portfolio with two Scenarios (Baseline, Aggressive Growth) generates two labeled epic sets. The customer validates the scenario labeling strategy during scoping. Scenarios with no corresponding Jira project target are held in a reconciliation queue.

Meisterplan Resources are schedulable employees billed per seat. Jira does not have a native Role object — Resources map to Jira User accounts assigned via Teams. During scoping, we identify every Resource referenced in allocation records, confirm whether they need Jira access, and map them to Jira user accounts (created manually by the customer's Jira admin before import) or to Jira Teams if the Resource is a role placeholder without a named assignee. Resource availability percentages do not migrate as Jira has no native availability field; we document availability in a custom field for reference.

Meisterplan Resource allocations (who is allocated to which project at what FTE percentage) map to Jira issue assignments. Each allocation record generates an assignment record on the corresponding epic or story. We resolve Resource names to Jira User accounts by email. If a Resource has no Jira account, we assign to a placeholder team and flag for reconciliation. Jira's native workload view shows individual assignments after migration.

Meisterplan Programs group related Projects. Jira has no native Program object, so Programs map to Jira Project Categories (a grouping label on Projects) or to a Component hierarchy within the primary Jira Project. We use Jira Project Categories when the customer's portfolio maps to multiple Jira Projects, and Component hierarchies when a single Jira Project holds all epics with Program distinguished by Component.

Meisterplan Milestones (with name, date, and associated project) map to Jira Milestones in Jira Premium or to a custom milestone_name and milestone_date field pair on the Epic in Jira Standard. Jira Milestones provide native timeline tracking and release association without requiring a custom field. We use native Jira Milestones when the destination is Jira Premium.

Meisterplan Custom Project Fields (text, number, date, choice) map to equivalent Jira custom field types. We retrieve the full Custom Project Field schema via the Meisterplan REST API, then create matching Jira custom fields during the destination schema phase. Choice fields map to Jira select or radio button fields. Number fields map to Jira number fields. Date fields map to Jira date fields. We flag any Meisterplan field with a Jira API name collision and propose a rename during scoping.

Meisterplan Risks are a custom configurable object with their own custom fields. Jira has no native risk register, so we map Risks to a dedicated Risk issue type within the destination Jira Project. We retrieve the Risk schema via the Meisterplan API, create a matching Risk issue type with equivalent custom fields, and link each Risk to its parent Epic via an Epic Link. Risk status (Open, Mitigated, Closed) maps to Jira issue status.

Approved Budget, Plan-Ist comparisons, CapEx/OpEx cost types, and actual financial figures are Pro and Premium features in Meisterplan. If the source account is on Basic, financial data does not exist in the export and we flag this at scoping. For Pro and Premium exports, financial fields migrate as Jira custom number fields (budget_amount, actual_cost, capex_amount, opex_amount) on the Epic. Financial Tracker roll-ups do not migrate as Jira has no native financial tracking.

Meisterplan Actuals (time worked recorded against projects) map to Jira Worklog entries on the corresponding Epic or Story. We resolve the Resource name to a Jira User account, map the booking date to the worklog date, and migrate hours/days based on the Meisterplan allocation unit (FTE or hours). Worklog entries preserve the historical timeline that feeds utilization reports in Meisterplan.

Meisterplan Portfolio Views (Gantt, List, Board, heatmap) are UI artifacts that do not have direct Jira equivalents. We migrate the column layout and grouping configuration as a written specification document for the customer's Jira admin to configure in Jira Dashboards and Board filters post-migration. View configuration does not migrate as executable code.