# Integrating SteelBrick with Salesforce SteelBrick is Salesforce CPQ. The metadata prefix is SBQQ. The object is the quote line. End of sale is not a switch-off date. **Published:** 2025-11-14 **Canonical:** https://synconai.com/integrating-steelbrick-with-salesforce **Author:** SynconAI Architecture Team ## In short SteelBrick was renamed Salesforce CPQ. The metadata prefix is SBQQ. End of sale for new customers is not a switch-off date. A new quote design goes to Revenue Cloud. The object on the existing org is the quote line. Do not switch that org off. The failure is a quote line that does not land. A new design and the purchase are the other two pages, not this connector. ## Sources - **The ultimate guide to Salesforce product rebrands** (retrieved 2026-10-10) https://gearset.com/blog/salesforce-product-rebrands/ > Steelbrick, acquired in 2016, was renamed Salesforce CPQ, though the metadata still references its origins with SBQQ prefixes. Salesforce CPQ is now in an end-of-sale (EOS) phase as Salesforce offers new customers Revenue Cloud Advanced and Revenue Cloud Billing. ## What to take away - SteelBrick was renamed Salesforce CPQ. The metadata prefix is SBQQ. - End of sale for new customers is not a switch-off date. Do not switch an existing org off. - A new quote design goes to Revenue Cloud. The object on the current org is the quote line. - The failure is a quote line that does not land. A diagram without that failure is a poster. ## The guide A quote went to a customer with a line missing. The seller can see the quote. The line they added is not on it. In the same hour, an architect treats the metadata prefix as a deadline and proposes to switch the org off, because end of sale sounds like an ending. The seller still needs the line. End of sale for new customers is not a switch-off date. Do not switch an existing org off. The integration question is why the quote line did not land. A diagram that jumps from SteelBrick to a new cloud, and never names the line, is a poster. The prefix is still on the objects the quote uses. That prefix is how you know you are in the product the record describes. It is not a date. Write the line that failed before you write a destination. ## The app The app, for an org that already quotes, is Salesforce CPQ. The record says the rename and the commercial phase, and this page quotes it once: "Steelbrick, acquired in 2016, was renamed Salesforce CPQ, though the metadata still references its origins with SBQQ prefixes. Salesforce CPQ is now in an end-of-sale (EOS) phase as Salesforce offers new customers Revenue Cloud Advanced and Revenue Cloud Billing." The metadata prefix is SBQQ. When you are in the org, that prefix is the mark of this product. This page will not invent a full API name beyond that prefix. The record says the metadata still references its origins with SBQQ prefixes. Use the prefix to find the product. Do not delete by prefix. A prefix is not a pile of unused fields. It is how the quote is stored. End of sale for new customers is not a switch-off date. The sentence offers new customers Revenue Cloud Advanced and Revenue Cloud Billing. Read who the sentence is about. It is about new customers. It does not name your existing org, and it does not name a day when your quotes stop. A new quote design goes to Revenue Cloud. An existing org stays until you have chosen a cutover on the implementation page. This page will not carry out that cutover, and it will not pretend the connector requires it. Spell the old name as the record does when you quote it. Teams say SteelBrick. The product you open, if the prefix is in production and quotes are still going out, is Salesforce CPQ. Put that name on the diagram for the current org. Put Revenue Cloud on a separate diagram if, and only if, you are designing a new quote. Do not draw one arrow that switches the current org off on the way. ## The connector The object is the quote line. The connector is the call that places that line on the quote. If the line is not named, you do not have a connector. You have a logo for CPQ and a hope that quotes will appear. Name the quote the seller was working, and name the line that should have been on it. Those two names are the integration. A middleware box is not. A new quote design goes to Revenue Cloud. That sentence is about a design you have not built yet. It is not an instruction to point today's quote line at a different product in the middle of a customer conversation. Do not switch an existing org off so that the line has somewhere fashionable to land. The line lands on the quote in Salesforce CPQ, or it does not. Record which. This page does not name an API beyond the SBQQ prefix, a daily cap, a middleware SKU, or a price. The record does not give them. A slide that prices a connector licence from the end-of-sale sentence has mixed a sales phase for new customers with your bill. Take the fee off. The connector is the quote line arriving, or failing to arrive. Write the sentence the seller can check. This quote, this line, this result. If the sentence says "migrate SteelBrick" and never mentions a line, it is not a connector design. It is a rename treated as a project. The rename has already happened. The line is today's work. ## The architecture The architecture for the current org names Salesforce CPQ, the quote line, and the failure when the line does not land. The prefix SBQQ is how you recognise the metadata. It is not a fourth system. Revenue Cloud is not a box on this picture unless the picture is explicitly a new quote design, and even then you still name the object and the failure. This page's object remains the quote line. Do not invent a second object so the new picture looks full. | What the picture must say | What you write | | --- | --- | | System | Salesforce CPQ on the existing org. A new design goes to Revenue Cloud | | Object | The quote line | | Failure | The quote line does not land | Do not draw a switch-off date on the picture. End of sale is not that date. A box that says "CPQ ends" has invented a fact the record does not give your org. Remove the box. Leave the quote line. A guide book will not draw your quote. People search for a Salesforce SteelBrick integration guide book because the prefix looks old and they want a finished map. This page is not that book. The map is finished when a seller can point at a quote, a line, and whether the line landed. A book cannot sit with that seller. Two pictures, if you truly have two jobs. One is the existing org, the quote line, and the miss. The other is a new quote design on Revenue Cloud, which is a different page of work and does not erase the first picture. If you only have one job, draw one picture. Most meetings only have the miss. ## When the call does not land The failure is a quote line that does not land. The seller added a line, or a call was meant to add it. The quote the customer sees does not contain it. That is the call not landing. Write the quote, the line, and the time. A ticket that says SteelBrick is end of life has changed the subject. The subject is the missing line. Check the system first. Are you in the existing Salesforce CPQ org, with the SBQQ prefix on the quote you opened? If someone tested in a diagram of Revenue Cloud while the seller is still in CPQ, they tested the wrong system. Do not switch the org off to make the test match the diagram. Move the test back to the quote. Then check the object. Is the line the one the seller named? A different line landing is not success. The named line landing is success. If the named line is absent, the call did not land. Say so. Do not fill the gap with a story about end of sale. End of sale did not remove the line this morning. The call did, by failing. Do not invent an error code or a retry cap. If the quote shows a status, write the status you saw on that quote. If the line is simply missing, write that it is missing. Missing is the failure. It does not need a manufactured fault string to be real. ## An integration names three things An integration exists only when the page can name the system, the object, and what happens when the call fails. A diagram that does not name those three is a poster. The system is Salesforce CPQ for the org you already run. The object is the quote line. The failure is that the quote line does not land. A picture that only says SteelBrick, SBQQ, and Revenue Cloud has listed names. It has not said what breaks. Add the line and the failure, or take the picture down. The same test stops a switch-off. Do not switch an existing org off and call the silence an integration. Silence is not a connector. A new quote design goes to Revenue Cloud when you are designing a new quote, on the implementation page, with a cutover you have chosen. It is not what you do because a line failed today. Fix the line on the org that still quotes. Reject a connector product this page has not named. Reject a fee. Reject a full API name you invented past the SBQQ prefix. The prefix is enough to find the metadata. The line is enough to test the call. If the proposal needs more names than that, ask which sentence in the record gives them. If there is no sentence, the names come off. ## The other two pages This page is not the implementation page, and it is not the page about what happened. Whether a new quote design moves, and how an existing org stays until a tested cutover, is implementation. That work is on [the SteelBrick implementation page](/steelbrick-salesforce-cpq). The purchase, the rename, and the end-of-sale wording as history are on [what happened to SteelBrick](/what-happened-to-steelbrick). Stay here for the app, the quote line, the architecture, and the line that does not land. Do not let a missing line become a programme to leave CPQ. The line is an integration fault until you have named it and watched it fail. The decision to design quotes in Revenue Cloud is a different decision. Link the pages. Do not price them as one connector. This page will not print a price, and it will not treat end of sale as a commercial term for your current contract. A partner who opens with a guide book and a switch-off quarter has skipped the quote on the screen. Ask them to open the quote, name the line, and say whether it landed. If they cannot, they are not ready to draw Revenue Cloud. If they can, and the line is missing, you already have the incident. You do not need the book. ::: warn End of sale for new customers is not a switch-off date. Do not switch an existing org off. The metadata prefix is SBQQ. The object is the quote line. If that line does not land, that is the failure. A new quote design goes to Revenue Cloud only as a new design. ::: Write the quote, the line, and whether it was on the quote when you looked. If the line was there, there is no fault to widen into a migration. If it was not, stay on Salesforce CPQ and say the call did not land. Leave the org running. A new design, if you still want one after the line is understood, belongs on the implementation page, not in the incident channel. The prefix will still be there tomorrow. That is not a failure. The failure is a line the seller needed and the quote did not hold. Keep those apart. Then stop. ## Questions ### What is the Salesforce SteelBrick app? Salesforce CPQ, on an org that already runs it. The metadata prefix is SBQQ. End of sale for new customers is not a switch-off. A new quote design goes to Revenue Cloud. Do not switch the existing org off. ### What must a Salesforce SteelBrick architecture diagram name? The system, the object, and the failure. The system is Salesforce CPQ. The object is the quote line. The failure is a quote line that does not land. A diagram that only shows a switch-off is a poster. ### What is a SteelBrick Salesforce integration? The call that places a quote line on a quote in Salesforce CPQ, and the record of what you do when that line does not land. Leaving the org is not the integration. ### What is the SteelBrick Salesforce integration connector? The quote line, found under the SBQQ metadata prefix. This page does not invent an API name past that prefix, a daily cap, a middleware SKU, or a price. If the line is not named, there is no connector. ### Is there a Salesforce SteelBrick integration guide book? This page is not a book. The integration is your quote and your quote line. A new design is the implementation page. The purchase and the end-of-sale wording are the other page. --- 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: Revenue Cloud (https://synconai.com/salesforce-revenue-cloud-advanced).