Migrate from Notion to Trello

Top-level Notion pages that function as project containers map to Trello boards. We extract the page title as the board name and the page's top-level block content as the board description. Each board is created via the Trello REST API using the workspace's default organization. Pages nested more than one level deep inside other pages require manual decomposition since Trello has no concept of sub-boards; we document these during discovery and flag them for the customer's admin to split into separate boards or flatten into lists.

Notion databases with a board (Kanban) view become Trello boards where each database row is a card. The database title becomes the board name. For databases that use table, gallery, or list views rather than Kanban, we create a Trello board with a single 'All Items' list to preserve the flat structure. Databases with rollup or formula properties cannot be represented in Trello; we extract the computed values as plain text card fields and document the original rollup definition for the admin to evaluate against Trello's limited field model.

Each Notion database row becomes a Trello card. The row title property maps to the card name. All other property values (select, multi-select, date, number, checkbox, URL, email, phone) map to Trello card fields or labels. Select options become Trello labels (one label per selected option). Multi-select properties create multiple labels per card. Date properties become the card due date if exactly one date is set; if a date range is stored, only the start date migrates.

Block content from Notion pages and database row pages is extracted and concatenated into the Trello card description using markdown formatting. Paragraphs, headings (h1-h3), bullet lists, numbered lists, quotes, code blocks, and callouts all render in Trello's markdown-enabled descriptions. Toggle blocks (collapsible content) are expanded and their contents included inline. Trello's description field has a 32,768-character limit; pages with content exceeding this are split into a primary card with a summary and secondary cards linked via card links.

Files and images stored in Notion blocks are extracted from Notion's hosted storage, re-hosted, and attached to the corresponding Trello card. Notion's 5 MB file limit on Free and unlimited on Plus/Business means we can extract all file sizes present. We preserve the original filename and note the file type. If a Notion file URL is expired or inaccessible, we flag it in the migration report for manual recovery.

Notion supports table, board, gallery, list, timeline, calendar, and Gantt views per database. Only the board (Kanban) view has a direct Trello equivalent. For other view types, we document the filter, sort, and group configuration in the migration handoff and recommend which Trello Power-Ups (calendar view, timeline) could approximate the original layout. Views that rely on formula properties are documented with the formula text for the admin to evaluate.

Notion's relational database properties link records across databases. Trello has no native cross-database or cross-board relation concept. We extract the related record IDs from Notion's relation properties and write them as plain-text card links (URLs to the related card if both boards exist in the same Trello workspace) or as a text field in the card description listing the related record titles. Full relational integrity must be re-established manually in Trello or via a Power-Up like Unito post-migration.

Notion comments live in a separate API endpoint from page content and reference specific block IDs. We extract comment text, author display name, and the associated block ID, then write each comment as a Trello card comment on the corresponding migrated card. @mentions in Notion comments are preserved as plain text since Trello comment @mentions reference Trello members rather than Notion users. We flag any Notion comment referencing a block that was not migrated (e.g., from a discarded page) and log it in the migration exceptions report.

Notion workspace members are extracted with their display names and email addresses. We match these against Trello workspace members by email and assign migrated boards and cards to the corresponding Trello members where a match exists. Notion guests with limited workspace access are noted separately; Trello Standard and above support board-level member assignment. Owners without a Trello match go to the reconciliation queue for the customer's admin to provision before card assignment proceeds.

Notion's select and multi-select database properties use an option set with color metadata. We map each select option to a Trello label with the same color name (Trello's label colors are named red, orange, yellow, green, blue, purple, sky, lime, pink, black, and null for no color). If Notion uses more label colors than Trello supports (25 per board), we map the overflow to additional label names prefixed with the property name. Multi-select options create multiple labels per card.

Notion to-do list blocks and checkbox blocks inside page content are extracted as Trello checklists on the corresponding card. Each Notion checklist item becomes a checklist item in Trello. If the Notion checkbox is nested inside a toggle or callout block, we include the parent block's content as a prefix to preserve context. Completed checkboxes migrate with their checked state preserved; unchecked items migrate as unchecked.

Notion templates are pages or database rows saved as reusable structures. We extract the full template content including block structure, property defaults, and view configurations. Trello does not have a native template page concept; the customer's admin recreates templates as Trello board templates or using Butler commands. We deliver a template inventory document listing each Notion template's content, database associations, and recommended Trello equivalent.