Quick answer: You can convert an Asana subtask to a task in a few seconds by dragging it into the main task list or adding it to a project. Asana doesn’t currently offer a built-in “Make a full task” button on subtasks, so drag-and-drop is the native method.
Two ways to convert a subtask to a task
Method 1: Drag and drop
- Open the parent task containing the subtask
- Click and drag the subtask out of the subtask panel
- Drop it into the project’s main task list
- The subtask becomes a standalone task
Method 2: Add to a project
If you want the subtask to appear in a project’s task list without fully removing it from the parent task:
- Open the subtask
- Use the project field to add it to a project
- The subtask now appears as a row in that project’s list view
- Optionally drag it to the right section or position
This makes the subtask visible in project views while keeping it nested under the parent.
Drag-and-drop promotion preserves all core task data: description, comments, attachments, assignee, and due date stay intact. Custom field values are also preserved but only visible in projects where those fields exist.
When to convert subtasks to tasks
Not every subtask needs to be converted to a full task. Here are the signals that a subtask should be restructured:
| Signal | Why it matters |
|---|---|
| Subtask needs its own subtasks | Deeper nesting becomes hard to manage and report on |
| You’ve crossed 30 subtasks | Roll-up calculations stop working at 31+ (see below) |
| Subtask needs project visibility | Subtasks don’t appear in project views by default; you can add them to a project to surface them |
| Assignment tracking gaps | Full tasks show up in workload views and reports more reliably |
The 30-subtask calculation limit
Asana’s roll-up calculations (Sum, Average, Count) stop working when a task has more than 30 subtasks. This catches teams off guard because there’s no warning. The numbers just stop updating.
If you’re restructuring subtasks because of this limitation, you have two options:
- Convert some subtasks to full tasks to reduce the count below 31
- Use a reporting tool that handles aggregation without the 30-subtask ceiling
Frustrated by Asana’s subtask limitations? BlinkMetrics tracks and aggregates data across unlimited subtasks without breaking. Try BlinkMetrics for Asana →
Frequently asked questions
No. The task keeps all its existing data: description, comments, attachments, assignee, and due date. Custom field values are preserved but only visible in projects where those fields exist.
Not natively. Asana requires converting subtasks one at a time. For bulk operations, you’d need to use the Asana API or a third-party automation tool.
Yes. The assignee and due date stay the same. Most other properties remain intact; only project-specific details like visible custom fields may change based on where you move it.
