Migrate from UpWave to Asana

UpWave boards export as a single structured CSV or JSON file capturing all cards, columns, and metadata in one pass. We create an Asana Project for each UpWave board, preserving the board name as the project name. The project description carries the original board description if one exists. We use the Asana Projects API to create each project before importing the card rows.

Each UpWave card becomes a single Asana task. The card title maps to task name, the card description maps to task notes, the completed date maps to completed_at, the due date maps to due_on, and the card color maps to a custom text field card_color__c. We resolve the card's column assignment to an Asana section name within the target project before task insert.

UpWave subtasks nested under a card export as separate rows with a parent-card reference. We create each subtask as an Asana subtask under its parent task by referencing the parent task's gid from the preceding import phase. Subtask title and completion status migrate directly. Ordering is preserved by inserting subtasks sequentially within the parent task's subtask list.

UpWave column names export as part of each card row and represent the card's current board position. We extract all distinct column names from the export, create corresponding Asana Sections within the project, and assign each card row to its section at task insert time. Column ordering in the exported CSV reflects the state at export time only; we document this limitation in the migration report.

UpWave assignees export as a comma-separated string of display names per card. We split the string into individual assignee names, resolve each by email against the Asana workspace User table, and set the task's assignee field to the matched User gid. Cards with unresolvable assignees (no matching Asana user) are logged to the reconciliation queue for the admin to provision or reassign. Asana only supports one assignee per task; cards with multiple assignees in UpWave create one primary-assignee task with a note listing the remaining assignees.

Due dates export from UpWave in the timezone of the user who initiated the export. We normalize all date fields to UTC before constructing the Asana due_on value. If the export contains dates from multiple timezone sources (common in multi-timezone teams), we flag rows where the source timezone differs from the workspace's configured timezone and log them in the migration report for manual review.

Completed dates export alongside due dates in UpWave's CSV and JSON. We set Asana's completed flag to true for any card with a completed date, and set the task's completed_at to the UTC-normalized timestamp. Cards without a completed date import as incomplete tasks. This field carries the same timezone normalization requirement as due dates.

Estimate and time-spent fields only appear in UpWave exports for boards where time tracking was explicitly enabled. We detect this condition during scoping by checking board settings in the exported metadata. For boards with time tracking enabled, we create two Asana custom fields: estimate_hours__c (number) and time_spent_hours__c (number). Boards without time tracking enabled generate no target custom fields and no mapping rows for these values.

UpWave cards carry a color label from a fixed palette. We create a custom text field card_color__c on each project and populate it from the color value in the card export. The customer chooses during scoping whether to map the UpWave color palette to Asana task color dots (available on Asana Business and Enterprise) or retain it as a text custom field value for filtering and reporting.

UpWave workspaces contain multiple boards. We export each board independently and import each as a separate Asana Project. Projects can be grouped into an Asana Portfolio if the customer has Business or Enterprise; otherwise they remain as independent projects. We document the workspace-to-portfolio mapping in the migration report for the admin to configure post-migration.

UpWave workspaces support Team grouping of members. We map UpWave team membership to Asana Teams using the workspace member list. If the customer's Asana destination is organized by team, we create corresponding Asana Teams during the initial setup phase. Member assignment per task resolves to the assignee mapping step.

UpWave file attachments are not included in the standard CSV or JSON export. We flag every card that carries an attachment during the scoping audit and instruct the customer to download them manually via UpWave's file interface before the migration window. We do not migrate attachments automatically and do not include them in the migration cost. The customer bears responsibility for re-attaching files post-migration or using a linked resource approach (Google Drive, Box, Dropbox) in Asana.