WordPress to Next.js Auto Dealer Migration

The full migration runs 4-6 weeks. Weeks 1-2 cover your WordPress inventory export and Supabase restructuring -- getting your data clean and properly indexed. Weeks 3-4 are custom design. Weeks 5-6 are build and testing. But here's what matters most: your WordPress site stays live the entire time. There's no scary weekend where everything's down. DNS only switches to Vercel once the new build is fully tested and you've signed off on it.

Pretty straightforward swap, honestly. WordPress plugins handling inventory management, lead capture, and financing calculators get replaced by native Next.js functionality built specifically for your site. No plugin dependency means no conflict risk. But the real kicker is what happens long-term -- as your catalog grows to 400, 600, 800 vehicles, performance doesn't degrade. There's no plugin author who stops maintaining their repo, no WooCommerce update that quietly breaks your lead forms.

So why does CarDealer actually time out? WordPress stores vehicles as custom post types, and the search logic loads everything into memory first, then filters. At 200 vehicles it's slow but survivable. At 500+ the server just gives up. Supabase PostgreSQL works completely differently -- indexes let it return filtered results in under 50ms regardless of inventory size. A customer filtering by make, model, year, and price gets results before they've finished thinking about hitting enter.

Yes, and we've done it. SleepDr came to us as a WordPress site sitting at a Lighthouse score of 35. After migrating to Next.js on Vercel, it hit 94. Same methodology, same stack. A WordPress dealer site has the same structural problems SleepDr had -- plugin bloat, unoptimized assets, no proper caching strategy -- and the migration produces the same kind of result.