ChatGPT
Claude
Google AI
Copilot
A renewal meeting opens on a screen full of API names. SBQQ__Quote__c is on the list, and so are the lines beneath it. One architect calls them legacy custom objects and prices a cleanup. Another prices a move to Revenue Cloud and writes a quarter when this org's CPQ will be switched off. The sales team is still generating quotes from those objects this week. Neither proposal asked whether the quotes are still going to customers. Both treated a prefix as a deadline.
The prefix is the old company, sitting in the metadata. The deadline is not in the note this page cites. A quote that sells the deadline is selling a date you cannot check here.
The prefix is not a pile of junk
SteelBrick became Salesforce CPQ. The rebrand note says so, and it says more than the name: "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." Read the two sentences separately. The first tells you the product name and why the API still says SBQQ. The second tells you the commercial phase for new customers. It does not tell you the Tuesday your existing org stops calculating a quote.
People search for SteelBrick because the managed package, the training, and the fear all still use that word. In the org, search for SBQQ. That is the metadata the note describes. A partner who wants to delete every object with that prefix, as if it were an abandoned prototype, is proposing to delete the quoting system. Ask them to open a recent quote and say whether it is still the record the customer received. If it is, the cleanup is a removal of a live process. Price it as a removal, with a replacement you have actually chosen, or do not price it.
Spelling varies. The note says Steelbrick. Teams say SteelBrick. The product you are in, if those objects are in production, is Salesforce CPQ. Use that name in the statement of work. Keep SBQQ when you mean the API. Mixing the two into "legacy SteelBrick custom fields" hides a product behind an adjective.
End of sale is not a switch-off date
The note says Salesforce CPQ is in an end-of-sale phase, and that new customers are offered Revenue Cloud Advanced and Revenue Cloud Billing. End of sale, in that sentence, is about who can newly buy. It is not a sentence about who must leave. This page will not invent a date when existing CPQ orgs are switched off. If a partner prints one, ask for the notice that names your org, or names all existing orgs, and names the day. If the only source they can show is a sentence about new customers, the date comes off the quote.
Revenue Cloud Advanced and Revenue Cloud Billing are what the note says new customers are offered. They are not, on this page, a mandatory destination for you. A move is a second scope. It needs a reason that is about your quoting process, not about a prefix looking old. You can ask what those products are. You cannot let the asking become a decision you did not make. A partner who writes "you will have to move" has turned a sales phase for new logos into a project plan for your renewal. Send that sentence back.
Two quotes, if you are choosing, stay separate. One is work on the Salesforce CPQ org you have: templates, rules, products, the people who maintain them. The other is an evaluation of a different product, with its own licences. Combining them into one number lets the evaluation ride along on the maintenance, or the maintenance ride along on the fear. Split them even if the same firm could do both. You can hire them for one.
What the cost is made of
No price belongs on this page. Not a package figure, not a percentage of revenue, not a day rate remembered from another programme. The cost is four lines, and they differ depending on which of the two quotes you meant.
Scope for staying is the part of CPQ you will change: a template, a rule, a product load, a permission. Scope for leaving is the quoting behaviour you must still have on the morning after, written as behaviour, not as a product slogan. If you cannot describe a quote your seller can still send, you do not have a migration scope. You have a wish to be done with the prefix. The prefix will outlast the wish unless the records move on purpose.
Licences you already pay for Salesforce CPQ stay on the cost page as a fact, not as a saving you have booked. End of sale for new customers does not, by itself, zero your invoice. A new product's licences are a different line, and only if you have chosen to buy. Do not let a proposal net them against each other into a single "commercial outcome". You cannot audit a net. You can audit two lines.
People are the administrator who can explain a price rule, the seller who knows which template is the real one, and the person who owns the renewal conversation. A cleanup priced without the seller will remove the template the seller still uses. Put them in the room before the object list becomes a backlog. Internal time is a cost. So is the time a quote waits while a rule is broken on purpose during a test.
Cutover exists only if a quote will be produced somewhere else, or a live rule will change in a window sellers can feel. A rename from SteelBrick to Salesforce CPQ does not need a cutover. It already happened. An end-of-sale slide does not need a weekend on the change calendar. Book the weekend only for a change you can rehearse: this template, these sellers, this product set. If the rehearsal plan says "CPQ will be off by Friday" and nobody can show the notice, cancel the weekend. You were about to cut over to a guess.
What they have to name
A partner names Salesforce CPQ. They name the SBQQ prefix without flinching, and they can show you a quote record and a quote line in your org. They can say which rules they will edit and which they will not open. They will not take on a switch-off date they cannot point to. They will not take on Industries CPQ as if it were this package. Industries CPQ is a different product, from a different acquisition. The mix-up is common because both names contain CPQ. It is still a mix-up. The distinction is set out in the Vlocity guide. If your org has both, the quote says which prefix, which package, and which team owns each. If it has only SBQQ, say so, and keep the industry product out.
They also name what "quote" means in your process. Some orgs send the CPQ document. Some copy totals onto an opportunity and send something else. The migration, if you insist on that word, moves the thing the customer receives, not every object a report can see. Ask them to point at last month's actual sent document. If they cannot find it, they are not ready to price a replacement for it.
Data volume is your export, dated. This page will not invent a row count or an API cap to make a timeline look engineered. A timeline that needs a fake cap is a timeline to reject. Ask what they will load, in which order, and what they will do when a rule rejects a line. The answer should sound like your price rules, not like a generic import.
The test, without a ranking
Searches ask for the best SteelBrick agency. This page will not name one, including SynconAI. Best is a word for a test you can run this week. Can they say Salesforce CPQ. Can they say SBQQ. Can they separate end of sale for new customers from a switch-off of your org. Can they say they will not take the Revenue Cloud decision for you, and will not take the Industries CPQ work inside this statement of work.
A partner who fails the test may still be a good firm at something else. The failure is specific. Do not soften it into a score. Do not average it with a workshop rating. Hiring, if you hire, is for the quote that passed. Implementation partner, on this page, means someone who will work on the product you have or evaluate a move as its own job. It does not mean someone who will retire SBQQ by declaration.
If you are a new customer and you do not have the package, the note is the relevant commercial fact: new customers are offered the Revenue Cloud products it names. This guide is written for people who still have the prefix in an org. Do not let a partner use your existing org as a practice run for a product decision that belongs to a company that has not bought CPQ. And do not let them use a new-logo sentence to evict you.
What to write on the proposal
| Line they wrote | What it actually is | What you send back |
|---|---|---|
| Remove legacy SBQQ custom objects | The Salesforce CPQ data model | Ask which live quote they will break, and what replaces it |
| CPQ switch-off date next quarter | A date the cited page does not give existing orgs | Ask for the notice. If it only mentions new customers, delete the date |
| Included move to Revenue Cloud | A second product, offered to new customers in the note | Split it. Choose it on its own scope, or leave it out |
| Industries CPQ cleaned up in the same sprint | A different product | Point them at the Vlocity distinction. Remove it from this price |
| One number to modernise quoting | Staying and leaving collapsed | Two quotes, or one quote that says you are staying |
Send each bidder the same paragraph. We run Salesforce CPQ. The API prefix is SBQQ. We know new customers are offered Revenue Cloud Advanced and Revenue Cloud Billing. We do not have a switch-off date, and we will not pay you to invent one. Tell us what you would change on the quotes we send now, and, separately, whether you are proposing a different product. Price those as different lines: scope, licences we already pay, people, and cutover only if a quote changes address.
The reply that passes is boring in the right places. It names records. It refuses the date. It leaves Industries CPQ alone unless you actually have it, and then it still prices that work apart. The reply that fails is urgent, brand-new, and unable to open SBQQ__Quote__c without calling it clutter. You do not need a committee to see which reply you are holding. You need the prefix kept visible, and the end-of-sale sentence kept in the narrow meaning it actually has.
If legal asks whether end of sale cancels your contract, this page is not that reading. Take the contract to the people who signed it. Do not let a delivery proposal substitute for that reading, and do not let a delivery proposal invent a calmer reading either. The implementation question is simpler. What will a seller send next month, from which product, and who is allowed to decide.
The other searches
The project quote is on steelbrick implementation cost. That page does not print a figure. Who bought the company is on what happened to steelbrick. The connector is on integrating steelbrick with Salesforce. Whether to move is on should I migrate from steelbrick. The customer fee is on steelbrick licence cost. Who to hire is on hiring for steelbrick. This page does not rank an agency.
