MS Project Import Conflict Resolution Rules

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

If a task exists in Allegra but has been deleted from the MS Project project, you will be asked if 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 will be asked if you want to restore the task in Allegra.

The following fields can be modified in either Allegra or MS Project, and the changes will be synchronized when imported into Allegra:

• Planned value for work

• Remaining estimated work

• Start date

• End date (due date)

• Task dependency links

• Task title

If the work start date or end date in Allegra was changed after the last modified 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 on the last modified date only. If a dependency link has been changed in MS Project, it overwrites the Allegra link when the MS Project file was changed later than the link in Allegra. Otherwise, the Allegra link remains unchanged.

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

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

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