[Epic]: V1→V2 parity — Import, Export, Reports, Dashboard

[nielsdrost7]

Domain epic under the V1→V2 feature-parity umbrella (#136). Full audit: 08-import-reports-dashboard.md (2026-07-18 parity audit, v1 prep/v180 vs v2 develop).

Summary: Import/export/reports are well-tracked at the epic level (#85, #145, #506) but three concrete v1 features fall through: invoices/items/payments CSV import, the invoice aging report, and per-status dashboard totals with configurable period — none of which the existing epics' bodies actually mention. A guided v1→v2 data-migration path (the single most important adoption route) has no issue anywhere.

Sub-issues

• [Invoices]: CSV import of invoices, invoice items, and payments (v1 parity) #676 — CSV import of invoices, invoice items, and payments
• [Core]: Import batch history with rollback #677 — Import batch history with rollback
• [Core]: Data migration from InvoicePlane v1 (guided importer) #678 — Data migration from InvoicePlane v1 (guided importer) — high-prio, adoption-critical
• [Reports]: Invoice aging report (v1 parity) #679 — Invoice aging report
• [Reports]: PDF export for tabular report pages #680 — PDF export for tabular report pages
• [Dashboard]: Invoice & quote status overview widgets with configurable period (v1 parity) #681 — Dashboard invoice/quote status overview widgets with configurable period
• [Core]: Export data for backup (CSV/JSON) #384 — Full-data export for backup (improved — was a single question sentence)
• [Clients]: Import clients in bulk for data migration #141 — Import clients in bulk
• [Core]: Import/Export Options for all data #85 — Per-module CSV export (epic)
• [Core]: Backup/restore #509 — Backup/restore
• [Reports]: Reports module — v1 feature parity #145 — Reports module v1 feature parity (epic)
• [Core]: The user shall be able to produce a complete Income vs Expenses report for a given period of time #71 / [Reports]: Report — Net Profit made in a financial year #72 / [Core]: The user shall be able to produce a report with total V.A.T amount that is due by the company according to the sales of products made #73 / [Core]: The user shall be able to produce a report with total Taxes amount that is due by the company according to the net profit #74 / [Invoices]: Create reports for groups of invoices #47 — new report types (v2-native, no v1 counterpart)
• [Dashboard]: Graphs stats about invoices and quotes #146 / [Dashboard]: Missing recap about projects #147 / [Dashboard]: Missing recap about tasks #148 / [Dashboard]: Financial metrics dashboard widget (profit margin, revenue) #132 — dashboard graphs, project/task recaps, financial metrics

Specific

Reach import/export/reports/dashboard feature parity with v1: CSV import of billing history, a guided v1→v2 migration tool, the invoice aging report, PDF report output, and the v1 dashboard's core per-status overview.

Measurable

All 20 sub-issues closed; a v1 user can migrate their full dataset into v2, import/export CSVs per module, see an aging report, and get the same at-a-glance dashboard totals v1 showed on login.

Achievable

#676/#677 (CSV import + rollback) establish the Importer conventions that #678 (v1 migration) reuses; #679/#680 build on the #145/PR #609 report-page pattern; #681 is independent.

Relevant

#678 is the single most important adoption route for existing v1 installations — without it, "upgrading" means starting from zero.

Time-Bound

#676/#677: 1-2 sprints. #678: 2 sprints, after #676/#677 conventions exist. #679/#680: after PR #609 merges. #681: independent, 1 sprint.