Migrate your Azor data
General-purpose project management tool with a free tier and simple task-tracking interface, designed for small teams evaluating PM software for the first time.
In its favor
Why people choose Azor
The signal that keeps Azor on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Azor offers a free plan for up to 3 users, making it one of the lowest-cost entry points for small teams evaluating project management tools for the first time, per G2 and ITQlick pricing data.
Users consistently describe Azor as easy to use, praising the straightforward interface and minimal learning curve for getting projects and tasks set up quickly.
Azor consolidates project information and task tracking in a single tool, reducing the need to coordinate across multiple spreadsheets or communication channels.
The platform is positioned as a general-purpose PM tool that can serve teams across different industries without requiring vertical-specific configuration or training.
Small teams cite the simplicity of assigning tasks and sharing project status as a key reason for choosing Azor over more complex alternatives.
The user interface is described as dated and not modern, which creates friction for teams expecting the visual polish of newer PM tools like monday.com or Asana.
Azor lacks native mobile applications, offering only a mobile browser experience, which frustrates field or remote teams that need full offline functionality on iOS or Android.
The platform has no documented API or webhook system, which blocks teams that need to automate reporting, sync with other tools, or extract data in bulk.
Scaling costs are a pain point: at 100 users the price reaches $499/month, which becomes less competitive compared to Asana's per-seat model at that team size.
The platform does not expose comments or attachments in any export format, making it difficult to preserve full project history when switching to a new tool.
Reasons to switch
Why people leave Azor
The recurring reasons buyers give for replacing Azor. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Azor fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Azor pricing overview
Azor uses a per-seat pricing model with tiered plans from free (3 users) to custom Enterprise pricing. Costs scale modestly for small teams but reach $499/month at 100 users, making per-seat competitors like Asana more cost-effective at larger headcounts.
Free
Tier 1 of 4
Free for up to 3 users
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Azor's schedule — see our quote-based pricing →
What gets migrated
Azor object support
Object-by-object support for Azor migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the top-level container in Azor. Every task belongs to a project. We migrate all projects 1:1 and preserve the project name, description, and creation date as standard fields.
Tasks
Fully supportedTasks are Azor's primary work unit. Each task carries a title, description, assignee, due date, and status. We map these directly to the destination task object, preserving the title, description, due date, and owner assignment.
Users
Fully supportedUsers are Azor's person records. We migrate user display names and email addresses directly. Role or permission levels are not exposed in Azor's data model and are not migrated.
Task Status
Mapping requiredAzor uses a fixed set of statuses (e.g. To Do, In Progress, Done) per project. We map these to the destination pipeline stage or status field but flag any non-standard statuses for manual review before import.
Task Assignments
Mapping requiredTasks are assigned to a single user at a time. We map the assignee to the destination owner field. Tasks with no assignee are flagged and left blank or assigned to a migration service account pending customer instruction.
Due Dates
Fully supportedDue dates are stored as date fields on tasks. We preserve them in ISO 8601 format and migrate them directly. Tasks with no due date are migrated as null.
Tags
Mapping requiredAzor supports tagging tasks. We extract tags as a comma-separated string or as an array, depending on the destination format. Tags that do not exist in the destination system are created as new labels.
Comments
Not in this platformAzor does not expose comments via any documented export or API. We cannot reliably migrate comments and advise customers to export them manually or accept them as lost data before migration begins.
Attachments
Not in this platformAzor does not expose file attachments via any documented export mechanism. We do not migrate attachments and flag this gap in the pre-migration scope document.
Custom Fields
Not in this platformAzor's data model does not document a custom field layer. Any customer-specific data stored in text fields, notes, or custom columns must be identified during scoping and mapped manually to the destination custom fields.
Time Tracking
Not in this platformAzor does not expose a time-tracking object or time-entry records in any documented export format. We do not migrate time data.
Project Groups or Workspaces
Mapping requiredAzor uses a simple project list hierarchy. We map each project as a top-level item and preserve any folder or group labels as a project tag or custom property.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the top-level container in Azor. Every task belongs to a project. We migrate all projects 1:1 and preserve the project name, description, and creation date as standard fields. |
| Tasks | Fully supported | Tasks are Azor's primary work unit. Each task carries a title, description, assignee, due date, and status. We map these directly to the destination task object, preserving the title, description, due date, and owner assignment. |
| Users | Fully supported | Users are Azor's person records. We migrate user display names and email addresses directly. Role or permission levels are not exposed in Azor's data model and are not migrated. |
| Task Status | Mapping required | Azor uses a fixed set of statuses (e.g. To Do, In Progress, Done) per project. We map these to the destination pipeline stage or status field but flag any non-standard statuses for manual review before import. |
| Task Assignments | Mapping required | Tasks are assigned to a single user at a time. We map the assignee to the destination owner field. Tasks with no assignee are flagged and left blank or assigned to a migration service account pending customer instruction. |
| Due Dates | Fully supported | Due dates are stored as date fields on tasks. We preserve them in ISO 8601 format and migrate them directly. Tasks with no due date are migrated as null. |
| Tags | Mapping required | Azor supports tagging tasks. We extract tags as a comma-separated string or as an array, depending on the destination format. Tags that do not exist in the destination system are created as new labels. |
| Comments | Not in this platform | Azor does not expose comments via any documented export or API. We cannot reliably migrate comments and advise customers to export them manually or accept them as lost data before migration begins. |
| Attachments | Not in this platform | Azor does not expose file attachments via any documented export mechanism. We do not migrate attachments and flag this gap in the pre-migration scope document. |
| Custom Fields | Not in this platform | Azor's data model does not document a custom field layer. Any customer-specific data stored in text fields, notes, or custom columns must be identified during scoping and mapped manually to the destination custom fields. |
| Time Tracking | Not in this platform | Azor does not expose a time-tracking object or time-entry records in any documented export format. We do not migrate time data. |
| Project Groups or Workspaces | Mapping required | Azor uses a simple project list hierarchy. We map each project as a top-level item and preserve any folder or group labels as a project tag or custom property. |
Gotchas
What to watch for in Azor migrations
Issues we've hit on past Azor migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No API means no bulk data export
No documented export format for comments or attachments
Free plan limits and per-seat pricing model
No sub-task or dependency model
Custom fields not a native feature
| Severity | Issue |
|---|---|
| High | No API means no bulk data export |
| High | No documented export format for comments or attachments |
| Medium | Free plan limits and per-seat pricing model |
| Medium | No sub-task or dependency model |
| Low | Custom fields not a native feature |
Leaving Azor?
Where Azor customers move next
5 destinations Azor can migrate to.
How a Azor migration works
Four steps, Azor-specific
Connect
None documented into Azor. Scopes limited to read-only on the data we move.
Map
We translate Azor-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Azor quirks before production.
Migrate
Full migration with Azor rate-limit handling. Rollback available throughout.
FAQ
Azor migration FAQ
Answers to the questions buyers ask most during Azor migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Azor migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Azor.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Azor setup and destination — written quote back within a business day.