Migrate from Demand Metric to Asana

Demand Metric Projects map 1:1 to Asana Projects. We preserve project name, description, start date, due date, and status. Status mapping: Demand Metric Active becomes Asana non-archived; Demand Metric Archived becomes Asana archived. Multiple Demand Metric workspaces map to multiple Asana Projects within a single Asana workspace, or to separate Asana workspaces depending on the customer's organizational preference established during scoping.

Demand Metric Tasks migrate as Asana Tasks with title, description (migrated as rich text notes), assignees, due dates, and priority preserved. Priority mapping: High maps to Asana High priority, Medium to Medium, Low to Low. Completed status in Demand Metric maps to completed tasks in Asana. We set the Task created_at and completed_at from Demand Metric's timestamps where available.

Demand Metric subtasks migrate as Asana Subtasks (child tasks) under the parent Asana Task. We preserve the nesting depth from Demand Metric — if a subtask has its own subtasks, we replicate the hierarchy in Asana. Asana supports one level of subtasks natively; deeper nesting is flattened to one level with a note indicating the original depth.

Demand Metric tags are extracted as a vocabulary list during discovery. We apply them as Asana Tags by default (using the Tags API), which allows cross-project filtering in Asana's My Tasks and project views. If the customer uses a structured tag taxonomy with defined values (e.g., Department, Campaign Type, Priority Category), we map them to Asana Custom Fields (single-select or multi-select) for stronger filtering at the project and task level. The customer chooses the strategy during scoping.

Demand Metric team members and assignees migrate as user references in Asana. We match by email address against the Asana workspace membership. Any assignee without a matching Asana user is held in a reconciliation queue for the customer's admin to provision before the task import phase begins. The mapping report lists every unmapped assignee and the tasks they are assigned to.

Demand Metric custom properties on tasks require field-level mapping against Asana's Custom Fields schema. We identify all custom properties during discovery, map each to a typed Asana Custom Field (text, number, date, enum, or multi-enum), and apply field configuration in Asana before loading any tasks. If a Demand Metric custom field has an incompatible type (e.g., a free-form text field that functions as a URL), we map it to a text Custom Field in Asana and flag it for admin review.

Demand Metric Calendar view layouts are view-level display metadata, not stored as a distinct data object. They cannot be migrated. Milestone dates from Demand Metric tasks migrate as Tasks with the Asana Due Date set; the calendar layout itself is recreated by the customer in Asana Calendar View post-migration. We flag all milestone tasks during extraction so the customer can apply the Asana Milestone marker.

The 1,000+ templates, playbooks, toolkits, and training resources on Demand Metric are content objects stored on the platform, not customer project data. They cannot be exported via CSV or any API. We treat them as reference material and flag them for manual re-download from Demand Metric or identification of equivalent Asana templates post-migration. We do not include template content in the migration scope.

Demand Metric attachments embedded in tasks and projects have no documented export API endpoint. We perform a separate attachment extraction pass: we identify every task with an attachment during discovery, extract the file URLs or download references, and re-upload them to the corresponding Asana task via the Asana Attachments API. For attachments with no accessible URL, we document the task and attachment name for manual re-upload post-migration.

Demand Metric marketing calendar entries that aggregate tasks and milestones by date are not a distinct data object in the platform — they are a view of tasks filtered by date. We extract the underlying task records with their due dates and load them as Asana Tasks with Due Date fields. The marketing calendar layout is view metadata and does not migrate; we flag the date-scoped task sets during discovery so the customer can apply Asana Calendar View post-migration.

Cross-project tag filters in Demand Metric are view-level metadata that organize tasks across multiple projects by tag. They do not transfer as structured filter objects. We preserve the full tag vocabulary during migration and recommend that the customer re-applies cross-project tag views in Asana using the My Tasks filter bar or Asana's portfolio-level tagging view. We deliver a tag taxonomy document listing every distinct tag in use.

Demand Metric project status indicators (active, on hold, complete) map to Asana project archived state and task completion state. On-hold status in Demand Metric becomes an active but non-archived project in Asana with a tag label On Hold so that the customer's team can identify paused work without archiving the project entirely.