MS Project import conflict resolution rules

MS Project import conflict resolution rules#

When you import an MS Project plan, conflicts with existing tasks can occur. Allegra follows specific rules to resolve such conflicts.

If a task exists in Allegra but has been deleted from the MS Project project, you are asked whether you want to mark this task as deleted in Allegra as well.

If a task has been deleted in Allegra but still exists in the MS Project project, you are asked whether you want to restore the task in Allegra.

The following fields can be changed in either Allegra or MS Project, and the changes are synchronized when importing into Allegra:

  • Planned value for work

  • Remaining estimated work

  • Start date

  • End date (due date)

  • Task dependency links

  • Task title

If work, start date or end date were changed in Allegra after the last modification date of the MS Project project, you can select the desired value during the import conflict resolution process.

Conflict resolution for task dependency links is based solely on the last modification date. If a dependency link was changed in MS Project, it overwrites the Allegra link if the MS Project file was changed later than the link in Allegra. Otherwise the Allegra link remains unchanged.

The same behavior applies when links have been deleted. If a link was deleted from the MS Project file, it is also deleted in Allegra if the change to the MS Project file came later than the last change to the link in Allegra.

If there is a conflict with the task title, the Allegra title remains unchanged.

Data for the actual work is never imported from MS Project files into Allegra, since this data is typically modified by a large number of team members rather than by a project manager. The actual work is, however, exported to MS Project files so that it can be analyzed by the project administrator.