---
title: "Migrate to Asana | FlitStack AI"
description: "Migrating to Asana? Import limits, the full migration checklist and every source FlitStack AI moves into Asana, with history and rollback."
url: "https://flitstack.ai/migrations/pm/asana"
---

# Migrate to Asana

Asana is a work-management platform whose import model rewards teams that pre-build projects with the right custom fields, structure subtask depth deliberately, and accept that comments, time history and attachments are second-class citizens of the CSV path.

Short answer

FlitStack AI migrates projects, tasks, and timelines into Asana from 150+ project management tools, including Trello, Notion, Jira, Slack. Every field is mapped to Asana's objects, history and associations come across, the Asana setup is configured alongside, and the whole migration stays reversible in one click.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See every source →](https://flitstack.ai/migrations/pm/asana#sources-list)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

From Any source ![](https://flitstack.ai/platforms-trim/trello.webp) ![](https://flitstack.ai/platforms-trim/notion.webp) ![](https://flitstack.ai/platforms-trim/jira.webp)

Destination Asana ![](https://flitstack.ai/platforms-trim/asana.webp)

Trello Notion Jira Slack Airtable

150+ sources mapped into Asana

## Systems we move into Asana

The project management tools teams most often move from. Each page shows what moves, the field mapping and what to watch for.

[Trello to Asana](https://flitstack.ai/migrations/pm/trello/to/asana) [![](https://flitstack.ai/platforms-trim/notion.webp) Notion to Asana](https://flitstack.ai/migrations/pm/notion/to/asana) [Jira to Asana](https://flitstack.ai/migrations/pm/jira/to/asana) [Slack to Asana](https://flitstack.ai/migrations/pm/slack/to/asana) [Airtable to Asana](https://flitstack.ai/migrations/pm/airtable/to/asana) [ClickUp to Asana](https://flitstack.ai/migrations/pm/clickup/to/asana)

## What Asana supports, and where its import tools stop

- Organizations with distributed teams cite Asana's multiple project views (List, Board, Calendar, Timeline) as the primary reason for adoption, allowing each team member to work in their preferred interface without changing the underlying data.
- The platform's 100+ native integrations with tools like Slack, Google Drive, Salesforce, and Microsoft Teams reduce context-switching and keep work synchronized across the stack.
- Small teams and non-profits value the free plan's generous limits: unlimited projects and tasks for up to 15 team members with basic views, enabling teams to validate fit before committing to a paid tier.
- Marketing and creative teams specifically praise Asana's visual project organization, reporting dashboards, and timeline views for managing cross-functional campaign workflows.

**REST only** Personal Access Token (Bearer) or OAuth 2.0

**Rate limits** 150 req/min (Free), 1,500 req/min (Starter through Enterprise+)

| Object            | Support | Note                                                                                                                                                                                                                                                                                                                                                                            |
| ----------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Projects          | full    | Projects are the primary container object in Asana. We export all projects including their settings, default view, color, and archived status. Projects map directly to Projects in most destination platforms and are imported with all child Tasks intact.                                                                                                                    |
| Tasks             | full    | Tasks are the atomic work unit in Asana. We preserve all standard fields: name, notes/description, start date, due date, assignee, liked (hearts), and completion status. Completed tasks retain their completed\_at timestamp at the destination.                                                                                                                              |
| Subtasks          | full    | Subtasks exist as a separate resource linked to their parent task. We recursively export the subtask hierarchy and reconstruct the parent-child relationship at the destination. Deeply nested subtask chains are handled with recursive depth tracking to avoid API pagination overflow.                                                                                       |
| Custom Fields     | mapped  | Asana supports custom fields of types: Text, Number, Date, Enum (dropdown), Formula, and Rollup. We map each to the destination's equivalent field type. Enum options with custom colors are preserved as option labels. If the destination lacks the equivalent type, we fall back to Text and flag the mapping for review.                                                    |
| Sections          | full    | Sections are row-level groupings within a project (distinct from rows or columns). We export section names and task ordering within each section. When the destination uses a kanban-style board, sections map to Swimlanes or status columns.                                                                                                                                  |
| Portfolios        | mapped  | Portfolios aggregate multiple projects for executive dashboards. Only available on Starter and above. We export portfolio metadata and the list of contained project GIDs. Since Portfolios are an organizational view rather than a data object, we map them to the destination's equivalent project grouping feature or flag them as requiring manual recreation.             |
| Goals             | mapped  | Goals (OKRs) are available on the Advanced tier and link to Projects, Portfolios, or standalone. We export goal titles, timeframes, owners, and progress metrics. Goals do not have a universal equivalent in most PM tools, so we map them to the destination's native goal feature or to linked Tasks with a Goals label.                                                     |
| Dependencies      | full    | Task dependencies in Asana use GID references and a dependency\_type field (predecessor/successor). We preserve the dependency graph and reconstruct it at the destination using the target platform's native dependency mechanism. Circular dependency detection is run before import to prevent infinite loops.                                                               |
| Attachments       | mapped  | Attachments include both files uploaded directly to Asana and links to external tools (Google Drive, Dropbox, Box). We resolve direct uploads by downloading and re-uploading to the destination's file storage. External links are preserved as URL fields. Files attached via third-party integrations that require OAuth re-authorization are flagged for manual re-linkage. |
| Comments          | full    | Comments are stored as a Stories resource linked to tasks. We export comment text, author, and created\_at timestamp. HTML formatting in comments is sanitized to plain text or markdown depending on destination support.                                                                                                                                                      |
| Tags              | full    | Tags are flat labels applied to tasks across a workspace. We export tag names and colors and map them to Labels or Tags at the destination. Tags applied to multiple tasks are handled as a bulk assignment operation.                                                                                                                                                          |
| Views             | mapped  | Asana offers List, Board, Calendar, Timeline (Gantt), and Workload views. We export the view configuration for each project including column order, grouping fields, and sort order. Views are reconstructed using the destination's equivalent view builder; Gantt-specific configurations map to Timeline or dependency views.                                                |
| Teams             | full    | Teams are organizational units within an Asana workspace that group members and projects. We export team membership and the list of projects per team. Members are mapped to the destination's equivalent team or group structure.                                                                                                                                              |
| Users/Members     | mapped  | User profiles include name, email, profile photo URL, and role. We export all active and inactive users. At the destination, users are matched by email for re-invite or mapped to a generic 'Asana User' placeholder if the destination does not support the same user identity model.                                                                                         |
| Automations/Rules | none    | Automation rules (Triggers and Actions) execute within Asana's native rule engine and have no standalone export representation. Custom rules built in third-party tools like Flowsana are also non-portable. We document which automations exist so customers can manually recreate them post-migration.                                                                        |

## The Asana migration guide

## Why teams migrate to Asana

*The four shapes an Asana migration takes, and what makes the platform easier — or harder — than the category average.*

Asana, Inc. was founded in 2008 by Dustin Moskovitz and Justin Rosenstein, launched commercially in April 2012, and is headquartered in San Francisco[1](https://flitstack.ai/migrations/pm/asana#source-1). The flagship Asana service is a web and mobile work-management platform that helps teams organise, track and manage their work across projects, portfolios and goals.

The typical Asana customer is a cross-functional team — 25 to 5,000 users — that wants a single tool for project plans, intake forms, recurring operational work and OKR-style goal tracking, without standing up a dedicated Jira admin. Compared with Monday, Asana positions on a more opinionated data model (Workspace/Team/Project/Section/Task/Subtask) and stronger Portfolio rollup; compared with Jira, on a faster ramp for non-engineering teams.

Migrations to Asana fall into four shapes. First, consolidation: replacing Trello + spreadsheets + an intake tool with Asana's Projects + Forms + Rules combination. Second, Monday or ClickUp exits, driven by teams that want a more structured workflow story and tighter portfolio rollup[127](https://flitstack.ai/migrations/pm/asana#source-127).

Third, legacy replacements — Wrike, Smartsheet, Teamwork, MS Project — where the source schema is loose and the project is a re-architecture. Fourth, M\&A consolidation, where an acquired business runs a different PM tool. A Trello-to-Asana move has clean object parity but loses card automations; a Monday-to-Asana move flattens board structure into Projects + Sections + custom fields.

What makes migrating to Asana easier than the category average is the CSV Importer itself — it accepts CSV exported from Excel, Smartsheet, Wrike, Monday, Airtable, Trello, ClickUp and Google Sheets, and preserves task name, description, assignee, due dates, start dates, dependencies, followers and custom fields in a single pass[2](https://flitstack.ai/migrations/pm/asana#source-2) [4](https://flitstack.ai/migrations/pm/asana#source-4).

What makes it harder than the average is that comments and historical activity do not import via CSV, attachments must be re-uploaded or relinked individually, completion state on imported rows is silently stripped to incomplete, and `created_at` cannot be overridden — every imported task is stamped with the import date[54](https://flitstack.ai/migrations/pm/asana#source-54) [99](https://flitstack.ai/migrations/pm/asana#source-99) [161](https://flitstack.ai/migrations/pm/asana#source-161).

Rules, Bundles, Forms and inbox notifications do not move across either — they are rebuilt from documentation. Teams that scope for that work up front finish on time; teams that assume CSV parity do not.

> CSV gets you tasks, names, owners and dates. Everything else — comments, history, completion state, attachments — is a second project.

## The Asana data model you need to map into

*Workspaces, Projects, Tasks, custom fields, multi-homing — the destination schema decoded.*

Asana's object model is small but layered. A top-level Workspace or Organization contains Teams, which contain Projects, which contain Sections and Tasks, which contain Subtasks[63](https://flitstack.ai/migrations/pm/asana#source-63). Tasks are the basic unit of action — they have an assignee, a name, notes (description), followers, likes and comments, and they inherit custom fields from their parent project[63](https://flitstack.ai/migrations/pm/asana#source-63).

Before you can map a field on the source side, you need to know exactly which destination object the row belongs on, what properties it requires, and which value will serve as your match key. The table below summarises the objects you will touch in a typical Asana migration.

| Object                    | What it stores                                                                                                 | Required                                                         | Tier                                                                                         |
| ------------------------- | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| Workspace / Organization  | Top-level container — Workspace for ad-hoc groups, Organization tied to an email domain                        | Name; Organization additionally requires a verified email domain | All tiers; Organization features expand on paid plans                                        |
| Teams                     | Sub-container within an Organization for grouping projects                                                     | Name; visibility setting (Membership-only, Public, Hidden)       | Organization-only (not available in standalone Workspaces)                                   |
| Projects                  | A collection of tasks for a specific outcome (campaign, sprint, launch)                                        | Name, team (in Org), privacy setting                             | All tiers; per-project custom field limits scale with plan                                   |
| Sections                  | Logical groupings of tasks within a project (often used as workflow status)                                    | Name                                                             | All tiers                                                                                    |
| Tasks                     | The unit of work — assignee, name, notes, followers, due/start dates, custom fields                            | Name; everything else is optional                                | All tiers                                                                                    |
| Subtasks (up to 5 levels) | Tasks nested under a parent task — maximum 5 levels deep                                                       | Name; parent task ID                                             | All tiers[37](https://flitstack.ai/migrations/pm/asana#source-37)                            |
| Custom Fields             | Typed metadata attached to tasks (text, number, single-select, multi-select, date, formula, ID, time tracking) | Name, type; created at workspace, project or portfolio level     | Starter and above (not on free plan)[81](https://flitstack.ai/migrations/pm/asana#source-81) |
| Portfolios                | Cross-project rollups of status, owner, dates and custom-field rollups                                         | Name, owner                                                      | Advanced and above                                                                           |
| Goals                     | OKR-style targets connected to projects and portfolios                                                         | Name, owner, time period, metric                                 | Advanced and above                                                                           |

Asana does not expose a true external-ID / upsert key on tasks. The platform identifier is the `gid` (a global ID surfaced in the URL as `/0/<project_gid>/<task_gid>`). The CSV Importer always creates new tasks — there is no native upsert; re-running a CSV against an existing project produces duplicates[54](https://flitstack.ai/migrations/pm/asana#source-54) [157](https://flitstack.ai/migrations/pm/asana#source-157).

Teams that need re-runnability typically introduce a custom ID-type field (unique readable IDs per task) plus a separate text External ID field for the source system's primary key, and handle upsert logic externally. The ID custom field is the closest Asana feature to a stable, queryable record key[38](https://flitstack.ai/migrations/pm/asana#source-38).

Custom property types determine validation and storage; the catalogue below covers what you can model and the limits you need to plan around.

| Field type                   | Limit                                                                                                                                              | Notes                                                                                                                       |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Single-select (drop-down)    | 500 options per field[38](https://flitstack.ai/migrations/pm/asana#source-38) [73](https://flitstack.ai/migrations/pm/asana#source-73)             | Case-sensitive matching on import; a new value creates a new option silently                                                |
| Multi-select                 | 500 options; multiple values per task                                                                                                              | Comma-separated on CSV import; ordering not preserved                                                                       |
| Text                         | Plain string; no enforced max in CSV path                                                                                                          | Rich text in task notes uses Asana-specific markdown subset                                                                 |
| Number / Percent / Currency  | Decimal places configurable                                                                                                                        | Strip currency symbols and thousands separators before import                                                               |
| Date                         | Date-only, separate from task due date                                                                                                             | Asana prefers mm/dd/yyyy on CSV; dd/mm/yyyy frequently mis-parses[124](https://flitstack.ai/migrations/pm/asana#source-124) |
| People                       | Single user reference                                                                                                                              | Adds user as collaborator automatically                                                                                     |
| Formula                      | Number-type output only on the project; UTC timestamps in date inputs[76](https://flitstack.ai/migrations/pm/asana#source-76)                      | Does not import — rebuild on-platform after data lands                                                                      |
| ID (unique readable IDs)     | Auto-generated per task                                                                                                                            | Recommended for tasks that need a stable handle[38](https://flitstack.ai/migrations/pm/asana#source-38)                     |
| Time tracking / Timer        | Estimated time + actual time                                                                                                                       | Source system time entries cannot be imported via CSV — see §5                                                              |
| Per-project custom field cap | 150 fields per project (Starter+)[38](https://flitstack.ai/migrations/pm/asana#source-38) [79](https://flitstack.ai/migrations/pm/asana#source-79) | Raised from 30 in 2023; per-task cap is 60 via multi-homing[38](https://flitstack.ai/migrations/pm/asana#source-38)         |

Relationships in Asana are modelled differently from a relational CRM. A task can be multi-homed — present in multiple projects simultaneously — which is how the platform expresses many-to-many[38](https://flitstack.ai/migrations/pm/asana#source-38). Subtasks belong to exactly one parent task and inherit nothing from it by default (they do not auto-populate custom fields or section). Dependencies are blocking / blocked-by relationships between tasks, configurable on Advanced+ plans.

**5 levels** Maximum subtask depth Asana caps subtasks-of-subtasks at five levels deep. A WBS exported from MS Project that nests six or more levels has to be flattened before import or the deepest rows are silently rejected.

There is no cascade-delete, no master-detail relationship, and no foreign-key constraints — deleting a parent task orphans its subtasks, and removing a project from a multi-homed task leaves it alive elsewhere. Reproduce stricter cascade semantics via Rules or import scripts if the source relied on them.

## Pre-migration prep — the work before you touch Asana

*What must be true on the source, the destination, and across the team before the first row hits the CSV Importer.*

The single best predictor of a clean Asana migration is how much work you do on the source side before the first CSV is uploaded. The CSV Importer is forgiving on file format but unforgiving on structure: wrong-parent subtasks, wrong-locale dates and mismatched assignee emails all silently land but produce broken tasks that take longer to repair than to re-import.

> Always finish an Asana migration in one sitting if you can — context loss between sessions is the single biggest source of mistakes.
>
> Bastien Siebman, Asana Forum Leader[129](https://flitstack.ai/migrations/pm/asana#source-129)

Treat the source export as raw material to be shaped to Asana's expected formats — dates in `mm/dd/yyyy`, assignees resolved to verified emails already in the destination workspace, drop-down values matched case-exactly to the destination custom field, and subtask parents resolved either by row position or via an explicit Parent Task column.

### Source-side prep

- Audit and de-duplicate tasks in the source — Asana's CSV importer does not detect duplicates on re-import and will happily create a second copy of every row[54](https://flitstack.ai/migrations/pm/asana#source-54), so any cleanup has to happen on the source side or in the staging spreadsheet.
- Resolve assignees to verified email addresses that already exist in the destination Asana org. The assignee column is matched by exact email; mismatches result in unassigned tasks with no error, which then break ownership-based filters and notifications.
- Normalise dates to `mm/dd/yyyy` in the CSV — Asana parses U.S. format reliably and frequently misreads `dd/mm/yyyy` files, producing off-by-month errors that look correct until someone notices a January task due in April[124](https://flitstack.ai/migrations/pm/asana#source-124).
- Convert drop-down values to the exact case used in the destination project's custom field. Case-only differences create new options silently — "option" and "Option" become two values rather than collapsing[157](https://flitstack.ai/migrations/pm/asana#source-157).
- Decide subtask strategy upfront — either put subtasks immediately below their parent row and let Asana infer hierarchy, or carry an explicit Parent Task column with the parent's exact name[21](https://flitstack.ai/migrations/pm/asana#source-21). Mixing strategies in one file produces orphan subtasks.

### Destination-side prep

- Request a sandbox from Settings → Admin Console → Sandboxes — available only on Enterprise+[53](https://flitstack.ai/migrations/pm/asana#source-53). A sandbox is a separate, empty space where you can dry-run imports, train users and validate rules before touching production. Each Enterprise+ org gets one or more sandbox slots.
- Provision users first via Okta, Entra ID or Google Workspace single sign-on (Enterprise+) or via the CSV user import at the admin console on Advanced+[96](https://flitstack.ai/migrations/pm/asana#source-96). The assignee column on a task import only resolves if the user already exists.
- Create destination projects, sections and custom fields before importing tasks. The CSV Importer can build a new project from a file, but if you want tasks to land in an existing project with a specific structure, the project, sections and field library entries have to exist first.
- Add the field library entries you will need — drop-down options, ID fields, formula fields. Adding fields mid-import creates per-project copies that don't roll up into Portfolios.
- Define dependencies as a column that references parent task names if you need blocking/blocked-by relationships preserved during import[124](https://flitstack.ai/migrations/pm/asana#source-124). The advanced CSV options support a Dependents column that resolves by exact name match.

### People prep

Cutover only works if humans cooperate. Lock down a source freeze window — 24 to 48 hours — and communicate it to every team that touches the source tool. Train project leads on Asana's Projects + Sections + Custom Fields model before go-live, especially if the source was board-first. A simple Trello move under 1,000 tasks runs one to two days; a complex multi-team migration with subtasks, dependencies, Forms and Rules rebuilds runs two to four weeks of elapsed time.

## Import mechanisms: CSV Importer and Smart Import

*Two paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at scale.*

Asana exposes two main load paths and the right one depends on dataset size and source format. The CSV Importer covers most one-shot migrations under \~20,000 tasks. Smart Import (AI-assisted) handles unstructured files like PDFs and presentations. Third-party migration tools cover the shapes CSV cannot reach, including Workspace-to-Workspace splits with comments and attachments preserved.

### CSV Importer

The native importer lives behind the + button in the top bar (Create new project → Import → CSV) or via any existing project's three-dot menu → Import → CSV[4](https://flitstack.ai/migrations/pm/asana#source-4) [16](https://flitstack.ai/migrations/pm/asana#source-16). It accepts a single CSV file mapped to a new or existing project, parses the first row as headers, and lets you confirm column mapping before commit. Supported columns: Task Name, Description, Assignee (email), Due Date, Start Date, Section/Column, Dependents, Followers, and any number of Custom Field columns[4](https://flitstack.ai/migrations/pm/asana#source-4).

Limits are practical rather than published: there is no documented hard row cap, but performance degrades above \~10,000 rows per file, and imports above \~20,000 rows often time out[37](https://flitstack.ai/migrations/pm/asana#source-37). Subtask depth caps at 5 levels[37](https://flitstack.ai/migrations/pm/asana#source-37), drop-down fields cap at 500 options[38](https://flitstack.ai/migrations/pm/asana#source-38), and attachments are not supported in CSV at all. The right call: CSV for one-shot loads under 20,000 tasks on a single project, especially when the source already exports clean CSV (Trello, Monday, Wrike, ClickUp).

### Smart Import (AI)

Smart Import accepts CSV, PDF, DOCX, XLSX, PPTX, TXT, JPEG and PNG, and uses Asana AI to generate a project structure (sections, tasks, custom fields) from the content[18](https://flitstack.ai/migrations/pm/asana#source-18). It is the right tool when the source is not already structured CSV — a plan in a Word doc, a Gantt screenshot, a meeting agenda. It is the wrong tool when you have clean columnar data: AI inference adds variability that direct CSV mapping avoids.

### Third-party migration tools

Tools sit between the source and Asana for the shapes CSV cannot reach. Asana's own migration service copies data between Asana domains for free but does not migrate paid plan, admin roles, or deleted objects[108](https://flitstack.ai/migrations/pm/asana#source-108) [115](https://flitstack.ai/migrations/pm/asana#source-115). Altosio ($14.99+ per project) covers Trello, Monday, Wrike, Planner, ClickUp and Asana-to-Asana with comments and attachments preserved[127](https://flitstack.ai/migrations/pm/asana#source-127). Relokia runs a managed CSV-bridged migration. Airbyte, Fivetran, Stitch and Matillion are reverse-ETL tools for ongoing sync.

Under 5,000 tasks on a clean CSV → CSV Importer. 5,000–20,000 → CSV in batches, one project at a time. Over 20,000, or any need for comments / attachments / dependencies-across-projects → a third-party tool like Altosio or Relokia.

## Mapping your data into Asana

*The longest section — because field mapping is where almost every PM migration that fails actually breaks.*

Mapping is where every PM migration earns its scars. The decisions in your mapping spreadsheet determine whether Portfolio rollups work on day two, whether Rules fire correctly on day five, and whether project leads trust the data on day thirty. Work object by object: Workspace/Organization first, then Teams, then Projects with sections and custom fields pre-built, then Tasks with subtasks, then dependencies, then comments and attachments as separate jobs.

### Project hierarchy: Workspace → Team → Project → Section → Task → Subtask

Asana's hierarchy is rigid in a way that catches teams from board-style tools. Subtasks max out at 5 levels[37](https://flitstack.ai/migrations/pm/asana#source-37); a WBS from MS Project nesting six or more levels has to be collapsed before import. Sections are not workflow status — they are visual groupings within a project. If your source used a Status column, the cleanest mapping is either (a) Sections (good for Kanban) or (b) a single-select custom field called Status (good for cross-project rollup via Portfolios).

Decide upfront — mixing patterns across projects makes Portfolio rollups inconsistent. The custom-field approach is generally the better default for multi-project organisations because Status values then roll up into Portfolio columns and Goals.

| Source                    | Destination                                | Note                                                                                                                     |
| ------------------------- | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| Task / Card / Issue title | Task Name                                  | Required; only mandatory column in the CSV importer                                                                      |
| Description / Body        | Notes (task description)                   | Plain text or Asana markdown subset; HTML stripped on CSV path[149](https://flitstack.ai/migrations/pm/asana#source-149) |
| Assignee / Owner          | Assignee (email)                           | Matched on exact email — user must already exist in the org                                                              |
| Due date                  | Due Date                                   | mm/dd/yyyy preferred; dd/mm/yyyy frequently mis-parses[124](https://flitstack.ai/migrations/pm/asana#source-124)         |
| Start date                | Start Date                                 | Distinct field from due date; both can be set independently                                                              |
| Status / Stage / Column   | Section OR custom single-select            | Pick one pattern org-wide — Section for board view, custom field for Portfolio rollup                                    |
| Priority / Severity       | Custom single-select (Low/Med/High/Urgent) | Create at workspace level so it rolls up across projects                                                                 |
| Tags / Labels             | Tags OR multi-select custom field          | Tags are workspace-level; multi-select is per-project — prefer tags for cross-project search                             |
| Source system primary key | Custom text field (External ID) + ID field | There is no native external ID — store source key in a text field for re-runnable upsert                                 |

### Task dependencies (blocking / blocked-by)

Dependencies in Asana are blocking / blocked-by relationships between tasks within the same project and require Advanced+ for full functionality[122](https://flitstack.ai/migrations/pm/asana#source-122). The CSV Importer supports a Dependents column that resolves by exact task name — duplicate names break the resolution silently and produce no error[124](https://flitstack.ai/migrations/pm/asana#source-124). A common pattern: keep dependencies inside a single project for the import, then split into multiple projects via multi-home afterwards. Cross-project dependency-shifting is only available in Timeline view[122](https://flitstack.ai/migrations/pm/asana#source-122).

If the source is MS Project or Smartsheet with finish-to-start, start-to-start and finish-to-finish dependencies, expect to collapse to Asana's simpler blocking/blocked-by model.

### Time tracking history

Asana ships a built-in Time tracking custom field for Estimated and Actual Time per task[38](https://flitstack.ai/migrations/pm/asana#source-38). Historical entries from Harvest, Toggl or Clockify do not import via CSV — the field accepts a current value, not a back-dated entry stream. Asana has a dedicated path from Everhour that copies the most recent estimated and actual values onto matching tasks[126](https://flitstack.ai/migrations/pm/asana#source-126). For other sources, summarise time per task, populate Actual Time with the rolled-up total, and archive per-entry detail.

If forensic per-entry detail matters for billable reporting or audit, keep the source archive accessible — Asana holds only summaries.

### Comments, @-mentions and reactions

Comments are the single biggest gap in the CSV path: CSV export does not include comments, and CSV import cannot create them[54](https://flitstack.ai/migrations/pm/asana#source-54). Anything preserved has to be recreated through a third-party migration tool that supports comment carryover, or accepted as a known loss.

Rich-text formatting in source comments survives only when written using Asana's markdown subset — the notes field supports `bold`, `*italic*`, lists, links, blockquotes[149](https://flitstack.ai/migrations/pm/asana#source-149). Confluence-style macros, embedded tables and team mentions degrade to plain text. Plan a transform step that strips HTML to Asana markdown before any comment-replay tool runs, or accept the degrade.

### Custom workflow status migration

Asana does not have a first-class Status concept on tasks — there is `completed: true|false`, and that's it[94](https://flitstack.ai/migrations/pm/asana#source-94). Source platforms with rich status models (Jira's workflow states, Monday's Status column, Trello's lists) need to land on either a Section or a single-select custom field, as outlined above.

Critically: the CSV Importer cannot create completed tasks — every imported task lands as incomplete regardless of source state[94](https://flitstack.ai/migrations/pm/asana#source-94) [161](https://flitstack.ai/migrations/pm/asana#source-161). The documented workaround: add a Status single-select with a Complete option, create a Rule that when status = Complete, mark task complete and clear status, then run the rule across imported tasks. This is the only reliable round-trip for completion state via CSV.

### Recurring tasks

Recurring task schedules — daily, weekly, monthly, yearly, on completion — are an Asana-managed property and the CSV Importer does not support a Recurrence column. Recurring tasks imported via CSV land as one-shot tasks. The mitigation: import as regular tasks, then configure recurrence manually post-import. For hundreds of recurring templates, a third-party migration tool that supports recurrence is the only practical option.

### Attachments: Asana-hosted vs linked from Drive / Box / Dropbox

Attachments do not import via CSV at all. Asana hosts files up to 100 MB per file uploaded from a computer; larger files must be attached as Dropbox, Google Drive, OneDrive/SharePoint or Box links[36](https://flitstack.ai/migrations/pm/asana#source-36) [130](https://flitstack.ai/migrations/pm/asana#source-130). There is no documented hard storage cap on the number of files per workspace[36](https://flitstack.ai/migrations/pm/asana#source-36), but performance degrades on tasks with very many attachments and forum threads recommend not exceeding a couple of dozen files per task.

For large estates (hundreds of GB), the pattern most teams adopt: keep originals in Drive, S3 or Box, store a deep link in a URL-type custom field, and inline-upload only the small subset that needs to live on the Asana timeline. Third-party migration tools handle the bulk file upload where inline hosting matters.

### Audit trail, ownership and original timestamps

Standard `created_at`, `modified_at`, `completed_at` and `created_by` are Asana-managed system fields — they cannot be overwritten on import via CSV[99](https://flitstack.ai/migrations/pm/asana#source-99). Every imported task is stamped with the import date and the importing user as creator. Teams discover this on day two when filtered reports of tasks created last month return nothing or everything from import day.

The pattern: create two custom fields per project, Legacy Created Date (date) and Legacy Created By (text or people), populated from the source export. All historical-period reporting runs against the legacy fields. Asana's audit log is available only on Enterprise+ or Enterprise + Compliance Management add-on, with events retained 90 days[93](https://flitstack.ai/migrations/pm/asana#source-93). Lower tiers have no granular per-property change history.

### Rules, Bundles, Forms, Approvals — the rebuild list

Asana's no-code automation runs on Rules (per-project), Bundles (reusable rule + field packages), Forms (intake), and Approvals. None of these import — they are rebuilt from documentation post-cutover, ideally in a sandbox first. A typical mid-market migration carries 20 to 80 source automations that map to a similar count of Rules; the rebuild runs days, not hours.

Lead-scoring-style logic from CRM-adjacent PM use cases similarly does not import. Recreate as Formula custom fields (number-output) on the destination project.

## The pitfalls that derail Asana migrations

*Eight specific failure modes — ranked by impact, each tied to the exact Asana mechanism that breaks.*

**high Imported tasks land as incomplete, regardless of source state**

The CSV Importer cannot create completed tasks — every row lands as incomplete, even when the source CSV carries a completion flag[94](https://flitstack.ai/migrations/pm/asana#source-94) [161](https://flitstack.ai/migrations/pm/asana#source-161). Teams discover this when project archives that were 80% done in the source appear as full backlogs in Asana. The workaround is a status custom field plus a destination-project Rule that maps status = Complete to mark-complete after import. Validate completion state on a 100-row dry run before scaling.

**high Comments and historical activity do not import via CSV**

Asana's CSV path carries task name, description, dates, assignee, custom fields and dependencies — but no comments, no @-mentions, no story timeline, no reactions[54](https://flitstack.ai/migrations/pm/asana#source-54). Teams that scope CSV and discover this mid-project either pivot to a third-party migration tool that supports comment carryover or accept the loss. Decide upfront whether comment preservation is in scope, because it determines the import mechanism, not the data shape.

**high created\_at and completed\_at cannot be overridden**

Standard `created_at`, `modified_at`, `completed_at` and `created_by` are Asana-managed and ignored if you supply them. Every imported task is stamped to the import date, and reports filtered on tasks created last month return nothing. The mitigation is to create Legacy Created Date, Legacy Completed Date and Legacy Created By custom fields on every project, populate them from source data, and rewrite all historical reports to use those legacy fields[99](https://flitstack.ai/migrations/pm/asana#source-99).

**high Drop-down options are case-sensitive and silently fork**

Single-select custom fields treat `option` and `Option` as distinct values. A CSV import that contains case variants of the same intended value creates a new option in the destination drop-down for each variant, with no error message[157](https://flitstack.ai/migrations/pm/asana#source-157). Drop-down fields cap at 500 options total[38](https://flitstack.ai/migrations/pm/asana#source-38) [73](https://flitstack.ai/migrations/pm/asana#source-73) — fork enough times and you bump the ceiling. Always normalise drop-down values in the staging spreadsheet to match the destination field's existing options exactly, character-for-character.

**high Date parsing flips months when the file is dd/mm/yyyy**

Asana prefers `mm/dd/yyyy` in the CSV path and frequently mis-parses `dd/mm/yyyy` files — a task due on 04/02/2026 (4 February) can land as 2 April[124](https://flitstack.ai/migrations/pm/asana#source-124). The error surfaces only on inspection, not at import time, so teams notice three weeks in when a January milestone shows up in April. Convert all date columns to ISO `yyyy-mm-dd` or U.S. `mm/dd/yyyy` before upload, and spot-check 30 random rows for date drift after the first import.

**medium Subtask depth caps at 5 levels — deeper rows silently drop**

Asana enforces a hard limit of 5 subtask levels[37](https://flitstack.ai/migrations/pm/asana#source-37). A WBS exported from MS Project that nests 6 or more levels deep loses the deepest rows on import with no clear error — they either land as orphan tasks at the top level or fail to land at all. Audit the source for depth before import (`MAX(depth)` in the staging spreadsheet) and flatten anything past level 5 into a Section + multi-home pattern.

**medium EU data residency available only on Enterprise+**

Asana operates a Frankfurt data centre for EU customers and a US centre for everyone else, but EU residency is purchasable only on Enterprise and Enterprise+ plans[138](https://flitstack.ai/migrations/pm/asana#source-138). New accounts choose at provisioning; existing customers can request a one-time region migration via the Asana team[115](https://flitstack.ai/migrations/pm/asana#source-115). If you are migrating into an EU-regulated business on a US-region account, plan the region migration before the data migration, or you will copy the data twice.

**low Attachments are an entirely separate post-import job**

The CSV path does not carry attachments at all, and Asana caps uploads from a computer at 100 MB per file[36](https://flitstack.ai/migrations/pm/asana#source-36) [130](https://flitstack.ai/migrations/pm/asana#source-130). Teams that assume the importer brings everything finish the task import and discover thousands of files still in the source. Plan an explicit attachment migration via a third-party tool or via re-linking from Drive/Box/Dropbox — the latter is faster but creates an external dependency for every link, which breaks if the source storage account is decommissioned.

## Validation and cutover

*What to verify after the import job, in what order — and how to fail safely when something is wrong.*

Validation is the bridge between the import finishing and users being allowed in. The three-stage rhythm that works on Asana: a test load of 10 percent of records with stakeholder spot-checks, the full load with real-time monitoring of task counts and assignee distribution, and a 30-day post-migration data-quality audit. The most reliable signal is having project leads verify their own projects — they know what right looks like better than any reconciliation script.

Build a reconciliation spreadsheet that compares source and destination on each of these counts. Anything outside a 1 percent variance gets investigated before users get login access.

- Total tasks imported vs source — minus deliberately excluded rows (archived projects, deleted tasks, role-based or system-generated entries).
- Total subtasks per parent task vs source — and a depth check (`MAX(depth) <= 5`) to confirm the cap did not silently truncate.
- Tasks per section per project vs source — a non-trivial count variance usually signals a Status mapping error or a hierarchy issue.
- Assignee distribution — `GROUP BY assignee_email` and confirm no tasks landed unassigned that should not have. Unassigned tasks are typically email-mismatch casualties.
- Custom field coverage — for each project, count tasks with a value in each custom field and compare to expected. Drop-down case-fork errors show up here as inflated option counts.
- Dependency integrity — for projects with dependencies, count blocking and blocked-by edges and compare to source. Missing edges usually indicate a duplicate-name resolution failure.
- Completed-task count — the high-frequency failure mode. Run before AND after the Complete Rule fires, to confirm the Rule actually closed the imported tasks.
- Legacy date field coverage — confirm every task has a populated Legacy Created Date; gaps reveal rows where the source field was empty or the column mapping dropped.

On top of reconciliation, run a manual spot-check: pick 30 random tasks across projects and verify each field against the source UI. Pick five high-stakes projects and trace the full tree — sections, tasks, subtasks, dependencies, custom fields, attachments. If a non-trivial discrepancy shows up in three or more of the 30, halt, fix the root cause, and re-import the affected rows.

Asana has no native bulk-rollback button[113](https://flitstack.ai/migrations/pm/asana#source-113). Once tasks are imported, undoing them is per-task delete (lands in the trash for 30 days on Enterprise[137](https://flitstack.ai/migrations/pm/asana#source-137)) or per-project archive. For larger reversals, the only practical mechanism is to delete the affected project entirely and re-import. This is why every import should be staged: load to a freshly-created project first, validate, then either keep it or delete-and-redo, rather than importing into a production project.

The real rollback strategy: export every source object to S3 before import, stamp every imported task with an Import Batch ID custom field, and if catastrophe strikes, filter on that batch ID, archive the project, and re-import from the cleaned source.

Cutover sequencing: (1) source goes read-only and the team is notified; (2) final delta export captures changes during the test-import window; (3) delta imports into staging projects; (4) reconciliation runs; (5) staging projects move to production teams; (6) users get login and a 48-hour hyper-care window with the migration lead on call; (7) source decommission is scheduled 30 to 90 days out. Asana's in-house service warns that paid plan, admin roles, and deleted objects do not carry over[115](https://flitstack.ai/migrations/pm/asana#source-115).

## Migration partners and tools

*Asana Solutions Partners, specialist migration vendors, ETL tools — what each is good for and how to choose.*

Asana's Solutions Partner Program lists certified consulting partners worldwide[103](https://flitstack.ai/migrations/pm/asana#source-103). Partners with explicit migration practices — particularly Trello-to-Asana, Monday-to-Asana, Wrike-to-Asana and ClickUp-to-Asana — tend to ship cleaner than generalist implementation shops. Examples from the partner directory include i.DO (France/global), Priceless Consulting, PMexperts (Poland), and Taco Technologies (Australia). Each offers fixed-scope migration packages alongside ongoing managed services.

Asana also runs an in-house migration team that copies data between Asana domains for free[108](https://flitstack.ai/migrations/pm/asana#source-108) [115](https://flitstack.ai/migrations/pm/asana#source-115). It has documented caveats: it does not migrate paid plan, admin roles, or deleted objects. Plan to re-provision those after the data copy completes.

On the specialist side, Altosio ($14.99+ per project) covers Trello, Monday, Wrike, Planner, ClickUp and Asana-to-Asana with subtasks, comments and attachments preserved[127](https://flitstack.ai/migrations/pm/asana#source-127). Relokia runs a Demo + Full Migration model with custom-field mapping and agent-resolution that handles email-mismatch cases. Workino, Omtera and ditto.kothar.net cover related niches, particularly for Asana-to-Asana Workspace splits.

On the ETL and iPaaS side, Airbyte, Fivetran, Stitch and Matillion all have Asana connectors. Their role in a one-time migration is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that converts drop-down values and resolves assignee emails, and the ongoing-sync layer that takes over once the one-time migration is complete. Workato is a common pick where the migration is bundled with a Rules rebuild.

Managed-migration cost ranges vary widely. A clean Trello-to-Asana move under 5,000 tasks with no historical comments often lands in the £1,500–£5,000 / $2,000–$7,000 range. A multi-team migration from Monday or Wrike with attachments, comments, dependencies and Rules rebuilds typically runs $15,000–$80,000, driven by task count, custom-field complexity, attachment volume and the number of source automations that need rebuilding rather than re-pointing.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Asana migrations and handles the project hierarchy planning, custom-field mapping, comment preservation, attachment migration, and validation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on task count and source platform, with separate line items for comment depth, attachment volume and Rules rebuilds so the scope is transparent before signature.

This is one of several legitimate paths — the right choice depends on whether you want an Asana Solutions Partner, Asana's free in-house service, a specialist tool, an iPaaS-first approach, or an end-to-end managed migration vendor. \[Explore FlitStack →]\(/contact)

In this guide

## Asana migration checklist

A phased, atomic punch list for moving project, task, and workflow data into Asana — covering decisions, prep, export, transform, sandbox testing, cutover, validation, and cleanup. Typical timeline: 4–12 weeks.

0\. Decide & Plan 10 tasks

- **Document the migration scope by Asana object class: Workspaces or Organizations, Teams, Projects, Sections, Tasks, Subtasks, Custom Fields, Portfolios, Goals.** Each class has different import paths and tier gating; list which are in scope and which are explicitly out.*If skipped: Discovering mid-cutover that Portfolios or Goals were assumed in-scope but were never planned for blocks executive reporting on day one.*
- **Decide between an Organization model and a Workspace model in the destination.** Personal Projects organizations cannot be used as a source or destination domain, and Organizations cannot be migrated to Workspaces. Pick the destination shape before any other work.*If skipped: Choosing the wrong domain type forces a full re-do because the platform does not convert between the two.*
- **Decide the historical-data scope: how many years of completed tasks, how far back for comments, and whether deleted tasks are included.** Deleted objects (teams, projects, tasks) are not copied during a platform-assisted migration, and completed-task history is often re-stamped on CSV import.*If skipped: Users expect to see closed work on day one and find a blank Completed view, eroding trust in the new system.*
- **Decide and document the strategy for record ownership: keep original assignees, reassign to a single migration user, or best-match by email.** Asana matches assignees on the email address in the Assignee column at import time.
- **Identify GDPR, SOC 2, HIPAA, and FERPA obligations that apply to the data set.** Asana holds ISO 27018:2019, ISO 27701:2019, SOC 2 Type 1 with HIPAA, and SOC 2 Type 2 with Privacy attestations; confirm your DPA covers the source data.*If skipped: A regulated data set landing in an unconfigured tenant can trigger a reportable incident before users even log in.*
- **Decide whether EU data residency is required and confirm the destination domain is provisioned in the Frankfurt region if so.** Data residency in the EU data center is an Enterprise add-on and an Enterprise+ inclusion; user authentication and seat-usage data remain outside the residency boundary.*If skipped: If residency is needed but not provisioned at sign-up, switching regions later requires re-migrating the domain through Asana's data migration request flow.*
- **Set the cutover date, the source-system freeze window, and the read-only date.** Pick a low-activity window; communicate it in writing to all source-system users at least two weeks ahead.
- **Assign a single accountable DRI for the migration project.** One named owner for end-to-end execution; secondaries for export, transform, load, and validation.
- **Document explicit success criteria for declaring the migration complete.** Examples: zero variance in active task counts per team, all subtasks linked to their parent, all attachments accessible, three power users sign off per team.*If skipped: Without written criteria, the project never formally ends and the source system never gets decommissioned.*
- **List out-of-scope items explicitly in the project plan.** Common out-of-scope items: deleted tasks, archived projects older than X years, board-only attachments, legacy integrations.

1\. Pre-Migration Prep 20 tasks

- **Export current record counts per object from the source as a baseline.** Tasks, completed tasks, subtasks, projects, sections, custom fields, attachments, comments, users.*If skipped: Without baseline counts, you cannot prove the destination received everything during validation.*
- **Run a deduplication pass on source users using email as the match key.** Asana matches by email when assigning tasks and when applying CSV user import; duplicate emails create ambiguous matches.*If skipped: Duplicate emails resolve to the wrong user during import and reassignment becomes a per-task cleanup job.*
- **Normalize email casing on every source user record to lowercase.** Email casing inconsistencies cause assignee lookups to silently fail on some imports.
- **Identify tasks with empty required-equivalent fields (assignee, due date, project) and resolve.** Decide per field whether to backfill, drop, or import as null.
- **Audit source picklist / dropdown values per custom field and collapse near-duplicates.** Asana single-select and multi-select fields are case-sensitive on import; "Option" and "option" become two separate values.*If skipped: Importing case-mismatched values silently creates a parallel dropdown option, doubling the value list and breaking filters.*
- **Identify any source dropdown field exceeding 500 options.** Asana caps drop-down custom fields at 500 field value options; values above that cap must be reshaped before import.*If skipped: An over-cap dropdown imports the first 500 values and silently drops the rest, orphaning tasks tagged with truncated values.*
- **Identify any source object with more than 100 custom fields on one project equivalent.** Asana allows up to 150 custom fields in a single project and up to 60 fields per task via multi-homing.
- **Provision the production Asana domain and confirm tier (Starter, Advanced, Enterprise, Enterprise+).** Tier determines access to Custom Fields, Rules, Bundles, Portfolios, Goals, Forms, Approvals, Service Accounts, the audit log, and the Time tracking field.*If skipped: If you build the migration plan assuming Enterprise features and the domain is on Advanced, half the workflow rebuild stops on day one.*
- **Request an Asana Sandbox via the super admin console.** Sandboxes are available on Enterprise+ and mirror production for performance, speed, and security; use one for the test migration in Phase 4.*If skipped: Testing against production exposes real users to dirty test data and rules they did not opt into.*
- **Create Teams in the destination Organization in the intended hierarchy.** Teams are containers for Projects; create them before importing projects so projects land in the right place.
- **Invite all required users and assign roles before any task import.** Use the CSV user import (Advanced, Enterprise, Enterprise+) to bulk-invite; guests are not processed via that import path.*If skipped: If assignees do not exist as members at import time, the Assignee column silently leaves tasks unassigned.*
- **Create the field library entries for every custom field that will be migrated.** Custom fields must exist on the destination project before import, otherwise the importer maps them into the task description text.*If skipped: Missing field definitions cause data to land in the task description as free text, requiring per-task re-parsing.*
- **Create a dedicated External ID custom field on every project receiving imported tasks.** Asana's ID custom field is platform-generated; use a separate text custom field to hold the source system's primary key for upsert matching and reconciliation.*If skipped: Without an external-ID column, re-running an import after fixing a transform creates duplicates instead of updating in place.*
- **Configure org-level settings (locale, timezone, working days, default project privacy).** These settings affect how the importer parses dates and how Rules evaluate them.
- **Pause every Rule and integration on the destination before import.** Rules fire on task creation and field changes; an active rule during bulk import can mass-assign, mass-notify, or mass-archive thousands of records.*If skipped: An unpaused notification rule during a 10,000-task load sends 10,000 emails to assignees who do not yet know the migration happened.*
- **Disable email notifications for the migration service account that will run the import.** Even with rules paused, native activity notifications still go to followers; muting at the account level cuts the noise.
- **Communicate the source-system freeze date and cutover window to every end user in writing.** Specify the exact time the source goes read-only and the exact time the destination opens.*If skipped: Users editing source data after the export point create a delta that has to be reconciled by hand at cutover.*
- **Schedule a 30–60 minute training session on Asana basics segmented by role.** Cover My Tasks, Inbox, List/Board/Timeline views, sections, dependencies, and search; admins get a separate session.
- **Identify and brief a roster of first-responders for the first 48 hours after cutover.** One per team is enough; their job is to triage "where did my task go" questions, not to do training.
- **Pre-write a one-page "day-one in Asana" reference and link it from the destination's home banner.** Login URL, how to find their tasks, who to contact, where the source archive lives.

2\. Source Export 13 tasks

- **Export every in-scope project as CSV including all standard and custom fields.** Include task name, description, assignee email, due date, start date, completion status, completion date, section, dependencies, follower emails, and every custom field.*If skipped: A missing custom field column at export time means re-pulling the entire dataset later, often after the freeze has started.*
- **Export the subtask tree to a depth of 5 levels with explicit parent linkage.** Asana caps subtasks at 5 levels; any deeper structure must be flattened before import.*If skipped: Subtasks at depth 6+ that are not flattened in the export are silently dropped at the importer.*
- **Export task dependencies as a separate junction file (predecessor task ID, successor task ID).** The Asana CSV importer can set dependencies between tasks within the same import file when the column references the dependent task name or ID.*If skipped: Dependencies imported in separate files from their tasks fail to link because the importer needs the referent in the same file scope.*
- **Export task comments with author email, timestamp, and rich-text body.** The Asana CSV importer does not import comments; record them as a CSV per task so they can be re-posted as historical context.*If skipped: Skipping comments at export time means losing every conversation thread tied to a task once the source is decommissioned.*
- **Export attachments with metadata: file name, size, MIME type, and the task ID it belongs to.** Asana hosts up to 100 MB per file uploaded from local; larger files require Box, Dropbox, Google Drive, or OneDrive/SharePoint links.
- **Download the binary contents of every Asana-hosted attachment in scope.** External-storage links (Drive, Box, Dropbox, OneDrive) can be preserved as links; native uploads must be re-attached to the destination task.*If skipped: If source is decommissioned before binaries are pulled, every in-task uploaded file becomes irretrievable.*
- **Export the user roster with name, email, role, team membership, and reporting line where applicable.** This becomes the input for the CSV user import on the destination.
- **Export every custom field definition including type, options list, and default value.** Include single-select, multi-select, text, number, percent, currency, date, people, formula, ID, time tracking, timer, and reference fields.
- **Export every Rule, Bundle, Form, Approval, and Workflow definition as screenshots or structured notes.** Rules and Bundles do not transfer through the CSV importer; they will be rebuilt manually in Phase 7.*If skipped: Without a captured definition, rebuilding a complex multi-trigger Rule from memory after cutover is error-prone and slow.*
- **Export Portfolio composition, Goal hierarchy, and report definitions.** Portfolios and Goals are not part of CSV import; capture the structure so it can be recreated.
- **Export Project status updates and Project descriptions as separate files.** These do not move through the project CSV importer.
- **Capture screenshots of every saved dashboard, report, and search filter in the source.** Reporting layouts are recreated by hand in the destination.
- **Record the exact UTC timestamp of each export.** This is the baseline against which the cutover delta is computed.*If skipped: Without a recorded export timestamp, the delta load in Phase 5 either over-pulls or under-pulls and creates duplicates or gaps.*

3\. Transform & Map 24 tasks

- **Build a master mapping spreadsheet: source field, destination Asana field, transform rule, required-on-import flag.** Include one row per source field per object type; this becomes the single source of truth for the transform.*If skipped: Without a documented mapping, every transform decision is reinvented per-engineer and produces inconsistent output.*
- **Resolve every picklist value mismatch between source and destination.** Asana single-select values are case-sensitive; "In Progress" and "in progress" import as two separate values.*If skipped: Case-sensitive value collisions silently inflate the dropdown option list and exhaust the 500-option cap.*
- **Choose the upsert key per object class: typically external-ID text field for tasks, email for users.** The CSV importer does not natively upsert, so store the source ID in a dedicated External ID custom field for cross-system reference and reconciliation.*If skipped: Without an upsert key, a re-run produces duplicates instead of updates and forces a manual dedup pass.*
- **Decide handling for source fields with no Asana equivalent: drop, concatenate into task description, or create a new custom field.** Document the call per field so reviewers can audit it.
- **Confirm per-project custom field count stays at or below 150.** Per-project limit is 150 custom fields; per-task limit is 60 via multi-homing.
- **Convert all date fields to ISO-8601 (YYYY-MM-DD) for due dates and start dates.** Asana CSV import accepts multiple formats but mixing MM/DD/YYYY and DD/MM/YYYY in one file causes silent reinterpretation.*If skipped: Date format drift between rows causes some tasks to land with a due date one year off and no error from the importer.*
- **Convert all datetime fields used in formulas to UTC.** When custom fields like Created on and Completed on are used in Asana formulas, the formula engine treats them as UTC timestamps regardless of display timezone.
- **Re-encode every text field as UTF-8 and verify with a byte-order-mark check.** Non-UTF-8 text causes attachment filenames and task names to render as garbled mojibake (notably on Japanese and Cyrillic strings).*If skipped: Mojibake in task names is irreversible once imported and requires re-importing the affected rows.*
- **Escape commas, double quotes, and newlines inside text fields per RFC 4180.** Unescaped quotes split rows mid-import and shift columns out of alignment downstream.
- **Truncate task name fields to fit Asana's display ceiling; preserve full text in the description.** Long task names render but degrade list-view usability; keep names under \~120 characters.
- **Translate source rich-text markup to Asana's supported markdown subset.** Asana descriptions accept H1, H2, bold, italic, strikethrough, blockquote, ordered/unordered lists, code, and links; everything else is stripped to plaintext.*If skipped: Unsupported HTML in descriptions gets silently stripped and tables, images, or color spans disappear without warning.*
- **Split or aggregate source files larger than 100 MB before upload.** Asana caps native attachments at 100 MB per file; larger artifacts must be moved to Drive/Box/Dropbox and attached as a link.
- **Capture the original creation date of every task in a dedicated "Source Created On" date custom field.** The CSV importer re-stamps creation date to the import moment; the original is only preserved if you put it into a custom field.*If skipped: Without a preserved creation date, every historical task looks like it was created on cutover day and breaks aging reports immediately.*
- **Capture the original completion date for completed tasks in a "Source Completed On" date custom field plus a Status single-select set to "Complete".** Pair this with a Rule that, when Status = Complete on import, marks the task complete and clears Status. Build the Rule before import.*If skipped: Completed-task history without a re-completion mechanism leaves every imported closed task open in the destination.*
- **Map source assignee identifiers to Asana user email addresses one-to-one.** Use the user roster from Phase 2; unresolved assignees become unassigned tasks.
- **Decide the attachment strategy: re-upload binaries to the destination task versus preserve as external-storage links.** Re-upload preserves the file inside Asana's 100 MB cap; linked files keep their permissions and are not bounded by Asana storage.
- **Collapse the source project hierarchy into Workspace → Team → Project → Section → Task → Subtask, capping subtasks at 5 levels.** Deeper hierarchies must be flattened: either promote depth-6+ nodes to siblings, or fold them into the parent's description, or relocate them to their own project.*If skipped: Subtasks beyond depth 5 are silently dropped by the importer with no error line for the affected row.*
- **Translate source task dependencies into Asana's blocking / blocked-by model via the CSV "Dependent on" column.** List the predecessor task name or row reference in the Dependent on column of the same CSV; cross-project dependencies are not date-shift-aware.*If skipped: Cross-project dependencies that shift dates in the source do not propagate date shifts in Asana, so downstream timelines silently desynchronize.*
- **Migrate Everhour or other source time-tracking entries into Asana's native Time tracking custom field.** Asana provides a documented Everhour-to-Time-tracking-field migration path; for other time tools, re-load as Estimated time and Actual time columns on the task.*If skipped: Time entries left in the source ledger after cutover make billing and capacity reports incomplete from day one.*
- **Re-create comment threads by re-posting each historical comment as a task story, including a prefix with the original author and timestamp.** The CSV importer does not carry comments; re-posted stories are timestamped at post time, so the prefix preserves the original conversation order.*If skipped: Re-posted comments without an original-author prefix all appear to come from the service account, making thread attribution useless for audit.*
- **Translate source custom-workflow statuses into either Asana Sections or a single-select Status custom field, not both.** Sections work for visual board columns; a Status field works better for cross-project reporting through Portfolios. Pick one per project class and stay consistent.
- **Re-create recurring task rules at the destination — they are configured per-task in Asana, not migrated.** Recurrence is a task-level setting ("set to repeat") and is not part of the CSV schema; configure on the template task post-import.*If skipped: Recurring tasks left without their recurrence setting silently stop generating future instances after cutover.*
- **Rebuild source Forms as Asana Forms; capture submitter-name and email questions explicitly.** Asana Forms create tasks on submit and pre-fill assignee and project; mirror the source form fields one-to-one.
- **Stage the Rules and Bundles rebuild list with priority order.** Rules cannot be migrated; document each Rule's trigger and action so they can be rebuilt in Phase 7 as Bundles where reused across projects.

4\. Sandbox Test Migration 14 tasks

- **Load a 1–5% representative sample of each object class into the sandbox.** Include at least one record with a long description, one with a subtask at depth 5, one with non-ASCII characters, and one with an at-limit dropdown value.*If skipped: A sample that does not exercise edge cases passes sandbox and then fails on the first odd row in production.*
- **Run the CSV Importer against a sandbox project and capture every parser warning and rejected row.** The importer surfaces a preview screen before commit; document any column it failed to auto-map.
- **Validate that subtasks landed at the correct depth and linked to the correct parents.** Spot-check the deepest subtask in the sample to confirm depth-5 preservation.*If skipped: If the importer dropped depth-5 subtasks during the sample, the same will happen in production at scale.*
- **Validate that custom fields landed in dedicated columns, not in the task description.** If field definitions were not created in advance on the destination project, the importer dumps custom field data into the description as free text.*If skipped: Description-dumped field data is invisible to filtering, formulas, and Portfolios.*
- **Confirm dropdown values are case-exact between source CSV and destination dropdown options.** Case mismatches create parallel options; check the field's option list for newly-spawned entries.
- **Confirm assignees resolved to existing destination users on every sample row.** Filter the sandbox project by "No assignee" and investigate every result.
- **Confirm dependency links landed: open the predecessor task and verify the successor appears in the blocking list.** Dependencies set via the CSV column appear in the task pane under "Dependent on" / "Blocking".
- **Confirm completion status set correctly via the post-import Rule.** Imported tasks with Status = Complete should fire the Rule and mark the task complete; tasks without that flag should remain open.
- **Test attachment re-upload on a small sample (5–10 files).** Watch for file-too-large and unsupported-media-type errors; both indicate per-file fixes before bulk run.
- **Test comment re-posting on a small sample.** Confirm story timestamps are post-cutover (expected) and that the author-prefix text renders cleanly.
- **Run a full-volume rehearsal in the sandbox or the largest available subset.** Rehearsal surfaces throughput ceilings and timing issues well before production.*If skipped: Discovering throughput issues for the first time during the production cutover blows the cutover window.*
- **Time each step of the rehearsal and extrapolate to production volume.** If the rehearsal extrapolates beyond the cutover window, either parallelize, batch larger, or expand the window.*If skipped: Underestimating cutover duration leaves users locked out of both systems for hours longer than planned.*
- **Have one power user per team spot-check 10–20 sandbox tasks for correctness.** They know what "right" looks like; the migration team doesn't.
- **Obtain written sandbox sign-off from each functional lead before scheduling production.** An email or a signed task in Asana is enough; the point is creating a clear go/no-go artifact.*If skipped: Skipping sign-off means accountability for migration defects defaults back to the migration team forever.*

5\. Production Cutover 12 tasks

- **Confirm the source system is in the announced freeze and no writes occurred in the last hour.** Pull an audit log or last-modified report from the source.*If skipped: Late writes in the source after the export point become an invisible delta that has to be reconciled by hand.*
- **Take a final full export of source data and compute the delta against the Phase 2 baseline.** Only the delta needs to load if the bulk has already been loaded into a near-production environment.
- **Re-confirm every Rule and integration on the destination is still paused.** Someone may have unpaused something during sandbox testing; verify before the load.*If skipped: A single unpaused notification Rule firing during a multi-thousand-task load triggers an inbox flood that drowns first-responders.*
- **Load Users first via CSV user import.** Every subsequent assignee lookup depends on users being present.
- **Load Teams second, then Projects, then Sections, then Tasks, then Subtasks in depth order (depth 1 first), then Dependencies.** Dependencies refer to task IDs that must already exist; loading them last avoids forward-reference failures.*If skipped: Loading in the wrong order forces re-runs that consume cutover time and increase the chance of conflicting writes.*
- **Load Custom field values immediately after Tasks but before Comments and Attachments.** Comments and attachments reference task IDs; loading them later means task identity is already stable.
- **Re-post comments as task stories using the prefix format from Phase 3.** Batch with exponential backoff if the platform throttles bulk operations.
- **Re-upload attachments to the destination task referencing the parent task identifier.** External-storage links can be posted as attachment records with a URL without uploading bytes.
- **Capture every job identifier, batch row count, and error log to a file.** These become the audit trail for reconciliation and incident response.*If skipped: Without captured logs, diagnosing a missing record post-cutover means re-running the analysis from scratch.*
- **Cross-check destination row counts against source counts at each load step.** Run a query after each step; investigate any variance before moving on.*If skipped: Treating partial-load failures as "fix later" means cascading failures in later steps that reference the missing rows.*
- **If any load step fails partway: halt, diagnose, fix the transform, and re-run idempotently.** Use the external-ID custom field as the upsert key so re-runs update rather than duplicate.
- **Re-enable Rules and integrations only after all loads complete and validation in Phase 6 is in flight.** Stagger re-enabling: notification rules last.

6\. Validate 18 tasks

- **Compare total task counts per project: source baseline versus destination post-load.** Investigate any variance beyond what the documented delta accounts for.*If skipped: An unexplained gap of even a few tasks usually indicates a systemic transform bug affecting more rows than the visible miss.*
- **Compare open task count by team in source versus destination.** Run the same filter on both sides and confirm the totals match.
- **Compare completed task count per project, scoped to the historical window.** Completed tasks rely on the Phase 3 Status field plus Rule mechanism; this check confirms the Rule fired.*If skipped: If the completion-state Rule misfired, every imported "complete" task is still open and clutters live work views.*
- **Cross-check 25–50 randomly-selected tasks field-by-field between source and destination.** Stratify the sample: 10 from depth-1, 10 from deeper subtasks, 10 with attachments, 10 with custom fields populated, 10 with comments.*If skipped: Sampling only depth-1 tasks misses the bugs that hit deep subtasks and attachment-heavy records.*
- **Verify every custom field value arrived intact on the sampled tasks.** Check single-select, multi-select, number, date, people, and formula outputs.
- **Verify a 20-task sample of parent-subtask links resolves correctly.** Open each subtask and confirm its parent matches the source.*If skipped: Broken parent links orphan subtasks visually under the project root, making them effectively invisible to the assignee.*
- **Verify dependencies: open the predecessor of 10 sample tasks and confirm the blocking list contains the right successor.** Dependencies established via the CSV "Dependent on" column should resolve in the task pane.
- **Verify attachments resolve: open 20 sampled tasks and confirm every attachment opens.** Check both Asana-hosted re-uploads and external-storage links.*If skipped: External links broken by post-migration storage permission changes (Drive folder moves, Box sharing changes) silently 404 with no surface alert in Asana.*
- **Verify multi-homed tasks appear in every project they belong to.** Asana lets one task live in multiple projects; if the source had similar multi-home behavior, confirm the import recreated each project membership.
- **Verify followers / collaborators on a sample of tasks resolved to existing destination users.** Unresolved follower emails fail silently at import.
- **Verify the original-creation-date strategy worked: open a sample of imported tasks and confirm "Source Created On" matches the source.** If this field is empty on any sample task, the transform pipeline regressed.*If skipped: Empty Source Created On on imported tasks means cutover-day-only timestamps and broken aging reports across every project.*
- **Verify completed-task history: confirm Source Completed On is populated on every imported closed task.** Spot-check against the source export.
- **Pull the Audit Log for the import window and confirm no unexpected event types.** Audit log access is restricted to Service Accounts on Enterprise+, legacy Enterprise, or Enterprise with the Compliance Management Add-on; events are retained for 90 days.
- **Confirm data residency: if EU residency was elected, confirm task data is stored in the Frankfurt region.** Customer task data including comments and attachments respects residency; user authentication and seat-count telemetry do not.*If skipped: Residency misconfiguration discovered after live use creates a regulatory exposure that requires re-migrating the domain through Asana's data migration request flow.*
- **Confirm retention policies: if data retention is enabled, validate inactivity rules match policy.** The data retention feature targets inactive projects and orphan tasks; recovery window is 30 days from trashing.
- **Have 3–5 power users per team walk through their day-one workflows in the destination.** My Tasks view, project board view, completing a task, posting a comment, attaching a file, filtering by custom field.*If skipped: Defects only visible inside daily workflow (broken filters, missing fields on board view) ship to users if power users do not catch them first.*
- **Capture every defect in a tracking project with severity, owner, and target fix date.** Severity 1 (blocking workflow) gets fixed before go-live; severity 2 and 3 ship as known issues with comms.
- **Obtain written sign-off from the migration sponsor and each functional lead before Phase 7.** Sign-off references the success criteria documented in Phase 0.*If skipped: Skipping written sign-off makes the project owner the implicit owner of every post-migration data defect forever.*

7\. Post-Migration Cleanup 12 tasks

- **Announce go-live to every end user with login URL, day-one reference link, and the first-responder contact.** Send the same content via email and via an Asana project status update so it is reachable from inside the new tool.
- **Re-enable notifications progressively over the first 24 hours.** Stagger to avoid notification floods: critical assignment notifications first, follower notifications later.*If skipped: Re-enabling everything at once on day one floods inboxes and burns user goodwill before adoption begins.*
- **Rebuild every Rule from the captured definitions in Phase 2.** Where the same Rule applies to multiple projects, package it as a Bundle for centralized management.*If skipped: Rules rebuilt one-off per project drift over time and re-create the configuration sprawl the migration was meant to fix.*
- **Rebuild Forms from the captured definitions in Phase 2.** Verify each form points at the right project and pre-fills the right fields.
- **Rebuild Portfolios, Goals, and saved reports.** Portfolio rollups depend on custom number fields existing in member projects; verify the source field is the same one populated by the import.
- **Re-establish integrations: SSO provisioning, calendar sync, Slack, BI/reporting connectors.** Use the platform's standard integration flows and rotate any credentials that were used for the migration run.*If skipped: Long-lived credentials left active after migration are a soft target for an audit finding against a freshly-loaded dataset.*
- **Run a one-hour training refresher 7 days after go-live to address surfaced questions.** By day 7, users have hit real workflow questions the day-one training did not cover.
- **Set the source system to read-only on the announced read-only date.** Confirm no edit paths remain (UI, integrations).
- **Archive source-system exports (CSV, JSON, attachment binaries) to long-term storage with restricted access.** Retain per the data-retention policy decided in Phase 0; encrypt at rest.*If skipped: Source archives kept on the team drive without encryption are a soft target for an audit finding.*
- **Schedule a 30-day post-migration retrospective.** Cover what went well, what surprised, what carried forward as known issues.
- **Decide and document the source-system decommission date.** Typically 60–90 days after read-only, after the final retention window passes.
- **Close the migration project formally: final status report, lessons-learned log, sign-off recorded.** Project closure ends the engagement and frees the team to move on.

Questions, answered

## Migrating to Asana: questions

How long does migration to Asana take?

A small Trello or spreadsheet migration with under 5,000 tasks and standard objects runs one to two business days end-to-end. A mid-market project from Monday, Wrike or ClickUp with comments, attachments, dependencies and Rules rebuilds runs two to four weeks of elapsed time, including dry runs, validation, training and hyper-care.

Can I migrate from Monday.com to Asana?

Yes. Asana's CSV Importer accepts Monday-exported CSVs and preserves task name, description, assignee, dates, subtasks, dependencies and custom fields. Comments, attachments and board-level automations do not import via CSV — use a third-party migration tool like Altosio for comment preservation. Plan a Status-column-to-Section-or-custom-field mapping decision upfront.

Can I migrate from Trello to Asana?

Yes, and Trello-to-Asana is usually the cleanest migration shape because the object models align — Boards become Projects, Lists become Sections, Cards become Tasks, Checklists become Subtasks. Use the CSV Importer or Altosio. Power-Ups, Butler automations and Trello card history do not transfer and need rebuilding.

Does Asana preserve original timestamps on import?

No. \`created\_at\`, \`modified\_at\`, \`completed\_at\` and \`created\_by\` are Asana-managed system fields and cannot be overridden. Every imported task is stamped to import day. The mitigation is custom Legacy Created Date, Legacy Completed Date and Legacy Created By fields populated from the source export.

Can I import completed tasks into Asana?

Not directly. The CSV Importer always lands tasks as incomplete, regardless of source state. The workaround is a Status single-select custom field plus a destination-project Rule that maps status = Complete to mark-complete after import. Forum threads document this as the only reliable round-trip for completion state.

What happens to comments and attachments during migration?

Comments and attachments do not import via the CSV path. Comments require a third-party migration tool that recreates them per task. Attachments can be re-uploaded into Asana Files or re-linked from Dropbox / Drive / Box / OneDrive. Asana's per-file upload cap is 100 MB; larger files must be linked, not uploaded.

Is there an undo or rollback for Asana imports?

There is no native bulk-rollback in Asana. Per-task deletes land in trash for 30 days on Enterprise, but there is no Restore-style versioning. The practical rollback strategy: stamp every imported row with an Import Batch ID custom field, archive the affected project, and re-import from the cleaned source.

## Sources

1. [Asana, Inc. — Wikipedia](https://en.wikipedia.org/wiki/Asana,_Inc.)
2. [Prepare data for CSV import — Asana Help Center](https://help.asana.com/s/article/preparing-data-for-csv-import?language=en_US)
3. [Asana CSV Importer — Asana Apps](https://asana.com/apps/csv-importer)
4. [Import data from other tools to projects in Asana — Asana Help Center](https://help.asana.com/s/article/import-data-from-other-tools-to-projects-in-asana?language=en_US)
5. [How to Import CSV Files into Asana — Asana Help Center](https://help.asana.com/s/article/how-to-import-csv-files-into-asana)
6. [How to use Smart Import — Asana Help Center](https://help.asana.com/s/article/smart-import)
7. [Advanced CSV import options — Asana Help Center](https://help.asana.com/s/article/advanced-csv-import-options)
8. [How many files can I upload to Asana? — Asana Forum](https://forum.asana.com/t/how-many-files-can-i-upload-to-asana-the-goal-is-to-be-paperless/49679)
9. [List of technical and data limitations in Asana — Asana Forum](https://forum.asana.com/t/list-of-technical-and-data-limitations-in-asana/236641)
10. [Custom field types & limitations — Asana Help Center](https://help.asana.com/s/article/custom-field-types-and-limitations)
11. [How to use Asana Sandboxes — Asana Help Center](https://help.asana.com/s/article/asana-sandboxes)
12. [Creating duplicate records in Asana importing data from CSV file — Asana Forum](https://forum.asana.com/t/creating-duplicate-records-in-asana-importing-data-from-csv-file/526544)
13. [Object hierarchy — Asana documentation](https://developers.asana.com/docs/object-hierarchy)
14. [Limit of 500 options within a custom field — Asana Forum](https://forum.asana.com/t/limit-of-500-options-within-a-custom-field/1031535)
15. [How to use formula custom fields — Asana Help Center](https://help.asana.com/s/article/formula-custom-fields)
16. [Raising the per-project custom fields limit from 30 to 100+ — Asana Forum](https://forum.asana.com/t/raising-the-per-project-custom-fields-limit-from-30-to-100/332951)
17. [Asana Custom Field Features — Asana](https://asana.com/features/project-management/custom-fields)
18. [Audit log — Asana Help Center](https://help.asana.com/s/article/audit-log)
19. [Completed tasks when importing a CSV file into Asana — Asana Forum](https://forum.asana.com/t/completed-tasks-when-importing-a-csv-file-into-asana/192682)
20. [How to use CSV user import — Asana Help Center](https://help.asana.com/s/article/csv-user-import)
21. [Preserving creation date when importing tasks — Asana Forum](https://forum.asana.com/t/preserving-creation-date-when-importing-a-task-from-personal-projects/1109610)
22. [Asana Service Partner Directory — Asana](https://asana.com/partners/channel/directory)
23. [Data migration guide — Asana Help Center](https://help.asana.com/s/article/data-migration-guide)
24. [Undo actions — Asana Forum (Product Feedback)](https://forum.asana.com/t/undo-actions/35)
25. [How to migrate data within Asana — Asana Help Center](https://help.asana.com/s/article/data-migration-guide)
26. [Dependencies between tasks of different projects — Asana Forum](https://forum.asana.com/t/dependencies-between-tasks-of-different-projects/172827)
27. [CSV Import dependent tasks to a project — Asana Forum](https://forum.asana.com/t/csv-import-dependent-tasks-to-a-project/39182)
28. [Migrating time tracking data from Everhour to Asana — Asana Help Center](https://help.asana.com/s/article/migrating-time-tracking-data-from-everhour-to-asana)
29. [A comprehensive guide to migrating from a tool to Asana — Asana Forum](https://forum.asana.com/t/a-comprehensive-guide-to-migrating-from-a-tool-to-asana/1076274)
30. [Always finish an Asana migration in one sitting — Asana Forum](https://forum.asana.com/t/always-finish-an-asana-migration-in-one-sitting-if-you-can/168259)
31. [How to use task comments & attachments — Asana Help Center](https://help.asana.com/s/article/task-comments-and-attachments)
32. [Data retention policy — Asana Help Center](https://help.asana.com/s/article/data-retention-policy)
33. [Asana EU Data Centre — Asana Help Center](https://help.asana.com/s/article/asana-eu-data-centre)
34. [How to get rich text formatting from Asana task — Stack Overflow](https://stackoverflow.com/questions/tagged/asana)
35. [Import to update existing tasks (case-sensitive drop-down behaviour) — Asana Forum](https://forum.asana.com/t/import-to-update-existing-tasks/26670?page=3)
36. [Updating completion date after CSV import — Asana Forum](https://forum.asana.com/t/updating-completion-date-after-csv-import/504104)

Get a quote

## Moving to Asana?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Asana setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
