Migrate from ProjectManager to Microsoft Project

Each ProjectManager Project maps to a single Microsoft Project .mpp file. We export project metadata via GET /api/data/projects including name, start date, finish date, status, and custom ProjectFields. The .mpp file is created in Microsoft Project desktop before data import. We preserve the ProjectManager project ID as a custom field in the .mpp for cross-reference. Multi-project portfolios that exist as separate ProjectManager Workspaces do not merge; each generates a separate .mpp file.

ProjectManager Tasks map directly to Microsoft Project tasks. We reconstruct the WBS hierarchy by exporting parent-child task relationships and setting Microsoft Project Outline Number and Outline Level. Dependency relationships (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) are imported as PredecessorLink records in the .mpp. Tasks are sequenced for import in topological dependency order to prevent ProjectManager's dynamic scheduler cascade logic from overwriting manually-set dates during export.

ProjectManager TaskAssignees link Resources to Tasks and map to Microsoft Project Assignments. We resolve the ProjectManager Resource ID to the Microsoft Project Resource GUID and write the Assignment with Units (percentage of resource capacity), Start, and Finish from the Task dates. If a ProjectManager TaskAssignee carries a billing rate that differs from the Resource standard rate, we create an Assignment cost entry rather than modifying the Resource cost table.

ProjectManager ProjectFields (custom properties scoped to the Workspace) require a two-step process identical to ProjectManager's own API behavior. We first discover existing ProjectField definitions via GET /api/data/projects/fields, then create corresponding Microsoft Project custom fields via the Field dialog or CSV import mapping. Custom field types (string, number, date, choice) map to Microsoft Project Text, Number, Date, and Flag or OutlineCode fields respectively. After field definitions exist in the .mpp, we write per-record values in a second pass.

TaskFields work identically to ProjectFields in ProjectManager and map to Microsoft Project task custom fields (Text, Number, Date, Flag, OutlineCode). We handle both field definitions and per-record values using the same two-pass approach: define first, then write. Not all Microsoft Project custom field types support the same filtering and grouping options as ProjectManager TaskFields; we flag any field type that loses functionality post-migration during scoping.

ProjectManager Resources map to Microsoft Project Resources. We transfer the resource name, type (material vs work), initials, email, max units, and calendar. ProjectManager availability windows and cost rates map to Microsoft Project Resource calendar exceptions and cost rate tables. If the ProjectManager Resource has ResourceSkills attached, we add them as Text custom fields on the Microsoft Project Resource since Microsoft Project does not have a native skills object.

ProjectManager ResourceTeams (grouping Resources for scheduling) map to Microsoft Project Resource Groups. We preserve team memberships and cross-reference with TaskAssignees to verify workload views are accurate after migration. Note that ResourceTeams and the separate Teams object in ProjectManager are distinct; only the scheduling grouping (ResourceTeams) maps to a native Microsoft Project concept.

ProjectManager Teams (organizational membership, distinct from ResourceTeams) have no direct Microsoft Project equivalent. We migrate team membership as a Text custom field on the Resource record. The customer decides whether this field is informational only or used to filter resource views.

ProjectManager Risks are standalone objects linked to Projects. Microsoft Project has no native Risk object. We migrate open Risks as task-level custom fields (Risk ID, Severity, Status, Mitigation) or as Notes attached to the associated summary task, depending on the customer's preference during scoping. RiskFiles attached to ProjectManager Risks migrate as file links in the .mpp Notes field.

ProjectManager Timesheet records capture actual hours logged against Tasks. We migrate Timesheet hours as Actual Work on the corresponding Microsoft Project Assignment, with the Original Estimated Work reduced to distinguish planned from actual. Historical billing rates embedded in Timesheet records may not map directly to Microsoft Project's cost model; we flag these during discovery and migrate hours only, leaving rate reconciliation to the customer's finance team.