Data & export
Export tasks, milestones, or a whole project as CSV/JSON, and create reusable project templates.
on this page
sprintrr lets you take your data with you and reuse project structures.
Analytics at a glance
A project's Analytics view answers three questions from its tasks, computed live:
- Are we on pace? A burn-up from project start to launch: the plan (tasks by due date) against what got done (by completion date), with one sentence that says the gap in words.
- Where does the time go? One row per milestone: estimated hours against logged hours.
- What's stuck? Blocked and overdue tasks, with status, due date and who has them. Each row opens the task.
The burn-up and the hours count the whole project; What's stuck follows the view's search and filters.
Where to export
- Analytics → Export — the project, its tasks or its milestones, as JSON or CSV, and Save as template.
- The project header's ⋯ menu — Export JSON, Export CSV and Save as template. ⌘K finds Save as template too.
A tasks export follows the current search and filters, so filter first to export just those tasks.
Export formats
| Format | Contents |
|---|---|
| CSV | Tabular export with quoted values; suitable for spreadsheets. |
| JSON | Structured export with metadata. |
| Template | A reusable project template (.json, version 2.0). |
Tasks export
Per task: id, title, description, category, status, priority, estimated hours, actual hours, due date, created date, and completion percentage.
Milestones export
Per milestone: id, title, description, status, progress, target date, created date.
Full project export
Project metadata plus a summary (totals and counts) plus all tasks and all milestones, with an export timestamp.
Reusable templates
Exporting a project as a template captures its structure so you can spin up similar projects later:
- Metadata: name, description, author, category, difficulty, estimated duration, tags, tech stack, and AI context.
- Difficulty is inferred from total hours (roughly: under 40h = beginner, 40–120h = intermediate, 120h+ = advanced).
- Project type and tech stack are inferred from task content when not explicit.
- Milestones and tasks are reset to Not Started, and dates are stored as offsets so they recompute from whatever start date you choose when instantiating the template.
tip:
Templates are ideal for repeatable engagements — client onboarding, launch checklists, recurring sprints — where the shape of the work is stable but the dates and details change.
Related
- Projects — what gets exported.
- AI generation — generating vs. templating a starting structure.
Something unclear or out of date? Email support@sprintrr.ai — the subject line already names this page.