Migrate from Meisterplan to Trello

Meisterplan Projects map to Trello Boards. Each Project becomes a Board with the Project name as the Board title, and the project description field migrates as the Board description. We set the Board visibility (private, workspace, public) based on a scoping question about team access. Multi-project portfolios in Meisterplan map to multiple Boards under a single Trello Workspace, preserving the portfolio structure as a Workspace-level naming convention.

Meisterplan Scenarios (named portfolio what-if snapshots) have no native Trello equivalent. We handle Scenarios as a configuration decision: if the customer has up to five Scenarios, we create one List per Scenario on the Board and place each project's Cards into the relevant List. If the customer has many Scenarios or plans to keep scenarios for reference, we create Trello Labels with a scenario_label naming convention and tag Cards accordingly. The customer selects the strategy during scoping.

Meisterplan Resources (the paid schedulable employees) map to Trello Board Members by email lookup. We flag Resources who have no corresponding Trello member account as a reconciliation action before migration, because Cards cannot be assigned to non-members. If the customer plans to use Trello members for resource assignment tracking, all Resources must have or receive a Trello account. If Trello accounts are not feasible for all Resources, we use a custom field labeled Resource instead of native card assignment.

Meisterplan Users (free and unlimited) who are not Resources map to Trello Workspace Members at the Workspace level. Role-based access in Meisterplan (Admin, Project Manager, Resource Manager, Viewer) has no direct Trello equivalent, so we document the role assignments in a separate roles inventory file for the customer's admin to reconfigure in Trello Workspace settings.

Meisterplan Custom Project Fields (text, number, date, choice) migrate to Trello Card Custom Fields available on Standard plan ($5/seat). We retrieve the full field schema via the Meisterplan REST API, then create Trello Custom Fields of the matching type (text, number, checkbox, date, dropdown) before migration. The field values migrate per Card. Basic-tier Meisterplan customers may have no Custom Project Fields if they never configured any; we verify this during scoping.

Meisterplan Milestones (named points in time marking significant delivery dates) map to Trello Card due dates. We extract the milestone name, date, and associated Project, then set the corresponding Card's due date to the milestone date. If multiple milestones share a date, we add a custom field labeled Milestone to identify the milestone name on the Card. Trello does not have a milestone-specific object, so this mapping is the closest structural approximation.

Meisterplan Programs (groups of related Projects) map to either a Trello Board (if Programs represent distinct work areas) or a Label (if Programs are cross-cutting categorization). We determine the strategy during scoping based on the customer's Program count and how their team expects to filter by program in Trello. If Programs are many, we recommend Label as a lightweight categorization; if Programs are few and each contains distinct projects, we recommend one Board per Program with the Project-level cards nested inside.

Meisterplan financial fields are Pro and Premium features only and have no native Trello equivalent. If the customer requires financial data in Trello, we create Custom Fields (Approved Budget, Plan, Actual, Variance) on the Board as number-type fields and populate them from the source export. We flag that Trello has no financial reporting engine, so these figures are display-only and require a separate reporting tool for variance analysis. If the customer is on Basic edition, no financial data exists in the source export.

Meisterplan Risks (a custom object with configurable fields in Pro/Premium) have no native Trello equivalent. We migrate each Risk as a Card on a dedicated Risk Board with a Label applied for filtering. Core risk fields (title, description, status, probability, impact) migrate as Card fields or Custom Fields. If the customer uses a dedicated risk management tool alongside Trello, we recommend linking risk cards via URL Custom Fields rather than duplicating risk data in Trello.

Meisterplan Actual time entries record hours worked against projects and roll up to utilization reports. Trello has no native time-tracking object. We migrate Actuals as either a Custom Field (hours logged) on the relevant Card or as a checklist item with the hours recorded in the item name, depending on whether the customer needs to preserve the hours as a data field or as a checklist step. Utilization reporting does not migrate; we flag this as a limitation and recommend a dedicated time-tracking integration.

Meisterplan Portfolio Views (Gantt, table, heatmap) are UI artifacts with no structural data equivalent in Trello. We document the view configuration (column layout, grouping, filters) as a written view specification for the customer's admin to apply in Trello. Trello's Calendar, Timeline, and Dashboard Power-Ups approximate some views but require separate setup. We do not migrate views as code.

Meisterplan Finance Categories (CapEx, OpEx, and custom category breakdowns) migrate as Custom Fields of type dropdown on the Board. We preserve the category definitions and their assigned values per project. Trello has no chart of accounts or cost code structure, so this mapping is informational rather than operational. If the customer needs budget-to-actual tracking, we recommend integrating with a finance tool rather than building this in Trello.