Migrate from Demand Metric to monday Work Management

Demand Metric Projects map directly to monday.com Boards. We preserve project name, description, start date, and due date by creating a new Board in the destination workspace and populating the Board name and description fields. The board type (managing work, project, campaign, etc.) is set to Project by default during migration, and the customer can override this during scoping. Multiple Demand Metric projects in the same business unit can be grouped into a monday.com Workspace for organizational clarity.

Demand Metric Tasks migrate to monday.com Items on the target Board. Task title becomes Item name, description migrates as the Item description column, due date maps to the Date column, priority maps to Status column values, and assignee maps to the Person column. We resolve the Board reference from the source project-to-task relationship and insert Items in the correct board group during migration.

Demand Metric subtasks nested under a parent task migrate to monday.com Subitems. Subitems are created as child records of the parent Item using the monday.com subitems API. The parent Item must be created before subitem insertion, so we sequence the migration with parent Items first, then subitems in a second pass. Subitem fields (title, assignee, due date) map identically to the parent Item field mapping.

Demand Metric tags migrate to monday.com Labels on the target Board. We preserve the full tag vocabulary as label names and apply each label to the corresponding Item. monday.com labels are board-scoped by default; cross-project tag taxonomy from Demand Metric requires the customer to decide whether to use workspace-level labels (available on Pro and Enterprise) or accept board-scoped labels. We flag this decision during scoping and configure accordingly.

Demand Metric assignees and team members are resolved by email match against the monday.com workspace user list. We extract every distinct email address referenced in assignee fields across all projects and tasks, then match against monday.com User records during migration. Any assignee without a matching monday.com user is flagged in a reconciliation report for the customer's admin to provision before final import.

Demand Metric custom fields require field-level mapping against monday.com column types. Text, number, date, and dropdown fields map to monday.com Text Column, Number Column, Date Column, and Status Column respectively. Person-assigned custom fields map to the Person Column. We identify all custom field types during discovery, build a column schema on each target board before data import, and apply the mapping in a pre-migration phase. Fields with unsupported types (e.g., complex multi-select matrices) are flagged for manual re-creation.

Demand Metric marketing calendar milestones (date-bound tasks spanning projects) are extracted as Items with Date or Timeline columns set to the milestone date. We preserve the milestone name, date, and any assignee. Milestone Items are placed on a dedicated board (typically named Marketing Calendar) and grouped by month or campaign. The calendar layout itself is not migratable; we recommend rebuilding the calendar view in monday.com's Timeline or Calendar column after migration.

Demand Metric's library of 1,000+ templates, playbooks, and toolkits are platform-hosted content objects and are not exported via any API or CSV endpoint. We do not migrate them. We flag the complete list of templates referenced in active projects and provide a written reference guide for the customer to re-download from monday.com's template library post-migration, which contains comparable project templates.

Demand Metric Calendar view is a display layout property on the project, not a distinct data object. The calendar layout (which tasks appear on which date spans) cannot be extracted or transferred. We migrate the underlying task dates (which are date fields), and the customer recreates the Calendar or Timeline view on the monday.com board using those date columns.

Demand Metric workflows and automations are platform-built logic not exposed for export. We do not migrate them. We deliver a written inventory of every active Demand Metric workflow or automation with its trigger, conditions, and actions, mapped to a recommended monday.com Automation recipe. The customer's admin rebuilds them in monday.com's automation builder. Note: monday.com's legacy automation infrastructure requires migration to the new workflow builder by April 30, 2026 per monday.com's developer documentation.

Demand Metric attachments embedded in the library are not exportable via any documented API endpoint. We extract file references from task descriptions where URLs are present, and map them to monday.com's File Column or URL Column on the Item. For attachments that are hosted inside Demand Metric's library without public URLs, we flag these for manual re-upload post-migration.

Demand Metric task status values (e.g., Not Started, In Progress, Complete) map to monday.com Status Column options. We extract the distinct status vocabulary from the source during discovery, create matching Status Column options on each target board, and map each task's status to the corresponding option during import. Custom status labels are preserved as-is.