Migrate from UpWave to monday Work Management

Each UpWave Board maps to a monday.com Board. During scoping we document the board name, column names, column order, and card count for every source board. monday.com boards are created with the same name and structure before card migration begins. If the customer uses UpWave Teams to group boards, we map those to monday.com Workspaces as the top-level organizational container.

UpWave Cards map directly to monday.com Items. The card title becomes the Item name. The UpWave column assignment (e.g., To Do, In Progress, Done) maps to a monday.com Status column. We create the Status column values to match UpWave column names during board setup. Card color maps to a Labels column or to the Status column color scheme, depending on how the customer uses color in UpWave.

UpWave subtasks export as nested rows with a parent-card reference. We flatten these into separate Item rows and use monday.com's Subitem feature to attach them to their parent Item, preserving the hierarchy. If the parent Item has not yet been created in monday.com, the subtask rows wait in a holding queue until the parent is resolved during migration.

UpWave column names export as part of each card row. We map each UpWave field (Assignee, Due Date, Completed Date, Estimate, Time Spent, Color) to the nearest monday.com Column Type: Assignee maps to People, Due Date maps to Date, Completed Date maps to a second Date column or a Checkbox indicating completion, and Estimate and Time Spent map to Numbers columns (or native time-tracking if the monday.com plan supports it). Any custom UpWave columns without a direct equivalent become a Numbers or Text column and are flagged in the migration report.

UpWave assignees export as a comma-separated list of names per card. We split these into individual user references and resolve them by email against monday.com workspace members. Any assignee in UpWave who does not have a corresponding monday.com user account is added to the reconciliation queue; the customer provisions the account before that batch migrates. Multi-assignee cards map to monday.com's multi-select People column.

UpWave due dates migrate to a monday.com Date column. We normalize all dates to UTC before import. If the UpWave export originated from a user in a different timezone than the migration account, we flag those rows in the reconciliation report. Completed dates migrate to a second Date column or a Checkbox column (checked = completed, unchecked = open) depending on the customer's preference for tracking completion in monday.com.

Estimate and Time Spent fields migrate only when time tracking was explicitly enabled on the UpWave board. We check board settings during scoping and flag any boards where these fields will be absent from the export. If monday.com is on a Pro or Enterprise plan, Time Spent maps to the native time-tracking column. Otherwise it lands as a Numbers column with the total minutes entered manually per item. Estimate maps to a Numbers column labeled Estimate regardless of plan.

UpWave file attachments are not included in CSV or JSON exports and live only in UpWave's storage. We flag every card with attachments during discovery and instruct the customer to download them via UpWave's file interface before migration. After migration, the customer manually uploads attachments to the corresponding monday.com Item. We do not automate file transfer between cloud storage systems as part of standard scope.

UpWave Workflow automations (triggers, conditions, automated actions) exist only in the platform UI and are not included in any export. We document the active Workflow rules during the discovery call: trigger type, conditions, and resulting action for each rule. This inventory is delivered as a written document with a monday.com automation recipe equivalent for each rule. The customer's admin rebuilds them in monday.com's automation builder. Workflows are not migrated as code.

UpWave Teams group boards and members. We map each UpWave Team to a monday.com Workspace. Member assignments migrate by email match. If monday.com plan supports multiple workspaces (Standard and above), each UpWave team becomes its own monday.com workspace. On Basic plans, boards are organized within a single workspace using Folders.

UpWave card colors export as hex values or named colors. We map these to a monday.com Labels column with color-coded labels matching the source, or alternatively to Status column colors if the customer prefers a cleaner board view. The customer selects the preferred approach during scoping.

UpWave time-tracking fields only exist when the board-level setting was enabled. During scoping we audit every board for time-tracking status and separate boards into two groups: those with time-tracking (mapping to native monday.com time-tracking on Pro/Enterprise) and those without (mapping to Numbers columns). This affects the column schema design for each destination board.