Data & Export
Export tasks, milestones, or a whole project as CSV/JSON, and create reusable project templates.
sprintrr lets you take your data with you and reuse project structures.
Analytics at a glance
The dashboard's Analytics view summarizes a project from task data: completed / in-progress / blocked / not-started counts, total estimated vs. actual hours, completed hours, a priority breakdown (high/medium/low), a completion rate, and a time progress measure (actual vs. estimated). These are derived live from the project's 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.
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.