Migrate from Coda to Trello

Each Coda Doc maps to a Trello Board. We enumerate all Docs in the source workspace via the Coda API v1 list endpoint and create one Board per Doc, preserving the Doc title as the Board name. Doc metadata (owner, created timestamp, last modified) migrates as Board description and as a sticky card for admin reference.

Coda Pages nested within a Doc map to individual Trello Cards within the corresponding Board. We traverse the full page tree via the Coda API, preserving parent-child hierarchy in the card description (a markdown outline structure) so the nesting is visible in Trello. Pages that contain only sub-pages render as a card with a checklist of child pages rather than creating a separate card.

Each Coda Table maps to a batch of Trello Cards — one card per Coda row. We extract the effective per-table column schema before mapping, because Coda allows different column types for the same logical field across tables. Coda Row IDs are preserved as a custom field on each Trello Card for reconciliation. Tables with more than 20 columns that exceed Trello's built-in Custom Fields capacity land as structured JSON attachments on the parent Card with a header row matching the column names.

Coda column types text, number, date, and email map to Trello Custom Fields (Standard tier or Custom Fields Power-Up on Free). Select and multi-select columns map to Trello label sets that we create dynamically during migration. We extract full column option lists from Coda and create matching label names in Trello, with the label color derived from the Coda option color if present.

Coda select and multi-select columns map to Trello Labels. The Coda option display name becomes the label name; Coda option color becomes the Trello label color. Multi-select columns that represent more than 30 distinct options split into multiple label groups (e.g., Status-Option1, Status-Option2) since Trello Labels do not natively support grouping.

Individual Coda rows map to individual Trello Cards. Row content from text columns populates the Card description; numeric and date column values populate Custom Fields; select column values become Labels. We use the Coda Row ID as a custom field for audit and reconciliation. Rows are inserted into the appropriate Trello List based on a status or stage column if present in the source table.

Coda cross-table relations use the Relation column type and store a target Row ID. We resolve the target Row ID to the corresponding Trello Card (via the Row-ID custom field) and write the Card URL as a Custom Field on the source Card. Relations that reference rows in a table that did not migrate to Trello are flagged as broken links in the migration report for admin review.

Coda cross-doc page references (URLs pointing to a page in a different Doc) do not have a Trello equivalent because Trello has no cross-board linking mechanism. We preserve the cross-doc URL in a Card custom field labeled Cross-Doc Reference and flag any cross-doc references that point to a Doc that also migrated — in those cases, we update the reference to point to the corresponding Trello Board instead of the original Coda URL.

Free-form Coda canvas content (text blocks, embeds, images, inline tables) extracts as structured JSON blocks. We render the text block content into the Card description as markdown. Inline tables and embeds that cannot render in Trello land as structured data in a Card attachment or as a pinned comment with the structured content.

Coda formula columns compute values from row data and cross-table lookups. Trello has no formula engine equivalent. We evaluate formula results at migration time and write the computed value as a static Custom Field on the Trello Card. Formulas that depend on real-time data or other rows (rolling sums, running averages) are flagged as dynamic and cannot be preserved — the migration report notes these fields for the admin to implement in Butler or a spreadsheet if required.

Coda automation rules use trigger-action logic scoped to a Doc. Trello Butler operates board-by-board with card-triggered commands, scheduled commands, and button commands. We export the full rule definitions (trigger, conditions, actions) and deliver a written Butler rebuild guide mapping each Coda automation to its nearest Butler equivalent. Complex automations with cross-table conditions or external API calls have no Butler equivalent and are noted for rebuild as a Butler Pro workflow or a third-party automation tool like Zapier.

Files embedded in Coda rows or canvas blocks are stored with expiring temporary URLs via Coda's API. We pull attachments directly from Coda's authenticated API session before migration staging begins, re-uploading each file as a Trello Card attachment. Files exceeding Trello's attachment size limit (10MB on Free, 250MB on Standard and above) are identified during scoping; the admin chooses whether to split large files, upload to Google Drive and link, or exclude.