Migrate from AGILITY to Microsoft Project

AGILITY Projects map 1:1 to Microsoft Project files (.mpp) or Project Online projects. Each AGILITY Project OID becomes the root MS Project node. The AGILITY Project description, Owner, and Team assignments map to MS Project Project Summary Task fields and project-level custom fields. We create the destination project first and use its Project ID as the parent context for all subsequent task imports.

AGILITY Iterations (with start date, end date, status, and velocity) map to MS Project Summary Tasks or milestone groupings. The iteration start/end dates become the Summary Task Start and Finish dates. Stories and Tasks within the iteration inherit the iteration as a Summary Task parent. Iteration status (Active/Closed/Planning) does not map to a native MS Project field; we store it in a custom column iteration_status__c.

AGILITY Stories are primary work items with story points, status, assignee, and custom fields. They map to MS Project tasks with the Story title as Task Name, story points stored in a custom column (e.g., StoryPoints__c), and status mapped to a custom column or MS Project text flag field. Parent-child relationships with Tasks are preserved via MS Project outline hierarchy (Summary Task/subtask). We resolve the parent Story OID to the destination Task ID during import.

AGILITY Defects share the primary work item schema with Stories and include severity, detected-in-iteration, and resolution fields. We map Defects to MS Project tasks with the defect title as Task Name, severity stored in a custom column, and the detected iteration reference stored as a text link to the summary task. Defect-to-Story linking is preserved via MS Project predecessor/successor relationships or a custom cross-reference column.

AGILITY Tasks are child work items under Stories or Defects with assignees, estimated hours, and status. They map directly to MS Project tasks with the assignee resolved to a Resource assignment, estimated hours mapped to the MS Project Duration or Work field (depending on the customer's resource-calendar preference), and task status mapped to a custom column. Parent links are preserved by matching the AGILITY parent OID to the destination Task ID.

AGILITY custom fields exist on Stories, Defects, Tasks, and Iterations. During discovery we extract the field System Name (not display label) for each custom field and create a corresponding custom column in MS Project using the display label as the column header. Field types map as follows: text to Text column, number to Number column, date to Date column, checkbox to Flag column, and drop-down to Text column with documented value set. Data Mart column names (which use System Names) are translated to human-readable column headers before import.

AGILITY attachments are stored with their own OID registry separate from the work-item JSON payload. We export attachment binaries independently, upload them to a SharePoint document library or Project Online attachment endpoint, and re-associate them with the corresponding MS Project tasks using a cross-reference table mapping source OID to destination URL. If the destination uses MS Project Desktop (MPP), attachments are embedded as hyperlinks pointing to the SharePoint library location.

AGILITY Comments attached to work items carry author, timestamp, and body text. We migrate comments as MS Project task Notes, formatted with the author name, timestamp, and body text on separate lines. If multiple comments exist on a single work item, they are concatenated in chronological order within the Notes field. Author attribution is preserved as a text prefix.

AGILITY Test Sets aggregate Test Cases and carry status, custom fields, and iteration assignments. Microsoft Project has no native test management object. We export Test Set metadata as a structured CSV inventory during discovery and flag the Test Set object as requiring manual recreation in a dedicated test management tool (Azure Test Plans, Zephyr, or qTest). The CSV includes Test Set name, member Test Case OIDs, status, and any relevant custom field values.

AGILITY Test Cases carry steps, expected results, and custom fields. They exist in the AGILITY Data Mart and have no MS Project equivalent. We export Test Case metadata (title, steps, expected results, custom fields) as a structured CSV inventory. The test steps and expected results are exported as multi-line text for manual entry into the customer's chosen test management tool. Any Test Case fields that overlap with task fields (assignee, status, iteration) are included in the task migration pass.

AGILITY Issues are tracked in Fact.Issue and behave like standalone defects with their own schema (status, priority, assignee, description). They map to MS Project tasks with the Issue title as Task Name, priority as a custom column, and the original Issue ID preserved in a custom column for traceability. Issues are imported after Stories and Defects to avoid ID collision in the cross-reference table.

AGILITY Members carry display name, email, role, and team membership. We map Members to MS Project Resources using email as the dedupe key. AGILITY roles (Developer, QA, Project Manager) map to Resource custom fields (e.g., Role__c) rather than the standard Resource Type field, since MS Project's standard Resource Type (Work/Material/Cost) is not semantically equivalent to AGILITY team roles. AD-integrated AGILITY orgs may have Members sourced from an external directory; we detect and reconcile against the target SharePoint or Project Online user directory.