Migrate from MeisterTask to monday Work Management

MeisterTask Projects map 1:1 to monday.com Boards. We preserve project-level settings including the project name, description, and color coding. The board is created first as the parent container before any child records are imported. If the source project is archived, we note the archive status and optionally create an archived board in monday.com for reference.

MeisterTask Sections map to monday.com Groups (the column containers on a board). Section order is preserved by creating groups in the same left-to-right sequence as the source. Any section color coding is noted as a metadata flag because monday.com Groups do not have native color attributes at the group level.

MeisterTask Tasks map to monday.com Items. We preserve task title, description (as the item's main text), due date (mapped to a Date column), status (active/completed/archived mapped to Item archived state and group placement), and the creation timestamp. Archived tasks migrate as archived items in the destination board.

MeisterTask enforces one assignee per task. When migrating to monday.com's people column (which supports multiple assignees), each task becomes one item with the single assignee placed in the people column. If your team used tagging or comments to simulate multi-owner workflows in MeisterTask, we surface those patterns during discovery and give you the option to convert them to additional people-column entries at the destination.

MeisterTask Tags are free-form labels scoped per project. They map to monday.com's Tags column on the target board. Tag names and color metadata are preserved. Note that monday.com Tags are board-scoped in the same way as MeisterTask Tags, so board-level tag governance is maintained after migration.

MeisterTask Business-tier custom fields are reconstructed as monday.com column types: text fields map to Text columns, numbers to Numbers columns, dates to Date columns, dropdowns to Dropdown columns, and checkboxes to Checkbox columns. Because custom field schemas vary per project in MeisterTask, we detect the full custom field inventory during discovery and configure each board's column palette before data load. This reconstruction is only available if your source account is on the Business plan; Free and Pro accounts do not have custom field data to migrate.

MeisterTask time tracking (available on Pro and Business tiers via the Agenda view) is logged per task. monday.com does not have a native time-tracking column as a standard board feature; time tracking is available via the monday.com Workdocs integration or through the separate Time Tracking by TimeCamp integration. We migrate the time entry values and timestamps as a Number column labeled with the logged duration, and note the available monday.com time-tracking integrations for your admin to configure post-migration.

MeisterTask recurring task patterns (daily, weekly, monthly, custom) are preserved as recurrence metadata on the migrated item. We do not create recurring automations in monday.com as part of the migration scope. Instead, we deliver a written inventory of each recurring task with its recurrence rule and the recommended monday.com automation recipe to recreate it in the Automation center.

MeisterTask Notes are powered by MeisterNote and are project-scoped. Free tier allows up to 5 notes; Pro and Business allow unlimited. We migrate note titles and content as text blocks. If your team relies heavily on linked wiki-style documentation, we recommend mapping notes to monday.com Workdocs attached to the board or as pinned text widgets on the board; the specific layout decision is made during scoping.

File attachments on MeisterTask tasks are downloaded during extraction, preserving filenames and upload metadata. They are re-uploaded to the monday.com Files column on the corresponding item. Attachment URLs stored as external links in MeisterTask migrate as Link column entries. Files are uploaded in the same sequence as the source to preserve ordering within each task.

MeisterTask comments migrate to monday.com Updates on the corresponding item. Each comment is associated with its author (resolved by email match to the monday.com workspace member) and preserves the original timestamp. Comment threading in MeisterTask is flattened into a chronological list in monday.com since monday.com does not support nested reply threads natively.

MeisterTask supports blocking and waiting relationships between tasks (one task can block another). We detect these relationship edges and reconstruct them as monday.com Dependencies column entries. Note that the Dependencies column is available on monday.com Standard plan and above. If your source account uses task relationships and your destination plan does not include this column type, we flag the gap during scoping.