Asana data backup: everything that has to survive

What's actually inside a workspace

Ask a teammate what's in Asana and they'll say "our tasks". Look closer and a living workspace has six interdependent layers — lose one and the rest lose their meaning:

• Projects and sections — the structure every task hangs on, plus the workflows built around them.
• Tasks and subtasks — with assignees, due dates, priorities and statuses.
• Custom fields — the columns your team actually works by: budgets, stages, dropdowns, links.
• Comments and activity — the reasoning and decisions behind the work. The first thing an export loses.
• Attachments — briefs, designs, contracts and assets attached to tasks.
• Dependencies and relationships — which task blocks which, and why the order matters.

Why a saved export isn't a backup

Asana lets you export a project to CSV, and full JSON exports are reserved for Enterprise admins. Either way, you get a frozen snapshot of one moment: comments, attachments, dependencies and custom field values arrive flattened or missing, and there's no faithful way to re-import them. Recovery needs two things exports lack: automation — it runs every day whether anyone remembers or not — and history, so you return to a specific day rather than to whenever the last export happened.

What Asana Backup preserves

Each daily snapshot covers all six layers: projects and sections, tasks and subtasks with every custom field value, comments and activity, attachments, assignees and dates, and the dependencies between items. Snapshots are dated and downloadable — your work stays yours, in a form you can actually read and use.