Migrate from Azor to Microsoft Project

Azor Projects map directly to Microsoft Project files (MPP) or Project Online projects. We preserve the project name as the Project Summary Task name, project description as the project summary task notes field, and creation date as the project Start Date. If the customer is migrating to Project Online, we create each project via the Project Web App (PWA) REST API with the project name and start date, then import task rows. For desktop MPP migrations, we use a CSV-to-MPP conversion with custom field mapping.

Azor Tasks map directly to Microsoft Project Task rows. Title maps to Task Name, description maps to Notes, assignee maps to Resource Names (or a single assigned Resource if Azor task has one assignee), due date maps to Finish, and status (To Do / In Progress / Done) maps to a custom Text1 field or Flag field since Microsoft Project does not have a native To Do/In Progress/Done status model. We preserve Azor's due dates as Finish dates; if Azor tasks have no due date we leave Finish blank and flag for manual scheduling.

Azor has no sub-task hierarchy, so every task is a top-level row in Microsoft Project. If the customer has any organizational convention for grouping tasks (e.g., phase labels in task names), we attempt to parse and indent them as summary tasks using the task name prefix. If no such convention exists, we import all tasks as flat rows and flag the absence of a WBS structure for the customer to establish in Microsoft Project after migration.

Azor exposes no dependency or predecessor data in any export format. We cannot reconstruct Finish-to-Start links from Azor's data. All migrated tasks arrive without predecessors and without successor links. We flag this gap in the pre-migration scope document and recommend the customer use Microsoft Project's predecessor auto-link feature or a dependency mapping session post-migration to establish the critical path before the project goes live.

Azor tags migrate to Microsoft Project custom fields. We map tags as comma-separated values in a Text1 custom field per task, or if Azor tags represent discrete categories (e.g., priority or phase labels), we map them to Flag fields or a Number field with a lookup table. Microsoft Project supports up to 10 custom fields per task; we use Text1 for tags and reserve remaining slots for any customer-specific attributes identified during scoping.

Azor user display names and email addresses map to Microsoft Project Resources in the Resource Sheet. Azor does not expose user roles or permission levels, so we import all Azor users as Generic Resources (type = Material) without cost rates. If the customer wants named resources with Active Directory integration, the Project Online admin provisions the resources in PWA before migration and we match by email. Resource calendars, max units, and cost rates are configured post-migration in the Resource Sheet.

Azor's To Do / In Progress / Done status values do not map to any native Microsoft Project field. Microsoft Project tracks percent complete (0-100) and task type (not started, in progress, completed) but has no equivalent status label. We map Azor status to a custom Text1 or Flag field on each task. The customer defines the flag logic during scoping: e.g., Flag1 = Yes if status = Done, or Text1 = original Azor status value.

Azor assigns each task to one user at a time. We map the assignee to a Resource Assignment on the corresponding Microsoft Project task with Units = 100%. If no assignee exists in Azor, the task arrives unassigned and we flag it for the customer's PM to allocate during resource leveling. Microsoft Project supports multiple resource assignments per task; Azor does not, so there is no N:1 merge scenario.

Azor due dates migrate directly to Microsoft Project Finish dates. We preserve ISO 8601 date format and set the Finish field on each task row. Tasks without a due date in Azor are imported with no Finish constraint and flagged for the customer to schedule manually. Microsoft Project will auto-calculate Finish based on Duration and Start date if the task is set to Auto Scheduled; if the customer uses Manual Scheduling mode, Finish dates are set directly.

Azor does not document a native custom field layer. Any customer-specific attributes stored in text fields, notes, or custom columns in Azor must be identified during scoping and manually mapped to Microsoft Project's available custom fields (up to 10 per task). We request the customer provide a field map before import identifying which Azor text fields contain structured data that belongs in a dedicated Microsoft Project custom field versus notes.