Migrate from Redbooth to Trello

Redbooth Workspaces are the primary container and map directly to Trello Boards. We preserve the workspace name as the board name, the workspace description as the board description, and the member list as board members with the original Redbooth role preserved as a Trello member label or a note in the migration manifest. Archived workspaces map to Archived Boards, which Trello preserves and makes visible to Workspace admins.

Redbooth Task Lists inside a Workspace map to Trello Lists on the corresponding Board. We preserve the task list name and the sort-order weight field so that list sequence matches the source workspace. Task lists that contain only subtasks without parent tasks are imported as a standard list with a header card noting the original task list name.

Redbooth Tasks map to Trello Cards. We map task title to card name, task description (rich text) to card description, due date to card due date, start date to a Custom Field of type Date, priority (urgent/normal/low) to card label color, and assignee to card member. Status (open/resolved/archived) maps to card position in the appropriate list or to the Archive. Multiple assignees on a single Redbooth task are resolved by adding all assigned members to the Trello card.

Redbooth subtasks (Business-plan feature) are extracted as a flat list linked to their parent task ID. We create a Trello Checklist on each card and populate it with subtask title, completion status, and due date. Subtasks with nested subtasks are flattened into a single checklist level because Trello checklists do not support nesting. If the source account is on the Pro plan with no Advanced Subtasks, this object has no data and is skipped.

Redbooth task-level Comments migrate as Trello Card Comments. We preserve the comment body, author name (from the user mapping), and timestamp. Comment attachments (file URLs) are added to the migration attachment manifest for manual re-upload because Trello comments can include file attachments but Redbooth exports only the file URLs, not the files themselves. Emoji reactions on Redbooth comments are not migratable.

Redbooth workspace-level Notes are standalone rich-text objects not attached to a specific task. Trello has no workspace-level note equivalent, so we create a header card on the destination Board with the Note title as the card name and the Note body as the card description, labeled with a Migration Note label so the customer can identify and reorganize these manually post-migration.

Redbooth workspace-level Conversations are threaded discussions not tied to a specific task. Trello has no board-level or workspace-level conversation feature; discussions happen on cards. We export Conversations as a separate dataset (author, thread title, thread body, timestamp) in a JSON file and alert the customer that these threads cannot be recreated in Trello natively. Options are to recreate key conversations as cards, move them to a connected tool like Confluence or Slack, or accept them as a historical reference document.

Redbooth user profiles (name, email, avatar) map to Trello members on the corresponding Board. We match by email address. Redbooth role hierarchy (Admin, External, Participant) does not have a direct Trello equivalent; we document role assignments per workspace in the migration manifest and advise the customer to configure Trello Workspace roles and Board permissions manually post-migration. Inactive Redbooth users are imported as inactive Trello members at the customer's request.

Redbooth workspace-scoped tags map to Trello board-level Labels. We preserve the tag name, map Redbooth tag color to the closest Trello label color, and reproduce the task-to-tag associations as Label assignments on each card. Tag groups (Custom Tag Groups on Business plan) map to Trello label categories implemented as separate label sets per board or as a consistent color-coding scheme.

Time tracking entries (Pro+ feature) are exported as a structured CSV with duration, user, task reference, and date. Trello has no native time-tracking object; we recommend a Power-Up like Planyo, Timely, or Timestracer for post-migration time tracking. The CSV is delivered as a separate artifact for the customer's admin to import into their chosen tool. We also flag tasks that had time entries so the customer can cross-reference logged hours against the correct cards.

Redbooth's Timeline View captures task start dates, end dates, and dependencies as Gantt-style data. Trello has no native Gantt or timeline view. We extract all task start/end date pairs and map them to Trello Custom Fields of type Date (Start Date and End Date), enabling teams to view the project schedule on cards. Complex dependency chains (Task A must finish before Task B starts) cannot be represented as Trello card dependencies without the Enhancement by Polypane or Tapflow Power-Up, which the customer can install post-migration.

Redbooth task-level custom fields map to Trello Custom Fields using a type-matching strategy: Redbooth text fields map to Trello Text, numeric fields to Number, date fields to Date, and dropdown or multi-select fields to Dropdown. We flag any Redbooth custom field name exceeding 25 characters (Trello's maximum field name length) and truncate or abbreviate per the customer's preference during scoping. Board-level Custom Fields in Trello are created before card import so that values can be written during the import phase.

Redbooth exports file URLs and metadata, not actual files. We extract the full attachment manifest (task ID, file name, file URL, uploader, date) and alert the customer that each file must be manually downloaded from Redbooth and re-uploaded to the corresponding Trello card post-migration. We provide the manifest as a CSV with source and destination card references to make the manual re-upload process traceable. Files stored in Redbooth integrations (Google Drive, Dropbox, OneDrive) retain their external links; we note these in the manifest so the customer can decide whether to link or re-upload.