Migrate from Azor to monday Work Management

Each Azor project maps to a monday.com Board. Project name, description, and creation date migrate as Board name, description, and created_at metadata. We create Boards in the target Workspace during migration. If the Azor project has folder or group labels, we store them as a Board tag or a custom column rather than a separate organizational layer since Azor's hierarchy is flat.

Azor tasks map directly to monday.com Items within the corresponding Board. Task title becomes Item name, task description becomes the Item's Description column, and task status maps to a Status column configured in monday.com to match Azor's status values (e.g. To Do, In Progress, Done). Due dates transfer to a Date column. Tasks with no assignee are left blank or assigned to a migration service account pending customer confirmation.

Azor user display names and email addresses map to monday.com Team Members. We extract all users from Azor CSV exports and provision matching accounts in monday.com by email. Azor does not expose role or permission levels in any export format, so all migrated users receive standard member access; permission elevation is handled manually by the customer's monday.com admin post-migration.

Azor's fixed status set per project (To Do, In Progress, Done, or project-specific labels) maps to a monday.com Status column. We extract the distinct status values from each Azor project's export and configure them as labeled color-coded status options in monday.com. Non-standard or custom status values are flagged for manual review before import because Azor allows per-project status labels with no centralized taxonomy.

Due dates on Azor tasks migrate to a monday.com Date column. Dates are preserved in ISO 8601 format through the extraction and import pipeline. Tasks with no due date are migrated with a null Date column value. If the source team uses a due-date-only field without start dates, we do not create a Timeline (start-end range) column; a separate Timeline column requires customer input on start-date logic.

Azor tags migrate to monday.com Tags. We extract tags as a comma-separated string from Azor's export and split them into monday.com tag labels. Tags that do not already exist in the destination Board are created automatically during import. If the customer prefers a dedicated Labels column (dropdown or multi-select) over tags, we configure this during scoping and remap accordingly.

Azor tasks with a single assignee map to a monday.com Person column. We resolve each assignee by email against the migrated Team Member list. Tasks with no assignee are flagged in the migration report. Tasks assigned to users not found in the Team Member list are held in a reconciliation queue for the customer's admin to map manually before the final import phase.

Azor does not have a nested group structure beyond flat task lists; each project is a single flat list. We map each Azor project to a monday.com Board with a single default Group (e.g. 'Group 1'). If the source Azor data reveals informal groupings (e.g. tasks prefixed with project phase names), we create monday.com Groups from those prefixes and assign items accordingly during scoping.

Azor does not expose comments in any documented export or API format. This is a permanent data gap. We include a pre-migration checklist item requiring the customer to acknowledge comment loss and, if possible, export comments manually before the engagement begins. We cannot import comments from Azor by any automated or screen-based method.

Azor does not expose file attachments in any documented export mechanism. Uploaded files associated with tasks cannot be retrieved for migration. We flag this gap in the pre-migration scope document and recommend the customer downloads any critical attachments manually before migration begins.

Azor does not document a custom field layer. Any customer-specific attributes stored in text fields, notes, or custom columns in the Azor source must be identified during scoping and manually mapped to monday.com's 29 column types. We request a field map from the customer before import so that text attributes map to Text columns, numeric attributes to Number columns, and date attributes to Date columns rather than requiring post-migration rework.

Azor does not expose time-tracking data in any documented export format. monday.com's Time Tracking column (available on Pro plan and above) cannot be populated from Azor data. If the customer relies on time tracking, they must configure it manually in monday.com post-migration.