Migrate from OneDeck to monday Work Management

OneDeck Boards map directly to monday.com Boards, preserving board name, description, and workspace assignment. Each board's default view configuration migrates as a named view. We extract the full board structure during discovery and create destination boards in the correct workspace hierarchy before any items are imported. Workspace-level access permissions require manual configuration in monday.com admin settings post-migration.

OneDeck Tasks on a board map to monday.com Items within the equivalent board and group. We preserve title, description (as rich text), status (mapped to a monday.com Status column), assignee (via email match to monday.com users), due date, and custom field values. Item creation timestamps migrate as a custom date column since monday.com does not expose native creation date as editable.

OneDeck Subtasks nested under a parent task map to monday.com Subitems. The subitem inherits the parent item's board and group context. We preserve subitem title, description, assignee, due date, and any subitem-specific custom field values. Note that monday.com subitem availability depends on the plan tier; we verify subitem support during discovery and flag if the destination account's tier does not support subitems.

OneDeck Groups within a board map to monday.com Groups. Group names and ordering migrate directly. We extract group names from the OneDeck board structure and create matching groups in the monday.com board before item import. Items are inserted into their corresponding groups by referencing the source group assignment stored in the OneDeck task record.

OneDeck custom fields per record map to monday.com column types based on the field's data type. Text fields become Text columns; number fields become Numbers columns; date fields become Date columns; person fields become Person columns; checkbox fields become Checkbox columns. We extract the complete custom field schema during discovery and configure equivalent columns in monday.com before migration. Some OneDeck field types may require a multi-select or text column as the closest monday.com equivalent, and we document these approximations in the mapping spec.

OneDeck user accounts and task assignee assignments migrate as owner references. We match OneDeck user email addresses to monday.com User records by email. Any OneDeck Assignee without a matching monday.com User is flagged in a reconciliation queue for the customer admin to provision before item import resumes. Orphaned assignee references (where the user no longer exists) are resolved as a nullable assignee field.

OneDeck Documents generated by Document Builder (quotes, invoices, work orders) migrate as file content and structured data fields. The file attachments migrate to monday.com file columns or item file sections. The underlying data fields (line items, totals, dates, client info) migrate as text or number columns. We flag that OneDeck Document Builder formatting does not survive migration; the rendered PDF layout is not transferable. Post-migration review of document rendering is required before sign-off.

OneDeck comments on tasks and records migrate to monday.com Updates on the corresponding item if the OneDeck API exposes comment history. We verify comment accessibility during discovery (availability varies by OneDeck plan and workspace configuration). If comments are inaccessible via API, we document the gap and inform the customer that comment history will not appear in monday.com unless manually exported or screenshots are captured.

OneDeck automation scenarios have no export mechanism and do not migrate as code. We identify every active scenario during discovery, capture its trigger conditions and actions in a written inventory, and deliver this document to the customer for manual rebuild in monday.com's automation builder. monday.com automations use a trigger-action model that requires rebuilding each scenario individually. This is a commonly underestimated step; we explicitly flag the rebuild effort in our scoping document.

OneDeck Workspaces containing multiple boards map to monday.com Workspaces. We preserve the workspace name and map the contained boards into the equivalent monday.com workspace. If the customer's OneDeck workspace structure uses nested teams or department divisions that do not map directly to monday.com workspace hierarchy, we document the gap and recommend workspace naming conventions for the destination.

OneDeck tags on records migrate to monday.com Labels if the destination account is on a plan supporting labels. Labels migrate as a color-coded label set attached to the item. If labels are not available or the customer prefers, tags migrate as a Tags column (multi-select text) in monday.com. The customer chooses the preferred strategy during scoping, and we document the choice in the mapping spec.

OneDeck file attachments linked to records migrate as file attachments in monday.com. Files are associated with the corresponding item via monday.com's file upload API. Large file attachments (>10MB per file) are chunked for upload; very large volumes of attachments extend migration timeline. We verify file accessibility in OneDeck during discovery and include a file count in the migration scope document.