CloudCraze to Salesforce B2B Commerce: migration guide for 2026
If your B2B store still runs on CloudCraze, it may be working perfectly well for your current needs. Problems often appear when the business wants to change something, whether that’s adding a new checkout process, introducing customer-specific pricing, or connecting another system.
CloudCraze was built on Salesforce, but its architecture differs from the B2B Commerce platform Salesforce develops today. Moving to the newer platform involves changes to the storefront, commerce data, customisations, and integrations.
In this article, we’ll look at what has changed, when a migration makes sense, and how to prepare for it. If you’re new to Salesforce commerce, our guide on what Salesforce B2B Commerce Cloud is and how to grow your business with it is a useful starting point.
CloudCraze vs Salesforce B2B Commerce on Lightning
Salesforce acquired CloudCraze in 2018. At the time, it was already a native Salesforce ecommerce application.
CloudCraze uses a managed package with its own commerce objects, Visualforce pages, and customisation model. It was designed for the Salesforce technology available at the time and can still support existing B2B stores.
Newer Salesforce B2B Commerce implementations use a different architecture. The commerce data model includes standard objects for products, price books, buyer groups, storefronts, and carts. Since Summer 2023, new B2B storefronts have been built using Lightning Web Runtime (LWR).
LWR supports configurable storefront components and custom Lightning Web Components. This gives development teams more options when adapting the buying experience without rebuilding entire pages.
It’s also worth distinguishing between moving from CloudCraze and migrating an existing Aura-based B2B Commerce storefront to LWR. These are two different projects, with different data and development requirements.
You can read more about the technology in our article on Lightning Web Runtime.
When does moving off CloudCraze make sense?
There isn’t one answer for every organisation. Some CloudCraze stores continue to meet business needs without major changes. Others have accumulated custom code and integrations that make even small improvements difficult.
The decision often comes down to what the business needs from its store over the next few years.
For example, a company might want to give distributors more control over orders, introduce new pricing models, or improve how commerce data is shared with sales and service teams. If those changes require substantial development on CloudCraze, moving to the newer platform may be worth the investment.
Maintenance is another consideration. Older customisations can become harder to change as systems and requirements evolve, particularly when the original implementation is poorly documented.
Before deciding to migrate, compare the cost of maintaining the existing store with the expected cost of moving. Include the work needed to rebuild functionality, migrate data, and support buyers during the transition.
What changes during a CloudCraze migration?
One of the biggest differences is how commerce data is organised.
Modern Salesforce B2B Commerce uses objects such as Product2, Pricebook2, BuyerGroup, and WebStore. These support product catalogues, buyer-specific pricing, and storefront configuration.
CloudCraze stores may already use Salesforce standard objects alongside package-specific data and custom logic. During migration, the team needs to identify how these records relate to the new commerce model and decide what information should be moved.
The storefront changes as well. With Experience Cloud and LWR, teams can use standard components for common shopping processes and develop additional functionality where needed.
Checkout and order handling also require attention. Modern B2B Commerce can create Salesforce Order records, but connections to ERP, payment, fulfilment, and inventory systems still need to work with the new implementation.
How much of the existing functionality can be reused depends on how the original store was built.
How to plan a CloudCraze migration
A CloudCraze migration usually involves reviewing the existing implementation and rebuilding parts of it for the newer platform. The work becomes easier to estimate once the team understands which functionality is still needed.
1. Review the existing store
Start with the current CloudCraze configuration. Document the product catalogue, pricing rules, custom objects, Apex code, checkout processes, and integrations. Pay particular attention to functionality that isn’t immediately visible to buyers. For example, a simple checkout screen might depend on several custom rules for pricing, inventory, or order approval.
This review should also identify features that are no longer used. There’s little benefit in rebuilding functionality the business no longer needs. A structured Salesforce audit can help identify technical dependencies and define the scope of the work.
2. Design the new commerce solution
Once the current implementation is understood, compare its requirements with the capabilities of modern B2B Commerce. Some processes can use standard Salesforce functionality. Others will need configuration or custom development.
This is also the point to review the storefront architecture, user access, licensing, and integrations. The goal is to define how the new store should work before development begins.
3. Prepare the data
Products, pricing, customer accounts, and order history need to be mapped to the target data model. This can be more complicated when the existing store uses CloudCraze-specific objects or custom relationships.
Decide which historical records are needed in the new system and which can remain in an archive. The team should also establish how data will be synchronised during migration, especially if buyers continue placing orders in the existing store.
4. Build and test the new storefront
Development can begin once the target architecture and data mappings have been agreed. Testing should cover complete buying processes, from signing in and finding products to applying the correct prices and placing orders. Integrations need particular attention. A successful checkout doesn’t necessarily mean the order has reached the ERP system or that inventory has been updated correctly.
Business users should take part in testing so that the finished store reflects how buyers and internal teams actually work. The same delivery principles apply to other Salesforce implementation projects.
5. Prepare for launch
Before switching to the new storefront, decide how to handle active carts, pending orders, and changes to product or pricing data. The cutover plan should cover the final data transfer, deployment, buyer communication, and arrangements for resolving problems after launch. A rollback or recovery approach should be agreed in advance.
For more complex stores, a phased rollout may be appropriate. After launch, monitor order processing and integrations closely until the new system is stable.
Common challenges to prepare for
Data migration is often one of the more demanding parts of the project. Product information, account relationships, and pricing mustremain consistent, especially when buyers have negotiated commercial terms.
Custom logic can also require significant work. CloudCraze-specific functionality won’t always have a direct equivalent in the newer platform, and some processes may need to be redesigned.
Integrations are another source of complexity. Payment providers, ERP systems, and product information management tools may rely on data structures or interfaces used by the existing store.
Finally, buyers and internal teams need to become familiar with the new experience. Even when the underlying business process stays the same, changes to navigation, checkout, or administration can require communication and training. Addressing these areas during planning makes it easier to estimate the migration effort and prepare for launch.
Is it time to move off CloudCraze?
If your existing store is stable and meets your requirements, there may be no immediate business reason to replace it. However, if maintenance is becoming difficult or planned improvements require extensive custom development, it’s worth evaluating modern Salesforce B2B Commerce.
Start with the current store and the changes your business expects to make. A technical assessment can help determine what can be reused, what needs rebuilding, and whether migration is justified. If you’re considering a move from CloudCraze, explore our Salesforce services to see how Spyrosoft can help assess your current implementation and plan the migration.
After launch, Salesforce managed services can help with ongoing maintenance, support, and development.
FAQ
Salesforce acquired CloudCraze in 2018 and incorporated it into its B2B Commerce portfolio. The older managed-package product is known as B2B Commerce for Visualforce. Salesforce’s newer B2B Commerce offering uses a different architecture, with LWR storefronts for new implementations. Organisations running CloudCraze should check their specific support arrangements when planning future changes.
You can build an LWR storefront as the target of a CloudCraze migration, but there is no simple one-click conversion. The work generally includes migrating commerce data, rebuilding storefront functionality, reviewing custom code, and adapting integrations. The amount of redevelopment depends on the existing implementation and its business requirements.
Migration costs depend on the size of the store, custom functionality, integrations, and the quality of existing data. A heavily customised implementation can require substantial redevelopment and testing. Before estimating the project, review which capabilities can use standard Salesforce functionality and which must be rebuilt.
Usually not. CloudCraze and modern Salesforce B2B Commerce use different commerce architectures. Products, pricing, customer access, and other data need to be mapped, while some custom logic must be rebuilt. An assessment helps establish which parts of the existing implementation are still useful and which should change.
Review the current store’s customisations, integrations, data quality, and business requirements. Identify the limitations affecting users and the improvements planned for the next few years. From there, you can compare the cost and risk of maintaining CloudCraze with a migration to the newer platform.
arrow_circle_rightContact us
Our experts will help you implement and tailor Salesforce to your needs
Our articles