Migrate from OneDeck to Trello

OneDeck Boards map 1:1 to Trello Boards, preserving board name, description, and default view configuration. We create the Trello Board first as the parent container for all subsequent List and Card imports. Workspace-level organization in OneDeck maps to Trello Workspace or Team structures depending on the destination plan.

OneDeck Tasks map to Trello Cards with title, description (as Card description), due date, and status preserved. Task priority from OneDeck maps to a Trello Label with color coding. Subtasks in OneDeck migrate as Checklist items on the parent Card. Card position within the List is preserved by index order at migration time.

OneDeck List-style views map directly to Trello Lists. We create Lists on the destination Board and map the OneDeck list name to the Trello List name. If OneDeck uses column configurations beyond name and order, we preserve those as Card fields or Labels. Multi-board views in OneDeck split into multiple Trello Boards where the view-to-board relationship cannot be preserved in a single destination Board.

OneDeck custom fields on Tasks map to Trello Custom Fields Power-Up. We extract all custom field definitions during discovery and map field types: text fields to Trello text fields, number fields to number fields, date fields to date fields, and dropdown fields to dropdown fields. Boolean fields map to a Trello label or checkbox field. The customer must have a Power-Up-enabled Trello plan to use custom fields.

OneDeck user accounts map to Trello Members by email address match. We extract every distinct user referenced as task assignee or board member and match against the destination Trello workspace members. Users without a matching Trello account go to a reconciliation queue for the customer admin to provision before card import resumes.

Task assignee assignments migrate as Card Members. We resolve the OneDeck assignee user reference to the Trello Member record via the User mapping and assign the Member to the Card at migration time. Orphaned assignees (user in OneDeck without a Trello Member match) are noted in the reconciliation report.

OneDeck task attachments migrate as Trello Card attachments. We download the file from OneDeck, store it temporarily, and upload to the destination Card via the Trello API. File type and original filename are preserved. Large files are chunked to stay within Trello's attachment size limits.

OneDeck task comments migrate as Trello Card Comments when the OneDeck plan exposes them via API. Comment text, author (mapped via User lookup), and timestamp are preserved. We verify comment accessibility during discovery and include them in scope only when the API exposes them. When comments are inaccessible, we document the gap and inform the team that comment history will not appear in Trello unless manually exported.

OneDeck task labels map to Trello Labels on the Card. We create Labels on the destination Board with matching names and colors. If OneDeck label names exceed Trello's label name limit, we truncate and note the original name in a custom field. Labels with no matching color in Trello are assigned the nearest available color.

OneDeck Document Builder PDFs (quotes, invoices, work orders) migrate as Card attachments. We export the PDF file content, but the rendered layout may not survive transfer intact because Trello does not have a comparable document generation engine. We recommend reviewing a sample of migrated documents post-migration to confirm formatting integrity, and we flag this as a review item before sign-off.

OneDeck Automation Scenarios do not export. We identify every active scenario during discovery, capture its trigger conditions and actions in a written inventory, and deliver this to the customer as a handoff document for manual rebuild in Trello Butler. The rebuild scope is often underestimated during planning; we flag this explicitly so teams budget admin time accordingly.

Task due dates migrate as Card due dates in Trello. The due date, due time (if present), and due complete status all transfer. Card start dates from OneDeck map to a custom field on the Trello Card since Trello does not have a native start date field unless the Card 2.0 Power-Up is enabled.

OneDeck users who are watching or subscribed to a board map to Trello Board Members with Normal membership type. Admin-level board users in OneDeck map to Admin membership in Trello. The customer admin should review membership levels post-migration to confirm the intended permission structure.