Migrate from Advantage to Microsoft Project

Each Advantage Project maps to a single Microsoft Project .mpp file or Project Online project site. Project metadata including name, description, start date, and finish date migrate directly. We create the destination project file structure before importing tasks and configure the project calendar to match the Advantage project's working time settings. Cross-project dependencies present a challenge in Microsoft Project desktop because linking tasks across separate .mpp files requires opening all files simultaneously; we document cross-project dependency chains for the customer to resolve using Project Server, Project Online, or a manual linking procedure post-migration.

Advantage Tasks map to Microsoft Project Tasks with task name, duration, start date, finish date, and percent complete preserved. Task hierarchy from Advantage (parent tasks and subtasks) maps to Microsoft Project outline levels using summary tasks and subtasks. The Advantage task ID is preserved in a custom text field (Text1) for reconciliation. Tasks without a duration (milestones) map to Microsoft Project milestones with zero duration.

Parent tasks in Advantage with subordinate child tasks map to Microsoft Project summary tasks. The summary task rollup dates (earliest start, latest finish) and percent complete are computed from child task data. We flag any Advantage parent tasks that have their own effort logged separate from children, because Microsoft Project summary task effort does not automatically roll up when the parent has direct assignment hours.

Advantage task relationships defined via Schema Manager or task-level linking map to Microsoft Project predecessor-successor dependencies. We map Finish-to-Start as the default, and use Start-to-Start, Finish-to-Finish, or Start-to-Finish where the Advantage relationship type indicates those variants. Lead time (negative lag) and lag time (positive lag) migrate to the Microsoft Project Lag field. Circular dependencies detected in Advantage are flagged for the customer to resolve before migration.

Advantage enterprise custom fields defined in Schema Manager require per-project recreation in Microsoft Project. We map each Advantage custom field to a Microsoft Project custom field (Text, Number, Cost, Flag, or Date based on the Advantage field type) and pre-create the column in each destination project file before data import. If the same custom field appears across multiple Advantage projects, we create it in each corresponding Microsoft Project file. The customer should note that Microsoft Project does not enforce a shared field definition across files; field consistency depends on manual adherence to a naming convention.

Advantage custom objects (defined in Schema Manager with their own fields, pick lists, and relationships) have no direct Microsoft Project equivalent. We map standalone custom object records with simple fields to Microsoft Project custom fields on the related task or project. Custom objects with complex relationship structures require the customer to decide between a custom field concatenation approach, a SharePoint list linked via Project Online, or accepting that the relationship data will be documented in a separate reference rather than native to the .mpp file.

Advantage user assignments on tasks map to Microsoft Project resource assignments on the same task. We resolve Advantage users by email address against the destination Microsoft Project resource sheet. Resources not already in the project resource sheet are added with their name and email. Actual work hours from Advantage assignments migrate to the assignment's Actual Work field. Note that Microsoft Project uses Max Units and Peak for assignment capacity rather than percentage allocation unless the resource has a defined calendar.

Advantage file attachments linked to tasks migrate as hyperlinks in Microsoft Project (Hyperlink field with address and description) pointing to the exported file location. We export attachments from Advantage to a structured folder hierarchy mirroring the project-task relationship, then configure hyperlinks in Microsoft Project to relative paths or a shared network location. Embedded file attachments are exported as separate files. If Advantage attachments are stored in SharePoint or a document management system, we preserve those URLs directly.

Advantage task comments map to Microsoft Project Task Notes. The comment text, author name, and timestamp migrate to the Notes field with author and date metadata embedded in the note body. If comments include @mentions or attachments, those references are preserved as text within the note or as separate hyperlinks.

Advantage workflow rules and automation logic (triggers, conditions, and actions defined in the Admin Console) do not migrate to Microsoft Project because the desktop application has no native workflow engine. We deliver a written inventory of every active Advantage workflow with its trigger object, condition logic, and resulting actions, plus a recommendation for each workflow's equivalent implementation in Microsoft Project using VBA macros, Power Automate, or manual procedure. The customer's project manager rebuilds workflows post-migration.