Migrate from Demand Metric to Microsoft Project

Demand Metric Projects map 1:1 to Microsoft Project projects. Project name, description, start date, and due date transfer directly. Status (active, archived) maps to a custom field or project stage indicator in Microsoft Project. If the destination is Project Online, we use the Project Online REST API (Projects endpoint) to create the project record. If the destination is Project for the Web, we use the Microsoft Graph API (projectRoot endpoint). Project workspace sites in SharePoint associated with Demand Metric projects do not migrate automatically; we flag them for manual re-creation in the Microsoft 365 tenant.

Demand Metric tasks map to Microsoft Project tasks with WBS hierarchy preserved. Subtasks in Demand Metric become indented subtasks under a Summary Task in Microsoft Project. Task name, description, start date, due date, priority, and status migrate directly. Task ID from Demand Metric is preserved as a custom column for reconciliation. Dependencies between tasks are not natively supported in Demand Metric, so task linkage does not carry forward — we document any dependency notes found in task descriptions for manual rebuild in Microsoft Project.

Demand Metric subtasks become Microsoft Project tasks indented under their parent Summary Task. The full nesting depth migrates as-is where the hierarchy is three levels or fewer. Deeper hierarchies are flattened to three levels with the original depth recorded in a custom WBS_depth column. We validate the indent structure against the source subtask count to ensure no orphaned tasks are left at the root level.

Demand Metric's cross-project tag vocabulary migrates to a Microsoft Project Text1 custom field (or a named classification column). Tags are preserved as space-delimited text values per task. Since Microsoft Project does not have a native tag or label object, we do not recreate cross-project tag-based filtering logic — this is view-level metadata that is lost. We deliver a tag vocabulary inventory document during discovery so the customer's admin can set up a SharePoint choice column or Power Automate flow for filtering if needed in the destination.

Demand Metric assignees map to Microsoft Project resources. We resolve each assignee by email lookup against the destination tenant's user directory (Azure AD for Project Online) or against the local resource sheet for Project desktop. If the assignee has no matching account in the destination, they are held in a reconciliation queue and migrated as text in the task's Assignment Notes field. Resource type (work vs material) is set to Work for all migrated team members.

Demand Metric task-assignee relationships migrate to Microsoft Project task assignments with the assigned resource and units (percent allocated) preserved. Where Demand Metric shows multiple assignees on a single task, we create one assignment row per resource in Microsoft Project. Assignment notes and comments migrate as task notes.

Demand Metric custom fields on tasks require schema mapping against Microsoft Project's custom column types. We identify all custom properties during discovery, classify each as Text, Number, Date, or Flag type in Microsoft Project, and create the custom columns in the destination project before data loading. Multi-select custom fields from Demand Metric flatten to pipe-delimited text in the Microsoft Project custom column.

Demand Metric marketing calendar entries with milestone markers (start date, end date, no associated task) migrate as zero-duration milestone tasks in Microsoft Project with the milestone name and date preserved. Recurring calendar milestones create individual milestone tasks in the destination. The calendar layout itself does not transfer — it is a view property in Demand Metric — so we document the date range and milestone names for manual calendar rebuild in the destination.

Demand Metric's library of 1,000+ templates, playbooks, and toolkits are platform-stored content objects that cannot be exported via CSV or API. We do not migrate them. We flag them as reference material and document the top 10-20 most-used templates by the customer for manual re-download from Demand Metric or replacement from the Microsoft Project template gallery post-migration.

Demand Metric's Calendar view is a view-level display property, not a data object. The calendar layout cannot be exported. We extract milestone dates and task date ranges from the calendar view as a structured data pass and re-create them as tasks and milestones in Microsoft Project, but the calendar visual itself must be rebuilt manually by the customer's project team.