Should I migrate from Cimulate

A merchandiser exports a week of searches that returned nothing and asks for a commerce rebuild. The export is a list of words customers typed. The rebuild would be a new storefront. Those are different projects. Cimulate is product discovery for commerce search. Search sits on a catalogue you already have. It does not become a mandate to throw the shop away. If you run B2C Commerce, that product remains the storefront it already is. This decision is about finding a product. It is not about replacing the shop that shows it.

The only sentence this page quotes from the announcement is the completion line. "Salesforce completed its acquisition of Cimulate on March 3, 2026." Strengthening search is not a cutover of the site, and it is not a till. A missed query is not fixed by a new point-of-sale project either.

#Should you migrate

Migrate a search problem you can sort, not a platform. Take ten queries from the export. A merchandiser who knows the range can usually say which box each query belongs in. A gap: the product exists in the business and is missing or invisible in the catalogue. A synonym: the product is there, and the customer used a word you did not map. A real absence: you do not sell it, and the honest result is to say so or to show the nearest thing you are willing to show. Those three boxes are the scope. "Better search" is not.

Do not migrate because the acquisition completed on 3 March 2026. The cited page does not publish a shutdown date for your storefront. You are not late, and you are not required to replatform. If you cannot export the queries, the first line of work is the export. You cannot steer a dictionary from memory.

#A sandbox is not the shop

A Salesforce sandbox copies the core org you refresh. It does not clone B2C Commerce. The storefront, the catalogue, and the orders stay in the commerce system. Refreshing a sandbox and calling the result a migrated shop will leave you without the shop. Do not migrate Cimulate, or the storefront beside it, by treating a sandbox as a clone.

Search ranking is not the catalogue. Ranking orders which products a query returns, using rules a merchandiser can name, such as a boost you already wrote for stock or a campaign. The catalogue is the set of products, categories, and attributes the storefront is allowed to show. Changing the order of results does not create a product that was never in the catalogue. A gap is a catalogue job. Calling it a ranking job hides the owner who can add the product.

#What the software is now

Salesforce owns Cimulate. The completion date is 3 March 2026. What the software is now is product discovery for commerce search. It does not replace B2C Commerce. It is not a screen this page will draw. The cited page does not publish a price. Whether a commerce-search product is on your contract is a question for that contract. The announcement can tie the work to search without putting a line on your order form. Check. If it is absent, a quote may say what is required. It may not mark it as included.

Locales are a split, not a footnote. A synonym in one language is not a synonym in another. Name the locales in the pilot. Leave the others until the first dictionary has an owner.

#The three pages

This page answers whether you should migrate, what the software is now, how ranking compares with the native catalogue, and which alternatives sit unranked.

The implementation page is Cimulate and commerce search. Use it for catalogue fields, synonyms, locales, and the queries you can export. The what-happened page is What happened to Cimulate. Use it for ownership, the date, the blank price, and the absent end date. The integration page is Integrating Cimulate with Salesforce. Use it when search must read the catalogue without becoming the catalogue. Pages, checkout, promotions, and the till stay out unless a single crossing is explicit.

#Versus the catalogue B2C Commerce already holds

A B2C Commerce catalogue already holds the products you sell online. A product has an identifier, a name, a category, and the attributes the storefront is allowed to show. Categories already group those products. Prices and availability, where you have connected them, already come from the signals you configured, on the delay you actually run. A daily feed is a different promise from a live one. The storefront already uses that catalogue to render a product page. That is the native commerce object for what you sell. It already answers whether the product exists to be shown.

Search on that storefront already returns an order of products for a query. Merchandisers already write synonyms and boosts when they have a dictionary and a rule. Ranking is that order. It is not a second catalogue. It cannot display a product the catalogue does not contain. It should not ignore a stock rule you meant to keep. A model that leans on a marketing paragraph you do not trust will surface whatever was last pasted there. The merchandiser already knows which field is the messy one. That knowledge is native operating practice. It is not something a migration installs.

Only after those descriptions does a comparison count. Cimulate is product discovery for the query. It does not replace B2C Commerce. A failed search is a gap, a synonym, or a real absence. Migrating "search" by rebuilding the shop, or by cloning a sandbox that cannot hold the catalogue, skips the object that already lists the products. Fix the catalogue when the product is missing. Fix the dictionary when the word is missing. Say so when you do not sell the thing. Do not call all three a new storefront.

#What you must not move

Do not replace B2C Commerce with this migration. Do not treat a sandbox refresh as a copy of the catalogue or the storefront. Do not treat search ranking as the catalogue. Do not fold the till, checkout, or a promotion rebuild into the same decision. A search result that must show a price from a system you name is a crossing. "Replatform while we are here" is not.

Who approves a synonym is a person, and the approval is a record. A synonym added in a workshop and lost in a slide will be added again, differently, next month. The dictionary is not a model weight you cannot read.

#Alternatives, without a rank

People search for alternatives after the acquisition, and for an alternative on AppExchange. This page has not been shown an AppExchange listing. It will not invent a listing, a rating, or a rank.

One way is to keep the synonyms and boosts you already run, and fix catalogue gaps as catalogue work. Another way is to pilot one locale's dictionary against an export of failed searches, without touching checkout. Another way is to replatform the storefront under its own quote, with no claim that search discovery required it. Another way is to evaluate a different search approach on your own criteria.

None of these is placed first. The gate is whether the brief is a query you can sort, or a new shop. A new shop fails this page's gate. It may be a different project. It is not this migration.

#A walkthrough you can finish on paper

Write ten queries. Mark each one gap, synonym, or real absence. Write the catalogue fields search may use, and the fields it must not lean on. Write the locale. Write who approves a synonym and where that approval is stored. Write whether availability is in the ranking, and how fresh the signal is. Write that a sandbox will not be treated as a clone of B2C Commerce. Write that ranking will not be treated as the catalogue. Stop if the ten queries are not marked.

Take the marks to the implementation page. Leave price and shutdown on the what-happened page. Take the boundary between search and the storefront to the integration page. If a sitemap of the whole shop appears, it belongs on a different brief.

#The sample of failed searches

Judge a pilot by whether the merchandiser agrees the marks. A gap that was actually a synonym means the dictionary was guessed. A synonym that was actually a missing product means the catalogue owner was skipped. A real absence that was filled with a random product means you promised something you do not sell. Fix the marks before you add a locale. A pack goes wrong when the title says replatform, the method is a sandbox refresh, and ranking is described as the new catalogue. Strip it back. Ten queries. Three boxes. Catalogue stays the catalogue. Shop stays the shop. No price. No end date. No screen.

The hours are the merchandiser's. Someone who knows the range has to mark the sample. Someone who owns attributes has to add a missing one. If those people are not in the brief, the migration will be priced as a model and delivered as a guess. Guessing a synonym is how the next month's export repeats the same words. Keep the dictionary as a record with an owner, in the locale you named, and leave every other locale until that owner has been right often enough that you trust the marks.

Availability is a separate mark on the same sheet. If stock should change what a query returns, name the inventory signal and how fresh it is. A daily feed is not a live promise. A ranking rule that ignores stock will recommend what you cannot ship, which is a catalogue fact the search layer does not get to overrule. Write the rule you mean to keep. A new model that quietly drops it has replaced a merchandising decision, not improved a query. The storefront still owns the product page, the price, and the checkout. Search may point at them. It does not become them.

Bring the table to the meeting. If the shop is inside the query row, split the programmes. The implementation page can price a dictionary and a catalogue gap. It cannot price a storefront a sandbox did not copy.