Move your Asana projects into Fareeqy

Yes. The default turns each Asana Section into a task list because that preserves the structure your team already knows. Choose assignee on the upload screen instead and every person's tasks are gathered into a list bearing that name, with unassigned work placed in its own clearly named list. If the preview is not useful, change the grouping there and the file is parsed again without writing a project to your account.

This choice does not replace the project or remove a Task; it changes only the middle level. With Section grouping, the parser keeps membership recorded by Asana whether it appears on the Task itself or through nesting under a Section in JSON. With assignee grouping, every Task's own owner is read separately. Two Tasks that shared one Section can therefore enter different lists when different people own them.

Grouping does not alter other Asana fields. The importer reads due_at when a timed deadline exists or due_on for a date-only deadline, and keeps completed_at when the export provides it. If a Task says it is complete without carrying that time, the reader falls back to created_at before using migration time. Assignee remains an Asana reference that you match to a member in the preview, so rearranging lists cannot become a fresh guess about who owns the work.

Subtasks participate as well. The importer expands nested Subtasks recursively, even when one child contains another, then makes each an ordinary task under its parent's Section when Section is selected. Assignee grouping instead places a Subtask with its own owner, not automatically with the parent Task's owner. Its completion state and due date stay actionable rather than becoming a bullet inside another description. Compare the list counts in both previews before committing to the structure your team will use.

The importer does not recreate Asana Custom fields as new Fareeqy fields, but it does not erase their meaning. For every field that has a value, it writes the field name and displayed value as a readable list inside the task notes, after the description your team wrote. Information such as a request type or internal stage therefore remains visible without pretending that Asana's customizable field system moved over unchanged.

The parser uses the displayed value present in the export. When a field is an enum, it takes the selected enum_value name. Empty fields add no blank lines to clutter the notes. Tags remain in a separate named line, allowing a reader to distinguish a tag the team applied from a Custom field with its own name and value. The original Task description leads all of this content, so imported context cannot masquerade as text your team authored.

What does not cross is field behavior. An Asana rule that changes a Custom field, a condition that moves a Task when that value changes, or a Portfolio organized around it is not replayed in Fareeqy. The readable meaning in the JSON arrives, not the automation system around it. After migration, review the task and select a Fareeqy priority or assignee explicitly rather than having an importer turn a custom value into a decision you never requested.