Notion to Trello migration
We migrate Notion pages, databases, and block content into Trello boards, lists, and cards with content preserved in card descriptions and a written inventory of Notion relations, rollups, and templates that cannot be reconstructed in Trello's flat card model.
FlitStack AI migrates boards, cards, card descriptions, card attachments and board configurations from Notion to Trello, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Notion to Trello?
Moving from Notion to Trello is a structural simplification, not a lateral move.
Read the full summary
Notion stores everything as a block tree with nested pages, relational databases, rollups, and cross-database links; Trello operates a flat board-list-card hierarchy with no native database concept, no cross-board relations, and no rollup fields. We extract Notion pages and database rows via the Notion API using token-bucket queuing against the 3 req/sec ceiling, chunk oversized pages that exceed the 1,000-block per-request limit, and write block content into Trello card descriptions. Notion databases with many properties become boards with cards, where each row is a card and select or multi-select property values become Trello labels. We do not migrate Notion Automations, page templates, cross-database relations, rollups, or linked-record chains as code; we deliver a written inventory of these for the customer's admin to evaluate and rebuild using Trello Butler or a third-party automation tool. Comments and @mentions do not map natively to Trello's card-comment model, and we flag this gap during scoping.
Pages (root-level) → Board
Top-level Notion pages that function as project containers map to Trello boards.
How it maps
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.
Databases → Board
Notion databases with a board (Kanban) view become Trello boards where each database row is a card.
How it maps
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.
Database Rows → Card
Each Notion database row becomes a Trello card.
How it maps
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.
Blocks (paragraph, heading, list, quote, code, callout) → Card Description
Block content from Notion pages and database row pages is extracted and concatenated into the Trello card description using markdown formatting.
How it maps
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.
Attachments and Files → Card Attachments
Files and images stored in Notion blocks are extracted from Notion's hosted storage, re-hosted, and attached to the corresponding Trello card.
How it maps
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.
Database Views → Board Configuration
Notion supports table, board, gallery, list, timeline, calendar, and Gantt views per database.
How it maps
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.
- PagesBoard1:1
- DatabasesBoard1:1
- Database RowsCard1:1
- BlocksCard Description1:1
- Attachments and FilesCard Attachments1:1
- Database ViewsBoard Configurationtransformed
+ 6 more in the mapping below
How Notion and Trello differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Notion | Trello |
|---|---|---|
| Core data model | Block tree: pages contain pages, databases, and blocks in nested hierarchy | Flat board-list-card: boards contain lists, lists contain cards, no nesting beyond board level |
| Database concept | Full relational databases with 20+ property types, rollups, and relations across databases | No native database; board-card model acts as a flat task list with labels as the only property proxy |
| Block types | 50+ block types including callouts, toggles, tables, code, embeds, and synced blocks | Card title, description (markdown), checklist, attachment, label, due date, and member only |
| Cross-reference capability | Relations and rollups link records across databases with aggregated calculations | No cross-board linking; cards are isolated unless managed via Power-Up or external tool |
| View types | Table, board (Kanban), gallery, list, timeline, calendar, and Gantt views per database | Board (Kanban), list, and calendar views on a single board layout |
| Automation model | Notion Automations with trigger-action rules, multi-step logic, and conditional branching | Trello Butler with rule-based, button, and command automations at board level |
| Free plan limits | Unlimited pages and blocks; 7-day history; 5 MB file uploads | Unlimited boards, lists, and cards; 10 board Power-Up per board; 10 MB per file attachment |
What to watch for in a Notion to Trello migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Notion databases with rollups have no Trello equivalent
Notion's rollup properties aggregate values across related records using formulas (count, sum, average, percent, min, max, show original, latest, range).
How we handle it
Trello has no rollup, formula, or cross-record calculation capability. We extract the last computed rollup value as a plain-text field and document each rollup's definition in the migration handoff for the admin to evaluate whether the data can be replaced by manual tracking or a Trello Power-Up with limited calculation capability.
Cross-database relations break in Trello's flat model
Notion's relation property links records across databases, enabling interconnected knowledge systems without code.
How we handle it
Trello cards are isolated within their board; there is no native concept of a cross-board reference or linked record. We extract relation IDs and record titles as text and write them to the card description, but the relational integrity of the original Notion workspace is not preserved. Customers relying on Notion relations for project interdependencies must re-establish these manually post-migration or adopt a Power-Up like Unito for two-way sync.
Notion API ceiling of 3 req/sec limits extraction speed
Notion's API enforces a 3 requests per second rate limit with token-bucket queuing.
How we handle it
Large workspaces with thousands of pages and blocks require thousands of sequential API calls, and the absence of a bulk export endpoint means we must traverse the full block tree recursively. We implement exponential backoff on 429 responses and chunk pages exceeding the 1,000-block per-request limit, but workspaces with over 10,000 pages can take multiple days of extraction alone before any Trello import begins.
Nested page hierarchy has no Trello analog
Notion pages nest inside other pages to arbitrary depth, and child pages often contain their own databases and sub-pages.
How we handle it
Trello has no sub-board or nested board concept; boards exist only at the workspace level. We flatten nested hierarchies during migration by creating a board for each top-level Notion page and documenting the original parent-child path. The customer's admin must decide whether child pages become separate boards, lists within a board, or card-linked secondary records.
Notion Automations do not migrate to Trello Butler
Notion Automations (formerly Workflows) use trigger-action rules with conditional logic, multi-step branching, and CRM-style actions that are structurally incompatible with Trello Butler's rule-based commands.
How we handle it
We do not migrate automations as code. We extract every active Notion Automation with its trigger, conditions, and action chain, and deliver a written automation inventory mapping each to an equivalent Butler command or recommending a third-party automation tool. The customer's admin rebuilds automations post-migration.
How the migration runs
Discovery and workspace audit
We traverse the Notion workspace via the API to inventory every page, database, block, relation, rollup, template, comment, and attachment.
What this step covers
We extract the full block tree for each page, handling the 1,000-block per-request limit by chunking oversized pages into sequential batch calls. We identify nested page depth, cross-database relation chains, and any rollup property that has no Trello equivalent. We also inventory Notion Automations with their trigger conditions and action sequences. The discovery output is a written scope document with page counts, database row counts, attachment volume, and a list of relations and rollups requiring admin disposition.
Schema design and board structure plan
We design the Trello workspace structure based on the discovery output.
What this step covers
Each top-level Notion page becomes a board; each database becomes a board with one list per status column (derived from the Notion database's board view group-by property). We define the label set per board from each Notion database's select and multi-select option colors. We document any Notion page that requires decomposition into multiple boards or lists due to nesting depth, and any database whose rollup properties must be captured as static values. This plan is reviewed with the customer before any extraction begins.
Notion extraction with rate-limit handling
We extract all Notion content via the Notion API using token-bucket queuing at 2.8 req/sec (below the 3 req/sec ceiling) with exponential backoff on 429 responses.
What this step covers
Each page's block tree is traversed recursively with chunking for pages exceeding 1,000 blocks or 500 KB per request. Database rows are extracted with all property values including select options, dates, numbers, and checkbox states. Comments are fetched from the separate comments endpoint and matched to block IDs. File and image URLs are collected for re-hosting during Trello import.
Content transformation and mapping execution
We transform the extracted Notion block tree into Trello card descriptions in markdown.
What this step covers
We convert toggle blocks to inline text, preserve checklist items with their checked state, and strip any Notion-specific block types that have no markdown equivalent (synced blocks become standard text). Select and multi-select property values are converted to Trello labels. Rollup values are written as plain-text card fields. Cross-database relation IDs are written as card description text referencing the related record title. Each transformation is logged for reconciliation against the source Notion export.
Trello workspace population
We create boards in Trello via the REST API, add lists per the board structure plan, create cards from database rows and page blocks, apply labels, set due dates from Notion date properties, and attach files.
What this step covers
We assign board members by matching Notion user emails to Trello workspace members. Comments are posted to cards in chronological order with author attribution. We run batch inserts with Trello's own rate-limit handling and exponential backoff, targeting 10-15 cards per second against Trello's API limits. Each batch emits a row-count reconciliation report against the source Notion database.
Validation, cutover, and automation handoff
We reconcile final record counts between Notion and Trello: boards created, cards created, labels applied, attachments migrated, and comments posted.
What this step covers
We flag any Notion content that could not be migrated (due to API inaccessibility, attachment expiry, or schema incompatibility) in an exceptions log. We deliver the automation inventory document listing each Notion Automation with its trigger, conditions, actions, and recommended Trello Butler equivalent. We do not rebuild Notion Automations as Trello Butler commands inside the migration scope; that work is a separate engagement or an internal admin task. We support a 5-business-day post-migration window for reconciliation questions before closing the engagement.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with the number of Notion pages, database rows, and the complexity of nested hierarchies requiring manual decomposition. Notion subscription costs end at migration cutover. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Notion to Trello →Why teams move from Notion to Trello
- Notion's flexible workspace becomes a liability at scale. Users managing 30+ databases or deeply nested page trees report slow load times, scroll stuttering, and difficulty locating content even with the search function. Trello's flat board-list-card hierarchy imposes a structural discipline that keeps performance consistent regardless of workspace size, and the mobile app handles large boards without the sluggishness reported in Notion's mobile experience.
- Notion's block-based editor and relational database model carry a steep learning curve that many teams never fully close. A designer managing multiple projects describes returning to Trello after trying Monday and Asana specifically because 'the interface is beautiful and user friendly, while Notion feels visually cluttered even when well organized.' Trello's board-card metaphor takes 30 seconds to explain to a new team member versus the hours required to onboard someone to Notion's block structure and database views.
- Teams that moved to Notion for its all-in-one promise find themselves spending more time maintaining the workspace than using it. One user who switched from Trello to Notion describes spending weeks learning and building templates before being productive, then switching back after realizing Trello's simplicity let them 'just get things done.' For teams whose primary workflow is Kanban task tracking, Notion's additional layers of capability add overhead without proportional value.
- Notion's pricing at $12/user/month for Plus and $18/user/month for Business exceeds Trello's $5/user/month Standard tier for teams that only need Kanban boards and task tracking. Multiple reviewers on comparison sites note that Trello's free plan is 'better equipped' for single users or small teams who do not need the wiki, documentation, and database features bundled into Notion's pricing. Teams moving from Notion Plus to Trello Standard can halve their per-seat cost while retaining all project management capability.
- Notion lacks a native Trello export or importer. Atlassian Community threads document that Notion, ClickUp, and Monday.com all offer Trello import tools to attract migrating users, but Trello has not built a reciprocal Notion import. Teams wanting to consolidate their Notion project data into Trello have no official path and must use CSV-based Power-Ups, third-party sync tools, or a custom migration pipeline. FlitStack AI closes this gap with a structured Notion-to-Trello extraction and import pipeline.
Questions, answered
Notion to Trello migration questions
How long does a Notion to Trello migration take?
Small workspaces with fewer than 500 pages and 5,000 database rows typically complete in three to five weeks. Medium workspaces with multiple interconnected databases, large attachment libraries, or extensive nested hierarchies requiring manual decomposition move to eight to twelve weeks. The extraction phase from Notion alone can take three to seven days for large workspaces due to the 3 req/sec API ceiling and the absence of a bulk export endpoint. Trello import runs faster once extraction is complete.
Do Notion Automations, templates, and relations migrate to Trello?
No. Notion Automations use a trigger-action model with conditional branching that has no direct Trello Butler equivalent. We do not migrate automations as code. We deliver a written inventory of every Notion Automation with its trigger conditions, action chain, and a recommended Butler command or Power-Up equivalent for the customer's admin to rebuild post-migration. Relations, rollups, and cross-database linked records do not migrate; we extract relation IDs and record titles as plain text in card descriptions and document the full relation graph for manual re-establishment.
Can we migrate only project management data and leave documentation behind?
Yes. We scope the migration to the Notion pages and databases the customer designates as project management content. Standalone documentation pages, wikis, and personal notes that have no Trello equivalent are excluded from the migration scope. We document which Notion content was excluded and why during discovery so the customer can make an informed decision before extraction begins. Teams that use Notion as a combined wiki and project management tool should evaluate whether the documentation can remain in Notion (with a reduced seat count) or must also move to a wiki alternative.
What happens to Notion page history and version control?
Notion retains page history server-side (7 days on Free, 30 days on Plus, 90 days on Business, unlimited on Enterprise), but the version history is not accessible via the public API. Only the current revision of each page is exportable. We warn customers during discovery if historical versions must be preserved and advise exporting those manually via the Notion UI before migration begins. Trello has no native version history on cards; the customer's admin can use Butler to create audit-log cards or a third-party Power-Up for change tracking if version control is required.
Do Notion comments and @mentions migrate to Trello?
Partially. Notion comments are extracted from the comments API endpoint and written as Trello card comments on the corresponding migrated card, preserving comment text and author name. @mentions in Notion comments are preserved as plain text because Trello comment @mentions reference Trello workspace members rather than Notion users. We match Notion workspace members to Trello members by email where a match exists and flag any Notion user without a Trello account for the admin to provision. Comments on Notion blocks that were not migrated (e.g., from discarded pages) are logged in the migration exceptions report.
Can Trello handle databases migrated from Notion with many columns and properties?
Notion databases with 15+ property columns cannot map one-to-one to Trello, which supports only a limited set of card fields (name, description, due date, members, labels, checklist, attachment, and custom fields on Standard and above). Properties that exceed Trello's field types (e.g., formula, rollup, relation, files, phone number, URL, email) are handled as follows: computed values (formulas, rollups) are written as plain-text custom fields; select and multi-select become labels; dates become due dates; numbers and text become custom fields on Trello Standard. We document all properties that could not be mapped natively during discovery and recommend the Trello Power-Up or manual process to fill any gaps.
What is FlitStack AI's role after migration cutover?
We support a 5-business-day post-migration window for reconciliation questions raised by the customer's team. This includes clarifying migration exceptions, providing re-run instructions for any failed batches, and answering questions about the automation inventory document. We do not provide ongoing admin support, Trello Butler rebuild execution, or workflow redesign as standard scope. Those are separate engagements or internal admin tasks. We do not provide post-migration training on Trello features or Power-Ups.
Related migrations
Sources: official documentation
- Working with Custom Fields — Trello Support
- Import data from Trello — Jira Cloud Administration Support
- File size and storage limits on Trello — Web Applications Stack Exchange
- Trello and GDPR — Trello Help
- Trello Support — Atlassian
- Recover a deleted description or card name — Trello Support
- Add an attachment to a card — Trello Support
Get a quote
Moving from Notion to Trello?
Tell us roughly how many records and objects you have. We scope the mapping and the Trello setup with you, then send a quote.
Get a quote