Migrate from OneDeck to Asana

OneDeck Boards map directly to Asana Projects. We preserve board name, description, and the default view configuration as the initial project view. Board-level custom fields migrate to project-level custom fields. All tasks, records, and attachments within the board move as child records of the resulting Asana Project.

OneDeck Records map to Asana Tasks. The Record title becomes Task name, description migrates as rich text, assignee maps from the OneDeck owner reference to the Asana assignee, due date maps directly, and status from the board column becomes the Asana Section within the project. Record-level custom fields migrate as task custom fields.

Tasks nested within a OneDeck Record map to Asana Subtasks of the parent Task. Subtask title, assignee, due date, and status migrate. If OneDeck subtasks have their own custom fields, those migrate as subtask custom fields. Subtask ordering is preserved by insertion sequence at migration time.

OneDeck custom fields on Records map to Asana task custom fields. We handle type mapping: text fields map to Asana text, number to number, date to date, dropdown to single-select, multi-checkbox to multi-select, and file attachment fields to file attachments in Asana. Global custom fields (shared across a OneDeck workspace) become portfolio-level or project-level custom fields in Asana depending on usage scope.

OneDeck supports multiple view types per board including Kanban, Table, and Calendar. We migrate each view as a named view on the Asana Project so teams retain their visual structure. Kanban becomes an Asana Board view with columns mapped to OneDeck status groups; Table becomes List view; Calendar becomes Calendar view. View configuration is preserved but not the view's saved filter state.

OneDeck status groups and swimlanes within a board map to Asana Sections within the project. Section names and the order of sections migrate. If OneDeck uses custom status values per board, we map each to a named Section in Asana. Tasks are placed in their corresponding Section based on the source status value.

OneDeck user accounts and task assignee assignments map to Asana workspace Users and Task assignees. We resolve by email match. Any OneDeck user without a matching Asana User is held in an orphaned-assignee queue for the customer's admin to provision before migration continues. We flag inactive assignees so the admin can decide whether to assign to active users or leave tasks unassigned.

OneDeck Document Builder PDFs (quotes, invoices, work orders) export as file attachments linked to the parent Task. We transfer the underlying file content and file name. Asana does not have a native document generation engine equivalent to OneDeck's Document Builder; the customer should plan to generate new documents in Asana or via an integrated document tool post-migration. PDF formatting may differ from OneDeck's rendered output; we recommend spot-checking document files post-migration.

Task and Record comments migrate as Asana Task comments where the OneDeck API exposes them. Comment availability depends on OneDeck plan tier and workspace configuration. We verify comment accessibility during discovery and include comment migration in scope only when exposed. If comments are inaccessible, we document the gap and note that comment history will not appear in Asana unless manually exported separately.

OneDeck automation scenarios use platform-specific triggers (Record Created, Record Updated, Document Published) and actions with no export mechanism. We do not migrate automation scenarios as code. During discovery, we identify every active scenario, capture its trigger conditions and actions in a written inventory, and deliver this to the customer. The customer must manually rebuild each scenario in Asana Rules or a third-party automation tool post-migration.

OneDeck workspaces map to Asana Workspaces for single-org migrations. If the customer uses multiple OneDeck workspaces, we map each to a separate Asana Workspace or to Projects within a single Asana Workspace depending on the target structure. Workspace-level settings (billing, user management) are not migrated and are handled by the customer directly in Asana.

File attachments on OneDeck Records and Tasks migrate as Asana task attachments. We transfer the file content, file name, and upload timestamp. Files exceeding Asana's 100MB per-attachment API limit are flagged and skipped during migration with a count reported to the customer for manual handling. Image attachments migrate with full fidelity; video and compressed archive formats are subject to the same size limit.

OneDeck tags on Records and Tasks migrate to Asana Tags. Tag names and the association to tasks migrate. Tag color is not transferable and defaults in Asana. Tags used for content classification migrate as-is; if tags represent a classification taxonomy that should become a custom field in Asana, we recommend converting them to a multi-select custom field during scoping.