Migrate from Azor to Trello

Azor Projects map 1:1 to Trello Boards. The project name becomes the board title, and the project description migrates to the board description field. We create one board per Azor project during the import phase. If the customer uses Azor project groups or folder labels, we map those as board tags or Workspace-level organization. Trello boards must be created inside a Workspace; we confirm the target Workspace during scoping.

Azor Tasks map 1:1 to Trello Cards. The task title becomes the card name, the task description migrates to the card description field, and due dates transfer directly in ISO 8601 format. Azor does not support sub-tasks, so every task in Azor becomes one card without nested hierarchy. We do not create Trello Checklist items from Azor data because Azor has no sub-task or checklist concept. Tasks with no assignee are created as unassigned cards; tasks with no due date are created without a due date field.

Azor uses a fixed set of statuses per project (e.g., To Do, In Progress, Done). We map each distinct Azor status value to a Trello List within the target board. We create the lists in order during board setup before card import begins. Any non-standard or customer-specific statuses are flagged during scoping and mapped manually to an appropriate Trello list name.

Azor user display names and email addresses map to Trello Member profiles. We match by email during migration. Trello members must exist in the target Workspace before they can be assigned to cards; we extract the full user list from Azor during scoping and confirm that each user has a Trello account or will be provisioned before card import. Role or permission levels from Azor are not exposed and cannot be migrated.

Azor tags map to Trello Labels within each board. We extract tags as a comma-separated string or array from Azor CSV exports and translate them to Trello Label names. We create labels in the target board before card import so that label assignment is valid at insert time. Labels that do not exist are created during import. Trello's free plan supports unlimited labels per board.

Azor task due dates migrate directly to Trello card due dates in ISO 8601 format. Tasks with no due date are imported without a due date field. We do not manipulate or recalculate dates during migration. Trello due dates display as date badges on cards and support due date reminders on Standard and Premium plans.

Azor tasks are assigned to a single user at a time. We map the Azor assignee to the Trello card member field. If the assignee email does not resolve to a Trello member in the target Workspace, the card is created without a member assignment and flagged for manual resolution. Multi-user assignments from the source system are not supported because Azor does not allow multiple assignees per task.

Azor does not expose comments in any documented export format. We cannot migrate comments programmatically. The pre-migration checklist requires the customer to acknowledge this data gap and, if comments are critical, to export them manually from Azor before the engagement begins. Trello card comments cannot be populated from the Azor source because the source data is inaccessible via API or CSV.

Azor does not expose file attachments in any documented export format. We do not migrate attachments. Customers who need attachment history are advised to download files from Azor manually before migration and re-upload them to the corresponding Trello cards post-migration. Trello supports up to 10MB per file on the free plan and larger limits on Standard and Premium.

Azor does not document a custom field layer. Any customer-specific attributes stored in Azor text fields or notes must be identified during scoping and manually mapped to Trello Custom Fields (available on Standard and above) or stored as card labels, checklist items, or description text. We request the customer provide a field map before import to reduce rework. Trello Custom Fields Power-Up must be enabled on the target board before migration begins.

Azor uses a simple project list hierarchy with no Workspace-level container. We map each Azor project to a Trello board within a single target Workspace or split across multiple Workspaces as directed by the customer during scoping. If the customer has more than one Azor project group that logically maps to separate Trello Workspaces, we create those Workspaces and distribute boards accordingly.

Azor does not expose a time-tracking object or time-entry records in any documented export format. We do not migrate time data. Trello does not have a native time-tracking object; teams requiring time tracking use Power-Ups like Clockify or TimeCamp.