Appearance
Exporting
Your data is yours and every level of it has a way out. This page lists each export, what it contains and who can run it.
Exports are not backups. A backup is a restorable snapshot of the running instance, taken on a schedule. See Backups.
Board export
Open the board page menu (the dots next to the board title) and choose Export. A confirmation appears with one option, Include automations, then the board downloads as a JSON file named after the board and the date.
The file holds the board record, its members, lists, tasks, tags, custom field definitions and their values, checklists, note folders, notes and note comments. Automations are left out unless you tick the box, so a casual export does not bundle your webhook wiring.
Board admins can export their own board. The board's creator counts as an admin, and workspace owners and admins can export any board. Every export is written to the audit log.
A board JSON export is what the Truetask source of the import dialog reads, so this is also how you move a board between workspaces.
Table export
The List view has a download button in its toolbar: Download as CSV or Excel.
What you get is exactly what the table shows. The filters, sorting, grouping, visible columns and column order you have applied all carry through, and custom field columns come with their resolved values: relations export their target titles, rollups and formulas export the computed result.
See List view.
Notes export
On the Notes view of a board, choose Export notes. You get a ZIP of Markdown files that keeps the folder structure.
Files pasted or dropped into an exported note ride along under an assets folder, and that note's links are rewritten to point at them inside the ZIP. Deleted notes and folders are not included.
See Notes.
Automation export
In the Automations view, right-click an automation in the left rail (or use its menu) and choose Export. You get a JSON file holding the automation's name and its graph.
Importing it back creates the automation switched off, and a review step first tells you about anything risky in it and asks what to do with references to lists, tags, fields or people that do not exist on the target board. See Automations.
Agent workflow export
The Agent workflows dialog exports one workflow as JSON you can import on any board. Agent assignments travel by name and are matched again on import.
Three switches decide how much travels with it:
| Option | What it adds |
|---|---|
| Include hand-off launch settings | How each agent gets started when a step hands off. |
| Include launch URLs | The exact addresses Truetask calls on handoff. Off by default, so you can share a workflow without exposing your runner's endpoints. |
| Include list and tag mappings | Where steps and run outcomes move the task and which tags they set, by name. |
Signing secrets never leave the workspace, whatever you pick. See Agent workflows.
Timesheet export
The Table view of Timesheets has an Export button offering Download CSV and Download Excel. The detail frame you open from a cell has the same pair for the rows behind it.
Rounding follows the workspace regional setting, which rounds each duration in reports and exports without ever changing the logged time.
Workspace export
Go to Settings > Server > Export and press Export Workspace. Owners and admins only.
The result is a single ZIP containing workspace.json plus an attachments folder. The JSON holds every board, list, task, tag, user, comment, checklist, time entry, automation, custom field definition and value, folder, priority and group in the workspace. User records are reduced to id, name, email, role and avatar, so no password hashes travel.
The attachments folder carries the actual files and user avatars. Progress runs through three stages as it works: fetching the data, downloading attachments one by one, then zipping. An attachment that cannot be fetched is skipped rather than failing the whole export.
Available on both deployments
Workspace export is not a self-hosted-only feature. Owners and admins can run it on Truetask Cloud as well.
From the API
The same exports are reachable programmatically.
| What | How |
|---|---|
| A board | GET /api/boards/{board_id}/export, with ?include_automations=true for the graphs. |
| Notes | GET /v1/notes/export?board={board_id}, which streams the ZIP. |
| One automation | GET /v1/automations/{automation_id}/export. |
| The workspace | POST /v1/actions/export-workspace, which returns the JSON without the attachments. |
Agents get the same reach through MCP: workspace_export, notes_export_zip and automations_export.