Migrate from Spreadsheet.com to Trello

Each Spreadsheet.com Workbook maps to a Trello Board. If the customer has multiple related Workbooks covering a single project, we consolidate them into a single Board with multiple Lists rather than spreading across Boards, since Trello's free tier limits Boards per Workspace. Workspace creation happens before Board creation and requires the customer to set up or designate a Trello Workspace during discovery.

A single Spreadsheet.com Sheet maps to a Trello List within the destination Board. When a Workbook contains multiple Sheets that represent sequential phases (e.g., Backlog, In Progress, Done), each Sheet maps to a List in the same Board. When Sheets represent unrelated datasets, we split them into separate Boards or use Labels to separate concerns within a single Board.

Every Spreadsheet.com Row maps to a Trello Card. Card titles come from the row's primary identifier column (often the first column or a Name column). Card descriptions populate from the remaining column values formatted as a markdown table or line-by-line key-value pairs. We preserve the original row order as Card position within each List to maintain sequencing intent.

Spreadsheet.com column headers map to Trello custom fields on each Card. Column types require translation: date columns become Trello date custom fields; number and currency columns become number custom fields; checkbox columns become checkbox custom fields; multi-select and user picker columns become Trello dropdown or label custom fields. Formula-computed columns cannot migrate as live calculations; we flag these for manual entry or a separate calculation sheet as a reference document.

Spreadsheet.com's native Kanban view configuration (column grouping field and swim lanes) maps to List structure and optional Labels in Trello. We infer the grouping column from the view configuration and apply it as the List split: each distinct value in the grouping column becomes a List, and cards land in the List matching their row's group value. This reconstruction produces the same card separation as the original Kanban view.

Spreadsheet.com Gantt and Calendar views have no direct Trello equivalent at the free or Standard tier. We preserve the temporal data (start date, due date, duration) as date custom fields on each Card, and recommend the Calendar Power-Up (Premium) or a Timeline integration post-migration. The original Card view data maps to the Card description.

File attachments stored in Spreadsheet.com cells export as file references. We map them to Trello Card attachments with the original filename preserved. Trello's attachment size limits apply (10MB free, 250MB Standard, unlimited Premium); attachments exceeding the target tier's limit are flagged for the customer to re-upload manually or provision a cloud storage link.

Spreadsheet.com cell-level and sheet-level comments migrate as Trello Card Comments. We append comment author attribution and timestamp to each comment block. If the customer used @mentions in Spreadsheet.com comments, we document them in the migration report for manual re-mention in Trello since Trello comment @mentions resolve differently.

Spreadsheet.com user accounts have no export path since the platform shut down. We reconstruct the user-to-record assignment from workbook sharing metadata where available and map it to Trello Member assignments on Cards. The customer provisions their Trello Workspace and invites team members before migration; we then match by email or name to assign Cards to the correct Members.

Spreadsheet.com web form submissions stored as rows in a Sheet map to Cards in Trello. Form field definitions do not have a Trello equivalent; we document the field names and types for the customer to configure as custom fields in the target Board. Conditional form logic cannot be replicated and is flagged for rebuild in Trello Forms (Standard tier) or a third-party form tool.

Spreadsheet.com automation rules (triggers, conditions, and multi-step actions) have no export mechanism and were stored server-side without user-facing backup. We document every discovered automation during discovery calls, describing the trigger, conditions, and actions in plain language so the customer's admin can rebuild equivalent logic in Trello Butler or a Zapier/Make workflow. Multi-step conditional chains require full manual reconstruction.

Spreadsheet.com workbook templates export as standard workbooks. We treat them identically to regular workbooks during migration, preserving the template structure as a Trello Board with the same Lists and custom field schema. The customer configures Board Templates manually in Trello post-migration from the migrated Board.