Azure Backend to Nextjs Migration

About job

I have already shipped a customer-facing front-end in [login to view URL], but my API layer still lives in a separate .NET service on Azure SQL. I want everything under one roof—a single [login to view URL] repository on Vercel that talks to Supabase (PostgreSQL) instead of Azure SQL. What I can hand over • Full source code of the .NET API • The database as a .bacpac export (schema + data) Beyond that .bacpac file, there is no live Azure environment to connect to, so you will work locally or in your own cloud workspace. Key objectives 1. Database migration • Convert the Azure SQL .bacpac into a PostgreSQL dump and import it into Supabase. • Preserve all tables, relationships, seeded data, and indexes. 2. API migration • Re-implement the existing .NET endpoints as either [login to view URL] Server Actions or /api routes inside my current repo. • Match request / response contracts one-to-one so the front-end continues to function with zero changes. • TypeScript strongly preferred for new code. 3. Auth & environment wiring • Hook our Clerk authentication up to the new Supabase database. • Provide .[login to view URL] and any Supabase/Clerk keys I need to define when deploying on Vercel. 4. How-to guide • A concise markdown file that shows me, a solo founder, how to spin up the project locally, deploy it to Vercel, and add a brand-new feature (model + endpoint + UI) following your structure. Acceptance checklist (used to sign off the job) • All tables and data visible in Supabase, matching the original Azure SQL counts. • Front-end runs locally with yarn dev and passes manual smoke tests against new routes. • Deployment on Vercel builds without extra steps. • README section “Add a Feature” lets me scaffold and deploy a test endpoint in <15 min. No automated tests exist today, so if you add light unit tests while porting that’s a bonus, not a requirement.