Migrate from monday Work Management to Trello

monday Boards map directly to Trello Boards as the top-level workspace container. Board name, owner, and workspace membership transfer. Board-level settings (default view, notification preferences, permission defaults) do not export via monday API and must be reconfigured manually in Trello. We flag board-level permission differences during scoping: monday workspace permissions are more granular than Trello's default board visibility (public, organization, private).

monday Groups (horizontal row containers within a Board, typically representing a status column or phase) map to Trello Lists. We preserve Group order and name. The mapping assumes a single-status-per-Item model; if a monday board uses multiple parallel Group columns for different properties, we map the primary status Group to the Trello List and flag secondary Group columns for Power-Up field coverage.

monday Items (the primary work unit on a Board) map directly to Trello Cards. Item name, description, assignees, and due date transfer. The Item's position within its Group becomes the Card's position within the List. Items without a Group default to the first List. We preserve the original Item ID in a custom Card field (Power-Up) for cross-reference during reconciliation.

monday Status columns behave like Trello Lists when the board uses one status column per view. We detect Status-type columns and evaluate whether the board's primary view uses a single status column (map to List) or multiple status columns (map to Power-Up single-select fields). Teams using Status columns for multi-dimensional tracking must choose one as the List source and map the rest to Power-Up fields.

monday Date columns map to Trello Power-Up date fields (Calendar Power-Up or Custom Fields Power-Up). Text columns map to Power-Up text fields. Number columns map to Power-Up number fields. Link columns map to Power-Up URL fields. We inspect each board's column set during discovery and provision the corresponding Power-Up field type in the destination Trello board before import. Note that Trello's Custom Fields Power-Up on Standard allows 25 fields per board, which may require column consolidation for boards with more than 25 columns.

monday Formula columns compute outputs from other column values; Trello has no formula engine. Dependency columns establish predecessor-successor links across items or boards; Trello card relations can replicate some cross-item links but cannot preserve cross-board dependency graphs. Vote columns (team voting on an Item) have no Trello equivalent and are not migrated. Time Tracking columns require a Power-Up (Time Tracking by Glavian or similar) and the customer must provision this before migration; we flag the dependency and optionally provision the Power-Up as a scoped add-on.

monday Subitems are nested Items beneath a parent Item. Trello has no subitem concept. We handle Subitems by flattening them into standalone Cards on the same destination board as the parent Card, then establishing a Trello card relation (one direction) from the parent Card to each child Card. This preserves the hierarchical relationship in a Trello-compatible form. The Subitems API requires a per-Item secondary call (no bulk endpoint), which multiplies against monday's complexity budget and may require multi-day migration pacing on Basic-tier accounts.

monday Users (assigned to Items, owning Boards) map to Trello Members by email match. Owner assignment on Items translates to Card assignment. We resolve Users by email against the Trello destination workspace's member list. Any monday User without a matching Trello member is held in a reconciliation queue; the customer's admin provisions the missing Trello account before card import resumes.

monday Teams group users for team-based permission scoping and Workload views. Trello Teams are not a native concept; Trello uses Workspaces and Organization membership. We map monday Teams to Trello Workspace membership. The customer chooses whether to create one Trello Workspace per monday Team or consolidate into a single Workspace.

monday Dependency columns establish predecessor-successor links between Items, including cross-board links. Trello card relations can model a subset of these (same-board predecessor-successor pairs) using the Card Relations Power-Up. Cross-board dependencies cannot be preserved in Trello natively; we flatten these into a free-text field (dependency_reference__c) carrying the original monday Item ID and board name. The customer receives a written cross-board dependency map to manually re-establish in Trello or accept as collapsed.

monday Updates (threaded comments on Items) migrate to Trello Card Comments. Each Update's body (HTML or plain text), author, and timestamp transfer. Nested replies migrate as comment threads. The original author is resolved by email match to a Trello Member. Comment ordering is preserved by timestamp. Updates exceeding 10,000 characters are trimmed to Trello's comment length limit and the overflow is flagged in the reconciliation report.

monday File column files and inline attachments on Items store file metadata (name, URL, uploader, timestamp). We preserve file references as Trello Card Attachments pointing to the same URL. Actual binary file download is out of scope for monday API access; we migrate the URL reference only and the Trello board must have network access to the file host. Files without a publicly accessible URL are flagged in the reconciliation report.

monday Tags (free-text labels with optional color) map to Trello Labels by name, with color preserved as the Trello Label color. Label scope in Trello is board-level; monday tags are board-level in practice though the platform supports workspace-level tag libraries. We map at board level and flag any workspace-level tag usage for manual consolidation.

monday Automation Center rules (trigger-action patterns) and third-party integration connections (Slack notifications, Salesforce syncs, Zoom meeting links) are server-side configuration objects not exposed via API. We do not migrate automations or integrations. We deliver a written inventory of every automation rule detected in the monday UI export, including trigger, conditions, and actions, so the customer's team has a reference to rebuild in Butler or the relevant Power-Up. Integration connections must be re-established manually in Trello or via Trello's native integrations.