Migrate from Trello to Asana

Trello workspaces map to Asana Workspaces for Standard-tier destinations or to an Asana Organization at Enterprise. We preserve workspace-level member lists, invite permissions, and any organization-level settings during migration. Multi-workspace Trello accounts generate multiple Asana workspaces or a single Asana Organization with multiple Teams depending on the customer's target structure.

Each Trello Board migrates as an Asana Project. Board visibility (public/private) maps to Asana's Project privacy settings, and the board description becomes the Project brief. Board background color and cover image do not have an Asana equivalent and are not preserved. We create the Project in Asana before importing any child records so that Section and Task inserts have a valid parent reference.

Trello Lists map directly to Asana Sections within the target Project. List order within the board is preserved as Section sequence order. Archived Lists are migrated as Sections marked complete in Asana. List-level automation triggers in Butler are documented separately and not migrated as automation rules.

Trello Cards migrate to Asana Tasks. Title, description (with Markdown rendering preserved), due dates, start dates, cover colors, and position within the list transfer directly. Card URL is stored in an Asana custom field for traceability back to the source Trello board. Tasks are inserted into their parent Section by resolving the List name to the created Section GID.

Trello Cards allow multiple members to be assigned, but Asana Tasks support exactly one assignee. We designate the first Trello assignee as the Asana Task assignee and add remaining members as Asana Followers. All assignees appear in the migration report so the customer can audit follower assignments post-migration.

Trello Checklists on Cards map to Asana Subtasks. Each checklist item becomes a Subtask with its own completion state, due date, and assignee preserved. Multi-checklist cards generate multiple subtask groups within the parent Task in Asana.

Trello Labels (color-coded per board) map to Asana Tags. Label name and color are preserved as the Tag name and tag color in Asana. Tags are project-scoped in Asana, so labels from multiple boards generate tags in their respective migrated Projects.

Trello Custom Fields using the core API (available on Standard and above) migrate directly to Asana Custom Fields of matching type: text to text, number to number, date to date, checkbox to checkbox, dropdown to enum. We validate type compatibility during discovery and flag any unsupported field configurations before migration.

Boards created before Custom Fields became a core feature may store field definitions and values in card pluginData rather than the structured API. We detect the storage mechanism during discovery and apply the appropriate extraction method. Legacy pluginData extraction is less reliable and may require a manual field-value audit post-migration for boards with complex custom field histories.

Trello file attachments download from Atlassian S3 and re-upload to Asana's attachment storage. We preserve original filename, file size, uploader name, and upload timestamp. Attachments over 100 MB cannot be pushed through the Asana API and are flagged with a download link to the source Trello file for manual re-upload. Google Drive and Dropbox links stored as Trello attachments migrate as URL attachments in Asana.

Trello workspace members map to Asana Users by email address match. We build a user mapping table during discovery that links each Trello member email to their Asana User GID. This mapping is required for accurate Task assignee resolution and for Attachment metadata showing uploader name. Members without a matching Asana User go to a reconciliation queue for admin provisioning before migration begins.

Trello card comments migrate as Activity notes on the corresponding Asana Task. Comment text, author, and timestamp are preserved. Reactions and @mentions in comments are not supported in Asana's activity model and are stripped. We extract comments via the Trello Action API, not the JSON export, to ensure accurate authorship attribution.