Migrate from Matilda Workspace to monday Work Management

Matilda Teamspaces are the top-level permission boundary containing Projects, Tasks, Docs, and Chat threads. We map each Teamspace to a monday.com Workspace, preserving the workspace name and any permission-scoped structure. If multiple Teamspaces map to the same monday.com Workspace for consolidation, we document the mapping during scoping. monday.com supports multiple workspaces on all tiers, including the free tier (2 seats).

Matilda Projects carry start/end dates, status, and linked Tasks. We map Project to monday.com Board, using the project name as the board name and project-level custom properties as Board columns. We configure the Board type (Team, Personal, or Shareable) during migration based on the Teamspace permission scope. Projects with multiple sub-projects in Matilda become multiple Boards linked via the Connect Boards column.

Matilda Tasks map to monday.com Items on the corresponding Board. Task fields (title, description, assignee, due date, status, subtasks) map to monday.com Item name, person column, date column, status column, and subitems or linked Items. Task priority from Matilda maps to a priority label column or tag group. We flatten subtasks into linked Items rather than subitems if the customer prefers a flat task list.

Matilda subtasks attached to a parent Task become separate monday.com Items linked via the Connect Boards column or Subitems column. We preserve the parent-child relationship by storing the parent task name or Item ID in a custom text column so the hierarchy is visible in the destination. If Matilda subtasks have their own assignees and due dates, those migrate as independent Item properties on the child.

Matilda Docs export as structured HTML or markdown content. If the customer uses monday Docs (available from Standard tier), we migrate content directly into monday.com Doc records linked to the corresponding Board. If monday Docs is not on the customer’s plan, we deliver Docs content as a structured HTML download package organized by project and linked from the relevant Board for manual re-creation.

Matilda Chat threads are integrated per-project with message metadata and timestamps. We export Chat thread metadata (participants, start date, message count) and message content as a chronological log with author and timestamp. monday.com does not have a native Chat Thread object; we recommend mapping Chat threads to a dedicated monday.com Board as Item Updates or linking a Slack workspace integration post-migration if the customer prefers to keep conversations in a dedicated chat tool.

Matilda task assignees and project members resolve to monday.com person column values by email address. We inventory all Matilda workspace members during discovery, match by email against monday.com user accounts, and flag any Matilda user without a matching monday.com account for the customer’s admin to provision before migration. Teams using Matilda’s free tier may have more users than the 2-seat monday.com free tier supports; we flag this during scoping.

Matilda supports custom fields on Projects and Tasks. We inventory all custom field types (text, number, date, checkbox, dropdown) during discovery and generate a custom column mapping table before migration. monday.com supports 30+ column types; we map each Matilda custom field to the closest monday.com equivalent. Any Matilda custom field with a type that has no direct monday.com analog is flagged for the customer’s admin to review.

Matilda task and Doc attachments are file references stored in the Matilda workspace. We export attachment metadata (filename, size, URL, upload date, attached-to object). If monday.com supports file hosting on the customer’s plan, we re-link files to the relevant Items. On plans with limited storage, we provide a download package of all exported attachments organized by project and task for manual re-upload.

Matilda’s auto-schedule engine computes task sequencing and sets task start and due dates based on dependency inference. These computed dates do not migrate as fixed values because monday.com’s own dependency column and Gantt views handle scheduling independently. We export the auto-schedule logic as a dependency map (task A precedes task B) stored in a notes column, and the customer re-runs scheduling in monday.com after migration. This avoids locking in Matilda’s derived dates as immutable values in a system with a different scheduling engine.

Matilda’s AI Copilot auto-generates task hierarchies, project outlines, and subtasks from minimal input. We export all AI-generated tasks as explicit Items with a flag in a custom column (source: ai_generated) so the customer’s admin can review and retain or remove AI-generated content in monday.com. The Copilot-generated outlines themselves are not recreated as monday.com automation recipes because monday.com does not have an equivalent AI task-generation feature at this time.

Matilda Tables is listed as coming soon with no GA schema, per Matilda’s product site. We do not migrate Tables objects because the schema is undefined. We flag this for the customer during scoping and revisit once Tables reaches general availability and the schema is publicly documented. monday.com’s Custom Objects feature (Standard tier and above) may serve as a replacement for Airtable-style tabular data collections once Matilda Tables is available.