Migrating from SFRA to Headless: A Parity and Cutover Checklist

A migration plan begins after the architecture decision. Deciding that Salesforce B2C Commerce should have a headless storefront does not tell you how to move one there. Our guide to choosing a headless SFCC storefront covers whether the move is justified and how to weigh the available starting points. This checklist walks you through: what has to keep working, how will you prove it, and what happens if cutover fails?

A storefront migration is not a transfer of pages. It is a transfer of customer journeys and operational responsibility. SFRA may currently carry behavior in controllers, cartridges, Business Manager settings, integrations, and shared commerce services. A new frontend must preserve the outcomes that matter, even when the implementation looks nothing like the old one.

Build a parity inventory around customer journeys

Select representative journeys before designing every page. Include anonymous browsing through checkout, a returning customer's account and purchase path, and the market or fulfillment flow most likely to behave differently. For each journey, write down the input, expected result, current owner, new owner, and the evidence that will establish parity.

• Catalog and discovery: variants, inventory messages, search, sorting, recommendations, and localized content.
• Basket and checkout: quantity changes, coupons, promotion stacking, shipping, tax, payment outcomes, and order confirmation.
• Customer state: sign-in, guest checkout, account data, consent, and session expiry.
• Experience and operations: SEO URLs, rendering, accessibility, analytics, monitoring, support ownership, and release controls.

Do not call a behavior "standard SFCC" and leave its ownership blank. The important exception is often in a cartridge or integration you discover only when a realistic basket is exercised.

Prove commerce behavior at the API boundary

Make a test basket for each pricing or fulfillment rule that could change the order. Add and remove items, change quantity, apply or remove coupons, and switch shipping methods. Compare item adjustments, tax, shipping, and final totals with the current storefront, not just the cart's appearance.

The storefront should display the basket returned by B2C Commerce, not independently decide which promotions apply. Our SCAPI custom promotion walkthrough shows why a headless UI can present the right message while a calculation rule still needs work behind the API. Salesforce documents that related SCAPI and OCAPI requests can share hooks, though their execution differences must be tested in the actual operation. A legacy calculation customization is therefore a migration test case, not an item to assume will carry over unchanged.

For every external service, record its failure behavior as well as its happy path. What does checkout show when a tax quote times out, a payment is declined, or inventory changes between product view and order submission? Decide whether the storefront can retry, recover, or direct the customer to a safe next step.

Plan the cutover before building the entire replacement

Choose a bounded first release that exposes the difficult seams without requiring every market, brand, and content module at once. Map URL ownership and redirects; identify how the new frontend will receive traffic; decide what data and events must be compared during a rollout. Do not promise parallel operation until authentication, basket continuity, analytics, and rollback have been tested in that routing model.

A useful release worksheet has five columns: journey, acceptance evidence, owner, failure threshold, and rollback action. Define who can stop the release, what telemetry they will see, and which parts can actually be reverted. A rollback that depends on reconstructing customer baskets or manually restoring an integration is not yet a rollback plan.

Before launch, run the highest-risk journeys in a production-like environment with the real configuration shape and supported payment test paths. Verify search-facing pages, canonical URLs, accessibility of key flows, and event collection alongside order behavior. After launch, watch checkout errors and order outcomes with operations and commerce owners, not only frontend page speed.

The decision at the end of discovery

If the team cannot account for a pricing rule, authenticate a representative customer, or demonstrate safe order placement, pause the cutover and close that gap. If the inventory is credible and the journeys pass, expand by market or capability with a named owner for the new frontend's ongoing maintenance.

A successful headless migration is not a replica of SFRA's templates. It is a verified commerce experience that the team can release, observe, and support. Tevpro's Salesforce Commerce Cloud team can help turn the parity inventory into a contained migration plan.