# Vlocity is Salesforce Industries Vlocity was acquired in 2020 and became Salesforce Industries. Industries CPQ is not Salesforce CPQ, and an industry cloud does not arrive with your data model already finished. **Published:** 2025-12-22 **Canonical:** https://synconai.com/vlocity-industry-clouds **Author:** SynconAI Architecture Team ## In short Vlocity was acquired in 2020 and became Salesforce Industries. Industries CPQ is not Salesforce CPQ from SteelBrick. An industry cloud does not remove the need for a data model. A quote that says the model arrives finished, or that mixes the two CPQ products, is pricing a confusion. Scope, licences, people, and cutover still need writing. This page will not print a number. ## Sources - **The ultimate guide to Salesforce product rebrands** (retrieved 2026-10-10) https://gearset.com/blog/salesforce-product-rebrands/ > Vlocity, acquired in 2020, became Salesforce Industries (or Industries Cloud) providing deep, industry-specific solutions. ## What to take away - Vlocity was acquired in 2020 and became Salesforce Industries, also called Industries Cloud in the note. - Industries CPQ is not Salesforce CPQ. The SBQQ product is a different acquisition. - An industry cloud does not remove the need for a data model. You still decide what the records mean. - A partner passes by naming the objects they will model and the objects, including SteelBrick CPQ, they will not take on. ## The guide A programme kickoff says the industry cloud has arrived, so the data model is handled. Assets, orders, and prices are described as included. Six months later the same room is arguing about what an asset is. One team means a thing in the field. Another means a row the billing file can recognise. A third means whatever the package created on install. Nobody wrote the choice down, because the choice was supposed to have come with the logo. In the same month a renewal for Salesforce CPQ absorbs "the industry CPQ" as a line item, on the theory that CPQ is CPQ. The logo did not attend the argument. The line item mixed two products. The quote that started the programme priced a feeling of completeness. Completeness was the part you still had to do. ## What the acquisition actually named Vlocity was acquired in 2020. The rebrand note is one sentence: "Vlocity, acquired in 2020, became Salesforce Industries (or Industries Cloud) providing deep, industry-specific solutions." Salesforce Industries, or Industries Cloud, is the name. Use it. Vlocity is the name on old statements of work, old packages, and old habits. A partner who prices a Vlocity implementation in the current year without saying Industries is pricing the habit. The sentence says the result provides deep, industry-specific solutions. That is the note's description. It is not a status report on your org. Deep does not mean your asset argument is over. Industry-specific does not mean the industry's catalogue is your catalogue, with your exceptions already modelled. Solutions does not mean the workshops can be skipped. Read the sentence as a product family. Then start the work the sentence does not do for you, which is deciding what you will store. Teams hear "industry cloud" and picture a finished vertical. What you bought is a set of capabilities aimed at an industry, sitting on the platform, still waiting for your meanings. If you skip the meanings, the capabilities will store whatever the first workshop typed. That is how six quiet months become an argument with live data in it. The argument is more expensive after the records exist. Have it while the nouns are still on a whiteboard you can throw away. ## The data model is still yours An industry cloud does not remove the need for a data model. This is the rule the kickoff broke. A model is the list of objects you will use, the relationships you will honour, and the facts you will refuse to store twice. The package can give you objects. It cannot tell you which of your legacy files is allowed to fill them, or what you call a site when the field team and the billing team disagree. Write the nouns before you ask for a build price. Customer. Account, if that is a different thing from the customer who pays. Premises or location. Asset or service point, using the word your people already say, then mapping it once. Product. Order. The commercial agreement, if it is not the order. For each noun, one sentence: what it is, what it is not, and which system is allowed to create it. If you cannot write the sentence, that noun is not in scope yet. A quote that includes it anyway is guessing, and the guess will be loaded. Do not accept "the industry model" as the sentence. Ask which industry, which package version you have, and which objects you will leave unused. Unused is a decision. Install-everything is how a data model hides. A partner who says you do not need this list, because the cloud is industry-specific, has failed the only test that matters on this page. Specific to an industry is not specific to you. Two sources of truth are the usual wreck. The industry objects hold one asset. A core custom object, built years earlier, holds another. An integration copies some fields and not others. The quote must say which object survives. If you do not know, the next phase is a decision, priced as a decision, with the people who will live with it. It is not a migration of both into a third object designed to avoid the argument. Avoidance is how you get three. ## Industries CPQ is not the other CPQ Salesforce CPQ is the product that was SteelBrick. Its metadata still carries SBQQ. Industries CPQ is not that product. The shared letters are a trap in renewal meetings and in search. A partner who cleans them up together will cross wires: the wrong rules, the wrong documents, the wrong licence conversation. If you have both, you have two scopes. If you have one, name it, and keep the other out of the statement of work. The SteelBrick path, including end of sale for new customers of that product, is a different page. Read [the SteelBrick guide](/steelbrick-salesforce-cpq) before you let a single "CPQ modernisation" cover both. End of sale on Salesforce CPQ is not a fact about Industries CPQ. Do not import it. Do not import SBQQ cleanup tasks into an Industries org that does not have them. And do not import industry objects into a SteelBrick renewal because someone said the word quote. When the quote says CPQ, make the author expand it in the first paragraph. Which package. Which prefix or which industry objects. Which team sends the document the customer signs. If they cannot expand it, they are not ready to price it. You can pause without insult. The pause is the work. ## What the cost is made of This page will not print a price, a percentage of a transformation budget, or a typical week count. Industry programmes collect those decorations. The decorations are not your design. Scope is the nouns you finished sentences for, and the processes that create and change them. It is also the nouns you parked. A scope called "the Vlocity migration" with no nouns is a blank cheque for workshops. Refuse it. A rename from Vlocity to Salesforce Industries is not, by itself, a migration. If the org already runs Industries under the old package name, say whether you are changing behaviour or changing words. Words are a glossary and a contract pass. Behaviour is a build. Do not buy the build to obtain the glossary. Licences are the industry licences you already pay. They are not a new cloud purchased so the old name can leave a slide. If the proposal adds products, each one needs a reason tied to a noun you wrote down. "The industry cloud includes it" is not a reason you can audit. Ask for the line on your contract. If the line is absent, the capability is a purchase, and the purchase waits until the model says you need it. Buying ahead of the model is how unused objects arrive. People are the ones who fought about the asset, plus the administrator who can show the object, plus the contract owner. A consultant cannot settle the asset by seniority. The field lead and the billing lead have to agree, or you have to pick an owner who will disappoint one of them on purpose. That disappointment is a decision. Put it on the page. Internal hours for that decision are a cost. Hiding them inside a partner's discovery phase makes discovery look long and the decision look like a technical delay. It is not technical yet. Cutover is the point when a process creates the new shape of record and stops creating the old one. You need a cutover if orders, assets, or prices will start life in a different object. You do not need a cutover to admit the product is called Industries. If the plan's milestone is "Vlocity is off" and the org is Industries already, the milestone is a press line. Delete it. A real cutover names the first transaction that must succeed, and the person who will check it on the day. Without that person, do not book the day. ## What they will not take on The search for the best Vlocity agency is a request for a ranking. This page will not rank SynconAI or anyone else. The test is whether they can name Salesforce Industries, name the objects they will model, and name what they will not take on. They will not take on a data model that "comes with the cloud". They will not take on Industries CPQ and Salesforce CPQ as one backlog. They will not take on every industry object the package can create. They will not take on a second system's records without a written survivor. They will not invent a regulatory sign-off. If your industry is regulated, the people who carry that duty read the design. A delivery quote does not replace them, and it should say so rather than implying a legal pass it cannot give. A reference visit to another organisation in the same industry is not the test. Their asset is not your asset, even when the package matches. Use the visit, if you take it, to hear questions. Do not copy their object list into your scope and call it due diligence. Due diligence is your nouns, in your language, with your exclusions. Hiring follows the test. An implementation partner who wants to start from a blank industry diagram and fill it in discovery is telling you the model is their first deliverable. Pay for that deliverable alone, as a decision record, before you pay for a build. If they refuse to separate them, they are pricing the build on an unsettled model. That is the kickoff failure, with invoices. ## How to read their paper | Line they wrote | What it actually is | What you send back | | --- | --- | --- | | The industry cloud includes the data model | A package, not your decisions | Ask for the noun list. Park every noun without a sentence | | Vlocity migration | Possibly a rename to Salesforce Industries, possibly a real change | Make them say which. Price words and behaviour apart | | CPQ, one workstream | Industries CPQ, Salesforce CPQ, or both, unnamed | Expand it. Split SteelBrick out. See the other guide | | All objects the package offers | Install-everything | Mark used and unused. Unused is a decision | | One figure for the vertical programme | Scope, licences, people, and cutover collapsed | Four lines. No total while the asset sentence is blank | ::: note An industry cloud does not finish your data model. Salesforce Industries can hand you objects. It cannot decide what an asset is in your organisation, or which system is allowed to create it. A quote that skips that decision is not further ahead. It is earlier than it looks. ::: Before the next pricing round, freeze one page. The industry name you bought. The five nouns in scope. The nouns out of scope. Whether Industries CPQ is even installed. Whether SBQQ is installed. Who signs the asset sentence. Hand that page to each partner and tell them the price is for that page only. A reply that adds "and the rest of the industry model" has not accepted the brief. A reply that names objects, refusals, and the four cost lines has. Keep Vlocity in the glossary if old integrations still say it. Do not keep it as the project name once you know you are in Salesforce Industries. Project names become architectures when nobody is looking. The architecture you want is small enough to point at: these objects, these owners, this thing we will not pretend is done. The acquisition was in 2020. The naming caught up. The model catches up only when you write it. ## The other searches The project quote is on [vlocity implementation cost](/vlocity-salesforce-implementation-cost). That page does not print a figure. Who bought the company is on [what happened to vlocity](/what-happened-to-vlocity). The connector is on [integrating vlocity with Salesforce](/integrating-vlocity-with-salesforce). Whether to move is on [should I migrate from vlocity](/should-i-migrate-from-vlocity). The customer fee is on [vlocity licence cost](/vlocity-salesforce-licence-cost). Who to hire is on [hiring for vlocity](/hire-vlocity-salesforce-partner). This page does not rank an agency. ## Questions ### What should a Vlocity data migration quote include? It should say Salesforce Industries, list the objects you have defined in a sentence each, and list the objects you will not use. It should say whether any record changes home, or whether the work is a rename and a glossary. It should keep Industries CPQ apart from Salesforce CPQ. Split scope, licences you already pay, people, and cutover. A blank "industry model" is not a quote. ### What is a Vlocity implementation cost made of? Scope of the nouns you have actually defined, industry licences you already pay, the people who must agree what those nouns mean, and a cutover only when a process starts writing a different object. Discovery that exists to avoid the asset decision is not a technical cost. It is the decision, unpaid and delayed. This page will not print a figure. ### Does an industry cloud remove the need for a data model? No. Vlocity became Salesforce Industries, described as industry-specific solutions. That does not decide what an asset, an order, or a price is in your organisation, or which system may create it. You still write the model. A partner who says the cloud handled it has skipped the work. ### How do you judge the best Vlocity integration agency? Do not rank agencies, including SynconAI. A partner passes if they say Salesforce Industries, name the objects they will model, refuse a finished model they did not write with you, and refuse to mix Industries CPQ with Salesforce CPQ. A same-industry reference story does not pass on its own. ### When should you hire a Vlocity consultant or implementation partner? Hire for a decision record first if the nouns are not written. Hire for a build only after that page exists, including what they will not take on. If they want one price for discovery and build while the asset sentence is blank, wait. You would be hiring the kickoff failure. ### Is vlocity owned by Salesforce? Yes. Salesforce bought Vlocity in 2020. The full account is at https://synconai.com/what-happened-to-vlocity. ### When did Salesforce acquire vlocity? 2020. ### What happened to vlocity after the Salesforce acquisition? It became Salesforce Industries. Industries CPQ is not Salesforce CPQ from SteelBrick. ### Should I migrate from vlocity to Salesforce? An industry cloud still needs a data model. Buying the vertical product does not finish the design. ### What is the vlocity licence cost, or the price Salesforce paid? The page this guide cites does not publish a purchase price or a licence fee. The licence read is at https://synconai.com/vlocity-salesforce-licence-cost. --- SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Salesforce consultancy (https://synconai.com/salesforce-consultancy).