Migrating to Salesforce Commerce Cloud (SFCC)

Last updated: August 17, 2026

Planning a migration? Let us know

As soon as a migration is on your roadmap, reach out to your Noibu CSM — the earlier the better, as it gives us time to prepare and support you through the transition. Sharing your plans early means we can keep your monitoring running smoothly with no gaps in coverage.

When you're ready, please fill out the form below with the details of your planned migration. It captures everything we need, including your new domain URLs, any changes to your site design or checkout flow, new payment gateways, updated success URLs, and whether you'd like your existing data wiped.

Fill out this form: Migration Form ​

Choose your deployment method

Your install path depends on the storefront architecture you're moving to.

1) Storefront Next

Install the Noibu Commerce App from Business Manager, under Merchant Tools > Ordering > Commerce Apps. It takes minutes: you'll merge one auto-generated pull request, then add Noibu's domains to your Content Security Policy.

See here: Deploying Noibu to Salesforce Commerce Cloud (Storefront Next)

2) SFRA or SiteGenesis

Install the Noibu cartridge. It's the SFCC equivalent of our Shopify and BigCommerce apps, and it's much simpler than deploying tags manually.

The cartridge is the SFCC equivalent of our Shopify and BigCommerce apps, and it's the easiest way to add Noibu to your store — much simpler than deploying tags manually.

  1. Install from the Noibu AppExchange listing. Once you're authenticated, you'll be redirected to GitHub to complete the installation.

  2. Please start from the AppExchange listing rather than installing directly from GitHub. Going through the listing lets us know you've begun setup, so we can reach out and help you finish.

  3. Complete the configuration by following the SFCC Deployment Guide.

Supported architectures: The cartridge works with SFCC SiteGenesis and SFRA. It isn't available for PWA Kit (headless) SFCC — if that's your setup, reach out and we'll walk you through an alternative approach.

See here: Deploying Noibu to Salesforce Commerce Cloud (SFCC)

Important: Once your new deployment is live, remember to remove any previous Noibu deployment method. Running two at once can cause duplicate data and conflicts in your monitoring.

Test on a staging environment first

Before you switch your live store to the new platform, we strongly recommend deploying Noibu to your staging (or development) environment. This lets you monitor and catch errors while you build and test the new site — so you can fix issues before they ever reach your customers and confirm Noibu is capturing data correctly ahead of go-live.

Deploy Noibu to your staging site using the same method you'd use for production (see the platform sections above). Because your staging site runs on a different domain or subdomain, let your Noibu team know its URL so we can set it up for monitoring alongside your production domain.

Salesforce Commerce Cloud (SFCC)
SFCC provides dedicated instances: sandboxes for development and a Staging instance for testing your site before code reaches Production. See the B2C Commerce architecture guide.

What Noibu monitors

Once the cartridge is deployed, you'll have Error Monitoring, Performance Monitoring, and Session Replay. Noibu automatically captures SFCC attributes including customer_id, customer_group, order_id, order_token, cart_id, basket_id, campaign_id, promotions, and coupon_codes. Ecommerce events are collected automatically on SFRA.