What about Asana's project hierarchy (portfolios, goals)?

Those don't migrate, and usually shouldn't. Portfolios and goals were Asana's answer to coordinating across projects; if your usage has settled into one team running one board, you don't need a portfolio over it. If you do still need cross-project coordination, keep that piece in Asana and use {PRODUCT} for the actual production board only.

How are Asana subtasks handled?

{PRODUCT} doesn't have nested cards by design - the model is flat cards moving through phases. The honest path is: subtasks that are real work units of their own become separate cards (often in an earlier phase like "prep"); subtasks that are checklist items get folded into the parent card's description as a markdown checklist. Most teams find their Asana subtasks were 70% checklist items, 30% real work.

What about Asana automations / rules?

Don't migrate them - rebuild the ones you actually need. Most Asana rules accumulate over years ("if status = blocked, send email to alice") and most stop being useful within a quarter. Audit yours: keep only the rules whose absence would cause a real miss. {PRODUCT} has hooks + scheduled tasks for this kind of automation; for very simple cases the dashboard's built-in overdue + blocked surfaces remove the need for a rule entirely.

Can the same person migrate multiple Asana projects at once?

Yes - one CSV per project, one {PRODUCT} board per CSV. We don't recommend merging two distinct production cycles into one board; the phase shape of two cycles averaged together is noise.

What happens to Asana comments + attachments?

Comments don't ship through CSV - they live behind the API only. If the comment history is genuinely load-bearing for the team, we can help script the API export via /support; in practice 90% of teams find that comment history is conversational chatter that no one re-reads, and starting fresh in {PRODUCT} is healthier than dragging it across. Attachments come over via the CSV's URL column - {PRODUCT} keeps them as references.

Production Board

Guides

Migrating from Asana to Production Board: a focused walk-through

Asana fits cross-functional projects with many roles. If your team is smaller and the work is production-shaped, the move is an evening's work.

Migration

Asana

Setup

Guide

Finn GlasCo-Founder + Engineering

·March 10, 2026·

4 min read

Step by step

Export tasks from Asana via CSV

In Asana: open the project → ••• menu → "Export" → "CSV". One project at a time. The CSV includes task name, description, assignee, due date, custom fields, and the section the task lives in. Asana's API is also an option for very large projects, but the CSV path covers 95% of teams without a single line of code.

Map Asana sections → Production Board phases

In Asana, sections are how you visually group tasks within a project ("In progress", "Review", "Done"). They map cleanly onto {PRODUCT} phases - same idea, different name. The honest 1:1 only works if your sections were already used as phases; if you used sections as buckets-by-priority or buckets-by-quarter, treat that as a tagging axis in {PRODUCT} instead, not a phase axis.

Sections used as phases (Backlog → In progress → Review → Done) → map directly.

Sections used as priority buckets (P0 / P1 / P2) → tags, not phases.

Sections used as quarters (Q1 / Q2) → tags or separate boards, not phases.

Decide which custom fields survive

Asana custom fields range from useful (priority, customer-id, deadline-type) to accumulated cruft (a flag someone added in 2022 and nobody updates). Walk through them once and pick the 3-5 you actually use. {PRODUCT} ships native fields for priority + due date + assignee + tags; anything beyond that goes into the card description as plain text rather than as a structured field, unless you have a strong reason to keep the structure.

Import via the CSV dialog

Open {PRODUCT}, create the new board with phases from step 2, then Account settings → Import. The dialog parses the CSV, shows a 50-row preview, and commits when you're satisfied. Map the Asana "Section" column → phase, "Assignee" → owner, "Due date" → due date. Skip the rest unless they were on your step-3 keep-list.

Run side-by-side, then archive Asana

For two weeks, set the Asana project to read-only and have the team work in {PRODUCT}. The window catches what didn't migrate cleanly and gives the team a fallback. After two weeks, archive the Asana project. {PRODUCT}'s export is one click in account settings if you ever need to leave us in turn.

When the move makes sense

Asana earns its keep when you have multiple cross-functional teams handing work between roles, with custom workflows per team. {PRODUCT} earns its keep when one production team is doing the same kind of work over and over and the board is meant to keep the live state honest. If your Asana usage has settled into one team running one board for one production cycle, the migration pays off; if you're using project-level grouping across multiple teams, Asana is still the right tool.

FAQ

Frequently asked

Share this article

Try Production Board

Free plan, no credit card. We host in Germany. You can export and delete everything self-serve.

Written by

Finn Glas

Co-Founder + Engineering

Finn is one of the Co-Founders. He owns the engineering side, the infrastructure, and most of the late-night fixes that ship before anyone notices.

finn.glas at aicuflow dot comLinkedIn Website