Prepare an Asana project CSV with the right task columns

Put Task Name first and make each row one task

Asana's preparation guidance expects a clear header row and one task per row. Reorder the source to match the import mapping, and do not use a report subtotal or blank line as a task.

• A report title becomes the first task because the header is missing
• Sections, assignees, or due dates land in the wrong columns
• An export includes totals and helper columns that Asana does not need

• Select the columns required by the template →Remove export-only fields while keeping all data rows.
• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.

Map source fields to Asana task fields

Asana's importer adds tasks; it does not infer your project hierarchy from arbitrary report columns. Write a source-to-destination mapping before selecting columns.

• Keep Task Name as a populated text field
• Use the exact header spelling expected by the importer when documented
• Remove totals, blank rows, and presentation-only columns

• Select the columns required by the template →Remove export-only fields while keeping all data rows.
• Keep only rows that belong in the import →Exclude test, inactive, or incomplete records with a visible count.

Prepare the file in LocaCSV

LocaCSV does not create project dependencies or assign people. It creates a stable input for Asana's mapping step.

1. 1Diagnose the export and confirm the header row and task count
2. 2Select and reorder the columns required by the Asana template
3. 3Filter confirmed blank or subtotal rows and record exclusions
4. 4Import a small project sample and compare task names and sections

Check the project after import

• The number of task rows equals the expected source count
• Task Name is present and no report subtotal became a task
• Sections, assignees, and due dates map to the intended fields
• The output column order and excluded-row count are recorded

• Select the columns required by the template →Remove export-only fields while keeping all data rows.
• Keep only rows that belong in the import →Exclude test, inactive, or incomplete records with a visible count.
• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.

If Asana creates tasks with wrong fields

Review the header names and the project import mapping. Correct the mapping or a single column rather than regenerating unrelated task values.

• Select the columns required by the template →Remove export-only fields while keeping all data rows.
• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.
• Keep only rows that belong in the import →Exclude test, inactive, or incomplete records with a visible count.

Shape the Asana project CSV