Migrate from MeisterTask to Trello

MeisterTask Projects map directly to Trello Boards. We preserve the project name, description, color coding (if any), and member list during migration. Board visibility (public, organization, private) defaults to private unless the source project had external sharing enabled in MeisterTask, in which case we set organization visibility. Each board is created before any child lists (Sections) are added so that parent references are satisfied at insert time.

MeisterTask Sections within a project map to Trello Lists within a board. We preserve section ordering, section names, and any color coding applied at the section level. If the source section uses a color to indicate priority (red for urgent, green for done), we recommend the customer configure label colors in Trello after migration as part of the rebuild scope.

MeisterTask Tasks map to Trello Cards. We migrate task title, description (markdown preserved), due date, status (active/completed/archived mapped to open/archived), and position within the list. Archived tasks in MeisterTask map to archived cards in Trello. If the task was in a completed section in MeisterTask, the card is archived in Trello rather than placed in a Done list unless the customer requests list-based status mapping during scoping.

MeisterTask tasks support exactly one assignee, which maps to a Trello Board Member. We resolve each assignee by email against the destination Trello Workspace members list. If a matching member does not exist in the destination Workspace, we add the member to the board during migration using the Trello API, creating a pending invitation if the email does not correspond to an existing Trello user. Multi-assignee workarounds (comments tagging multiple people) are surfaced during discovery for manual conversion to Trello members.

MeisterTask Tags (project-scoped) map to Trello Labels. We preserve tag names and map them to Trello label colors using a default mapping (red, orange, yellow, green, blue, purple) or a customer-specified color scheme if provided during scoping. If a task in MeisterTask has multiple tags, each tag becomes a separate label on the card in Trello. Labels that exist in the source but have no tasks are omitted from the migration.

MeisterTask Comments on tasks map to Trello Card Comments. We preserve comment text, author name (resolved against Trello member list), and timestamp. Rich text in comments converts to plain text or markdown depending on content complexity. Comment ordering is preserved by setting the Trello creation timestamp to match the original.

File attachments on MeisterTask tasks migrate to Trello Card attachments. We download files from the source, preserve filename and metadata, and re-upload to Trello. Files stored as external URLs in MeisterTask (Google Drive links, etc.) are migrated as link attachments in Trello. Files exceeding Trello's 10MB per-attachment limit are flagged for chunking or alternative upload during discovery.

MeisterTask subtasks on Business tier map to Trello Checklists. We preserve subtask title, completion status, assignee (mapped to checklist item member in Trello if the Premium checklist feature is active), and position within the parent card. Subtasks that are themselves subtasks (nested) are flattened into a single checklist level since Trello does not support hierarchical checklists without a Power-Up.

Custom Fields from MeisterTask Business accounts migrate to Trello as card fields if the destination board has Trello Premium, Enterprise, or Standard with custom fields enabled. Text, number, date, dropdown, and checkbox field types map to Trello custom field equivalents. If the destination Trello plan does not support native custom fields, we document each custom field schema and recommend a label-based or Power-Up-based workaround, accepting that the migration will not preserve custom field data in structured form. Custom Fields are project-scoped in MeisterTask and board-scoped in Trello, so we map them per-project-to-board pair.

Time entries logged against tasks in MeisterTask Pro and Business tiers do not have a native Trello equivalent. Trello has no built-in time tracking on cards without a Power-Up. We extract all time entry records (duration, task association, user, date) and deliver them as a CSV inventory. The customer can use this to reconstruct time data in a Power-Up like Planyo, Toggl, or timeDoctor, or to populate a separate spreadsheet for billing reconciliation. We flag the absence of this data in the destination and note that it is a migration gap, not a technical failure.

Recurring task configurations in MeisterTask (daily, weekly, monthly, custom recurrence patterns) do not migrate because Trello has no native recurring task feature. We extract every recurring task's recurrence rule and next occurrence date and deliver them as a written inventory with the recommended Butler rule equivalent for each pattern. The customer or their Trello admin rebuilds the rules post-migration. We note which recurring tasks were active so no recurrence is inadvertently dropped.

MeisterTask supports blocking and waiting task dependencies. Trello has no native dependency feature without a Power-Up (Dependencyer or similar). We detect all dependency edges during extraction and deliver them as a relationship map in the migration report, documenting which card blocks which card so the customer can recreate them manually or via a Power-Up.

MeisterTask's linked Notes feature (MeisterNote) contains project-level documentation, meeting minutes, and wiki pages associated with tasks. Trello has no native note or wiki feature; project documentation would live in Confluence, Google Docs, or Notion instead. We extract Note content as a structured text inventory and deliver it separately, flagging the absence of a destination location for structured documentation.

MeisterTask Owners (workspace members) map to Trello Workspace Members. We resolve by email address across both systems. If a MeisterTask owner has no corresponding Trello account, we document the gap and recommend provisioning the account before migration so that assignee resolution succeeds. We do not create Trello accounts on the customer's behalf.