Migrate from MeisterTask to Microsoft Project

MeisterTask Projects map 1:1 to Microsoft Project files (MPP) or Project Online PWA projects. Project-level settings including start date, fiscal year, and default calendar are configured at migration time based on the earliest task due date in the source. We preserve the project name and description as-is and set the Project Summary Task field to the first section header for out-of-the-box timeline rollup.

MeisterTask Sections are Kanban column containers with no scheduling weight. We convert each Section into a Summary Task in Microsoft Project, using the section name as the task name and the earliest task due date as the summary task finish. Tasks within the section become child rows beneath the summary task, inheriting the section's relative position. If a section has no tasks, we create a placeholder summary row to preserve the board structure. Section color coding is noted but has no Microsoft Project equivalent and is recorded in the project metadata.

Each MeisterTask task maps to a Microsoft Project task row. The task title, description (migrated as Notes field rich text), due date maps to Finish, and creation date maps to Start. Status (active, completed, archived) maps to Percent Complete (0 for active, 100 for completed, excluded for archived). Tasks without due dates are set to Start = project start and Duration = 1 day as a placeholder requiring admin scheduling after migration.

MeisterTask's one-assignee-per-task constraint maps to one resource assignment per task in Microsoft Project. We create a resource pool from the distinct assignee list, matching by email to existing Microsoft 365 users in the destination tenant where available, or creating generic resources. If the same task had multiple assignees simulated via tagging or comments in MeisterTask, we surface that pattern and offer to convert it to a primary resource assignment with a secondary resource note in the task Notes field.

MeisterTask tags are project-scoped free-form labels. We map them to a Project-level custom text field (Text1) with a picklist derived from the tag vocabulary, or as a Flag field if the tags function as binary task markers. Tag names with special characters are sanitized to valid custom field option values. The customer chooses tag strategy during scoping based on how tags are used operationally.

MeisterTask Notes (powered by MeisterNote, available on Pro and Business tiers) are project-scoped documentation linked to the project board. We extract the Notes text and append it to the Project Summary Task Notes field. Per-task notes in the MeisterTask task detail view migrate to the individual task Notes field with author and timestamp preserved as plain text in the notes body.

MeisterTask Custom Fields (Business tier only) are project-scoped with types including text, number, date, dropdown, and checkbox. We create equivalent custom fields in Microsoft Project using the Text, Number, Date, Flag, or custom field types that match the source field type. Dropdown fields from MeisterTask become picklist values in the Project custom field. Custom field schema is migrated project-by-project because MeisterTask enforces per-project field scoping.

MeisterTask time tracking (Pro and Business tier, accessible via Agenda view) logs time values and timestamps per task. We migrate logged time as Assignment Actual Work on the task row, formatted as hours in Microsoft Project's work units. Time entry author attribution is appended to the task Notes field if the destination Project plan supports notes. Free-tier accounts have no time entry data to migrate; we skip gracefully and note the absence in the migration report.

MeisterTask recurring tasks (Pro and Business) carry a recurrence pattern (daily, weekly, monthly, custom) stored per task. We create recurring task series in Microsoft Project using the recurrence dialog, mapping the daily, weekly, and monthly patterns to the equivalent Microsoft Project recurrence options. Custom recurrence patterns with non-standard intervals are converted to a best-match monthly or weekly recurrence with a note in the task Notes field describing the original custom pattern for admin review.

MeisterTask supports blocking and waiting task relationships where one task can block another. We detect these relationship edges during data extraction and convert them to Microsoft Project Finish-to-Start dependencies. A blocked task in MeisterTask becomes a successor task with a FS dependency from the blocking task. If MeisterTask's blocking relationship uses a lag time, we create the predecessor link with the corresponding delay in days.