Why teams outgrow Salesforce Commerce Cloud
Salesforce Commerce Cloud's monolithic architecture delivers reliable out-of-the-box commerce, but it creates real constraints as ecommerce teams scale. Three pain points tend to drive teams toward a different setup:
Architectural limits: Personalization must be implemented client-side, which means duplicate downloads and slower page loads.
Restricted tooling: Integrating best-in-class services requires awkward workarounds, limiting the technical options engineers have for building features and experiences.
Scaling difficulty: Under peak traffic, bloated tag managers, inefficient data pipelines, and unoptimized assets make slowdowns—or outright downtime—more likely.
These issues extend beyond performance and sales. They hurt developer experience by requiring specialized knowledge and tribal know-how, which in turn constrains hiring and retention. They also undermine the foundation for future growth and produce user experiences that push customers away.
An incremental path off the monolith
Replacing an entire ecommerce platform is high stakes when it moves millions or billions in annual revenue. An incremental migration lets teams frontend modernization while keeping the commerce backend intact.
Pick a capable frontend framework: Salesforce offers PWA Kit, but Next.js gives large-scale ecommerce sites a more robust and flexible foundation, backed by an active open-source community. Server-side rendering, image optimization, built-in routing, and a large library of pre-built components accelerate development and integrate cleanly with backends including Salesforce Commerce Cloud.
Plan for staged traffic shifts: Edge Middleware—built into Next.js and supported by the Vercel platform—makes it possible to gradually reroute traffic between a new Vercel-hosted application and the existing one.
Protect business continuity: Existing data and integrations stay in place while the new headless layer is introduced progressively.
The goal is to migrate one page or route at a time, cutting risk while gaining modern frontend capabilities. You keep Salesforce as the backend and upgrade at your own pace.
Practical techniques for a smooth transition
Start with the presentation layer
Build the new UI with Next.js and keep Salesforce Commerce Cloud as the backend. This lets you address performance issues incrementally instead of through a full system replacement. Begin with a single, low-traffic route to validate the approach before expanding.
Route traffic with Edge Middleware
Edge Middleware acts as a reverse proxy by defining rewrites directly in the Next.js configuration. That dynamically sends traffic between your existing application and the new Next.js app on Vercel. For finer control, add A/B tests or percentage-based rollouts.
This setup supports staged migration and progressive feature testing. Deploying to Vercel also provides near-instant rollback if something goes wrong.
Keep sessions consistent across platforms
Shared session strategies—encrypted cookies and centralized session storage—ensure users don't experience double logins or lost shopping carts as traffic shifts between systems. JWT-based authentication passes user data securely between apps without database lookups, and edge validation keeps user states consistent while maintaining sub-100ms response times.
Preserve SEO equity
To avoid disrupting search visibility, keep existing URL structures in place and manage redirects carefully through Edge Middleware to minimize added latency. Use proper canonical tags and monitor Google Search Console as pages move, comparing old and new data for continuity.
Test against realistic conditions
Salesforce Commerce Cloud sandbox environments can host pre-production instances with representative data, letting you test the Next.js frontend against realistic datasets before it touches the live store. Vercel's preview deployments generate a unique URL per change, and custom environments can mirror your team's workflow.
Work around Salesforce API constraints
Next.js's composability gives granular control over data fetching and caching. Strategic API response caching and Incremental Static Regeneration (ISR) reduce the number of requests hitting Salesforce Commerce Cloud, easing rate-limit pressure and improving overall performance.
What an incremental migration delivered
A global sportswear brand used this approach and saw clear improvements across performance, development speed, and revenue. They started with their homepage as an isolated test; the results were strong enough that the full migration timeline compressed from five months to two.
Performance gains
Under load testing during high-traffic periods, the new architecture proved 10x faster than Salesforce Commerce Cloud alone, thanks to edge computing, server-side rendering, and optimized data handling.
Core Web Vitals—which directly affect search ranking and site usability—improved across the board:
Time to First Byte (TTFB): 2.0s → 0.8s
First Contentful Paint (FCP): 3.2s → 1.8s
Largest Contentful Paint (LCP): 4.0s → 2.4s
Interaction to Next Paint (INP): 350ms → 200ms
Cumulative Layout Shift (CLS): 0.1 (maintained)
Developer productivity
Teams shipped more often and with greater confidence in a more engaging work environment.
Deployments went from hours to minutes
Rollbacks now take seconds
Feature flags control release timing
Development team retention improved 40%
Business outcomes
Infrastructure and UX improvements translated directly into revenue:
28% drop in cart abandonment
15% rise in mobile conversion rates
$10M in incremental quarterly online sales
Zero downtime during Black Friday, even with 125,000+ concurrent users
The work continues beyond the initial migration. Upcoming plans include a microservices-based checkout, third-party script optimization, and moving personalization to the edge. The team is confident in the path forward, backed by better monitoring and regular performance audits.
Migrating from Salesforce Commerce Cloud doesn't require a full re-platform. Focusing on the frontend with tools that support a measured, route-by-route approach unlocks a faster, more scalable architecture—without betting the business on a single cutover. Start small, validate early, and expand from there.
