Unified migration starter
A single codebase for Vercel and Supabase.
This scaffold begins the cutover from the AWS multi-repo setup by creating one app shell, one auth surface, and one place to converge the shared product flows.
Phase 1
Migration milestones
1Single Next.js deployment
2Supabase Auth and Postgres
3Unified product routes
4Rebuilt CSV workflow
App shape
Unified route map
AuthSupabase-backed login and sign-up flow.InventoryDonation, product, and storage operations.AnalyticsRead models and dashboard surfaces.CSVDonation upload, validation, and approval workflow.TransactionsUnified transaction ledger and reporting.Donation drivesDrive management and approval workflow.ConfigurationCatalog management and legacy admin surfaces.ProfileLegacy account entry point now mapped to the unified app.Carbon trackerLegacy analytics entry point folded into unified reporting.UsersRoles, profiles, and admin workflows.SettingsEnvironment and deployment checks.FAQMigration and support reference.
Now
Initial implementation scope
AuthSupabase client helpers, an auth form, and session state are already wired into the scaffold.
BackendA health endpoint is in place to verify the unified project can run as one deployable app.
CSV workflowDonation CSV uploads now validate against the database, store artifacts in Supabase Storage, and approve into transactions.
Legacy frontendsThe old auth, inventory, analytics, and configuration page families are now represented in the single route tree.
Design systemThe shell uses a single visual language so the future inventory and analytics screens can be merged cleanly.