Migrate from Matilda Workspace to Trello

Matilda Teamspaces are the top-level permission boundary containing Projects, Tasks, Docs, and Chat. We map each Teamspace to a Trello Workspace using the Workspace name from Matilda. Permission inheritance (who can see which Teamspace) does not map directly because Trello Workspace permissions are Workspace-level (admin, member, observer) and not inherited from child objects. We document the original permission matrix in a permission-map deliverable for the customer's admin to re-apply at the Workspace level. If the customer uses Enterprise features in Matilda, those map to Trello Enterprise Workspace with domain-claimed member restrictions.

Each Matilda Project maps to a Trello Board. Project name, description, start date, end date, and status (active, archived) migrate as Board name, Board description, and a custom Board field for target dates. The Project's status (active vs archived) maps to Board archival state in Trello. Project-level custom properties (Matilda custom fields defined at the Project level) migrate to Board-level Custom Fields if the destination is on Standard plan or above; Free-tier destinations flag these as unmapped and surface them in the pre-flight report for plan upgrade consideration.

Matilda Tasks map to Trello Cards. The Task name becomes the Card title, description migrates as Card description (markdown-formatted), due date maps to the Card due date field, assignee maps to Card member, and status (To Do, In Progress, Done) maps to the Card's position within the appropriate List. We resolve the Matilda status to the nearest Trello List during scoping. Task custom properties (custom fields on individual Tasks) migrate to Trello Custom Fields on the Card if the Standard plan is active; otherwise they are flagged as deferred.

Matilda supports multi-level subtask nesting. Trello Checklists are a single level of Checklist items per Card. We flatten Matilda's subtask hierarchy into a flat Checklist on each Card, preserving parent-child relationships by prefixing child items with a dash (e.g., '- [ ] Subtask text') or nesting them as a text hierarchy within a single Checklist. The original subtask depth is recorded in a custom field subtask_depth__c so the customer can optionally restructure in a project management tool better suited to hierarchy. Checklists in Trello are available on Free tier with a limit of 100 items per card on Free, unlimited on Standard and above.

Matilda Docs are rich-text documents embedded within Projects. Short Docs (under 4,000 characters) migrate as Card descriptions in Trello with markdown formatting preserving headings, lists, and links. Longer Docs are exported as individual markdown files organized in a folder structure mirroring the original Matilda Project hierarchy, and the Card description contains a relative path link to the exported file. For teams using Google Docs or Notion alongside Matilda Docs, we can generate placeholder Cards with a card description linking to the original Matilda Doc export URL until the content is manually re-hosted in the destination Docs tool (Notion, Confluence, Google Docs).

Matilda Chat threads are per-project messaging with author, timestamp, and message body. Trello has no native Chat module; collaboration happens in Card comments and Board-level activity logs. We transform each Chat message into a Trello Card comment with the author name as comment author, original timestamp preserved, and message body in markdown. Thread context (which thread the message belonged to) is preserved in the comment body header. For high-volume Chat migrations (over 10,000 messages), we batch comments to avoid Trello's comment rate limits (documented at 100 comments per minute per token on Standard plan). Chat threads that reference specific Tasks are linked to the corresponding Card comment thread; standalone Chat threads without a Task reference are attached to the Project's primary Board as a dedicated Card comment thread.

If the customer's Matilda workspace uses a Labels system on Tasks, we map Labels to Trello Labels using the same color and name. Label-to-Task assignment migrates as Card-Label association. Trello Labels are available on Free tier and support arbitrary color and name pairs, which is compatible with Matilda's label model. We inventory the full label set during discovery to avoid naming conflicts within each Trello Board.

Matilda Task assignee and Project membership data map to Trello Card members. We resolve users by email address across both platforms. Trello exposes only usernames via API for user mapping (not email), per Atlassian documentation on the Power-Up migration flows. We use the email-based lookup from Matilda to resolve the correct Trello member, and flag any Matilda user whose email does not match a Trello account in the destination Workspace as an unmapped user in the reconciliation queue. The customer's admin provisions any missing Trello accounts before record migration resumes.

Matilda Task and Docs attachments migrate as Card attachments in Trello. We export attachment metadata (filename, URL, size, upload date) and re-link files to the Card if the destination Trello plan supports attachment storage (Free tier includes 10MB per attachment, 250MB total per Board; Standard and above increase these limits). For attachments exceeding Trello's size limits, we generate a download package and include the URL reference in the Card description. If the customer uses a cloud storage integration (Google Drive, Dropbox, OneDrive Power-Ups), we re-link attachments to the corresponding cloud file URL.

Matilda custom fields defined at the Project level map to Board-level Custom Fields in Trello if the destination Workspace is on Standard plan or above. The Custom Fields Power-Up (a Trello Inc. power-up, not third-party) supports text, number, date, checkbox, and dropdown field types. We inventory all Matilda custom field types during discovery, map them to the nearest Trello Custom Field type, and flag any Matilda field type without a Trello equivalent (e.g., Matilda-specific field types or multi-reference fields) as deferred with a recommendation for a third-party Power-Up or a Trello Standard plan upgrade. Custom Fields are not available on Trello Free tier, which is surfaced during scoping if the customer's Matilda workspace uses extensive custom fields.

Matilda custom fields defined at the Task level map to Card-level Custom Fields in Trello (same Custom Fields Power-Up noted above). The field name, type, and default value migrate. If the destination Trello Workspace is on the Free plan, custom fields are not available; we surface this gap in the pre-flight report and recommend upgrading to Standard before migration. The customer can choose to merge task-level custom fields into the Card description as structured text if a plan upgrade is not feasible, though this loses filterability.

Matilda's AI Copilot auto-schedules tasks and generates task sequencing based on dependency analysis. This AI-generated schedule does not translate to equivalent automation in Trello. We preserve the auto-scheduled due dates and task sequencing order as Trello Custom Fields (date type) and as a Card ordering note so the customer can re-enter them manually or run Trello's Butler automation to approximate the schedule. The original AI-generated dates are preserved in custom fields ai_original_due_date__c and ai_schedule_order__c on each Card for reference. The customer should plan a post-migration review of AI-scheduled dates to validate that Trello's manual scheduling aligns with project expectations.