Migration to Talkulate AI CPQ
Move quoting onto Talkulate from spreadsheets, a legacy CPQ, Salesforce Steelbrick, or your own in-house rules. We rebuild your catalog and validation logic for buyer-facing quotes on your site, starting with one product line, typically live in weeks.
This page is the Talkulate AI CPQ migration guide
For product overview, capabilities, and pricing, see the product overviewfeatures pageFAQpricing pagecomparisons.
From spreadsheets and PDF
Quotes run on Excel, Google Sheets, PDF price lists, or email. We rebuild that as a structured catalog and validation rules on your website.
What you bring
- Products and prices in any format you have today
- Compatibility notes, bundle rules, or selection spreadsheets you use today
- One presales or product owner for 2–3 working sessions
What we do
- Build a catalog the quoting engine runs against
- Encode compatibility and pricing as validation filters
- Embed on your site; leads to CRM or email
From legacy CPQ
Leaving SAP, Oracle, Conga, DealHub, or similar is a rebuild. Rules are modeled again in Talkulate’s catalog and validation layer, not imported as-is.
What you bring
- Catalog and price book exports from the old system
- Rule documentation, constraint specs, or admin guides
- Production quotes that failed validation, with notes on why
What we do
- Map SKUs, attributes, and compatibility into the new catalog
- Rebuild pricing and bundle logic as checkable rules
- Pilot on one product line, then expand
Migration from Salesforce CPQ (Steelbrick)
Common case
Steelbrick is a legacy CPQ path inside Salesforce. Same rebuild rules apply; quote objects and rules do not carry over.
What you bring
- Product and price book exports from Salesforce
- Product rule documentation, plus any QCP or PSP custom logic
- 2–3 workshops with RevOps or presales on edge cases
Is Revenue Cloud an upgrade to Steelbrick?
No. Revenue Cloud and Agentforce Revenue Management run on Salesforce Platform core with a new catalog and pricing model. Steelbrick is the legacy SBQQ managed package. Moving to Revenue Cloud is a full reimplementation: new objects, rebuilt rules, and a multi-month program if you need quote-to-cash, billing, or subscriptions on the same tenant. SBQQ configurations do not transfer.
When is Talkulate the better fit?
When your first milestone is validated buyer quotes on your website. A visitor describes the job, the flow checks compatibility against your catalog, and you receive a lead or specification in CRM. Typical go-live is weeks on one product line. Revenue Cloud fits when quote-to-cash, billing, and rep-led quoting on one Salesforce tenant is the primary goal.
Do Steelbrick rules import automatically?
No. Product rules, price rules, and custom QCP or PSP logic live in SBQQ objects and Apex. Talkulate rebuilds selection and pricing in its catalog and validation layer from exports, documentation, and workshops with your RevOps or presales team. Same rebuild model as other legacy CPQ paths on this page.
Does Salesforce CRM stay?
Yes. Talkulate replaces Steelbrick for buyer-facing quoting on your site. Leads, opportunities, and validated specifications hand off to Salesforce (or another CRM) per implementation scope. We do not write back into SBQQ Quote records.
From custom in-house quoting
Rules sit in code, internal tools, and senior staff. We need rule scan access before build can start.
What you bring
- Rule scan: source code, decision tables, internal specs, or export scripts
- Sample inputs and outputs from real customer requests
- Product owner for compatibility edge cases
What we do
- Digitize selection logic into catalog and validation filters
- Pilot on one product line with a website embed, then expand
How migration works
Same sequence for every starting point.
Audit
Products, prices, rules, and where they live today
Catalog build
Structured database for quoting (your sources stay as they are where possible)
Rules and filters
Scattered conditions become a checkable set; incompatible combinations block before pricing
Pilot
One product line on real requests
Go-live
Embed on your site; leads to CRM or email per scope
There is no one-click import from Excel or legacy CPQ. Migration means rebuild for Talkulate’s model.
What we connect
Standard migration covers your site embed, CRM handoff, and one-time catalog ingest. Ongoing ERP sync and buyer document upload are scoped separately.
Website
Included
Chat widget, iframe, or API on your domain. No CMS backend changes.
CRM
Included
Lead, specification, and conversation context to Salesforce, HubSpot, Pipedrive, and others. Connection scope is set per system in implementation.
Catalog sources
Included
One-time ingest from PIM, ERP exports, spreadsheets, SQL, REST APIs, XML, or PDF into the Talkulate catalog.
ERP / PIM sync
Optional
Ongoing sync for components, prices, and availability from your ERP or master catalog. Scoped when you need live data, not only migration ingest.
Buyer document upload
Add-on
RFQ PDFs, drawings, and spec sheets in the buyer interview. Scoped per document types and extraction rules.
Standard implementation scope
Typical first deployment on one product line. Buyer document upload and ongoing ERP sync are quoted separately.
Included at go-live
Website embed
Chat widget, iframe, or API on your domain.
Catalog build
Construction and population from your exports, spreadsheets, or APIs.
Rules for one pilot line
Business logic and validation filters for the first product line you launch.
Calibration
Tuning on real buyer requests before you expand the catalog.
Lead delivery
Email or CRM handoff with quote context. Connection scope is set per system.
Line-item fees, optional integrations, and add-ons are on the pricing page.
Scope your migration
Tell us your starting point: spreadsheets, legacy CPQ, Steelbrick, or custom rules. We map the minimum viable path and timeline.
On the call
- We identify your starting path and what data or rule access we need
- We outline pilot scope: one product line, embed, and CRM handoff
- Clear answer on calendar and team hours before build starts
Typical call: 20 minutes on your catalog and migration path plus 10 minutes Q&A.
Prefer email first? hi@r-sun.ai
Migration FAQ
Timeline, team effort, catalog scope, rule rebuild, and coexistence during the pilot.
How long does migration take, and what moves the calendar?
Between 5 days and 6 weeks for a standard path after the data audit. One product line with clean exports often lands in 3–5 weeks. Deep compatibility rules, Steelbrick QCP or PSP custom logic, multi-system CRM mapping, or buyer document upload extend the schedule. We fix the timeline in the scoping call before build starts.
How much time does our team spend on migration?
Plan for about 10–15 hours over 2–3 weeks: 2–3 workshops on selection logic and edge cases, sample quotes for calibration, and sign-off on pilot output. A RevOps lead or product owner who knows the catalog is enough for most paths. We handle catalog construction and rule encoding.
Do we need the full catalog live on day one?
No. Standard scope covers one pilot product line. You validate real buyer requests on that line, then expand SKU coverage in phases. The same phased path applies whether you start from spreadsheets, legacy CPQ, or Salesforce Steelbrick exports.
Are rules copied automatically from our old CPQ or spreadsheets?
No. Talkulate runs against a structured catalog and validation layer built for buyer-facing quotes. Product rules, bundle logic, and pricing from SAP, Steelbrick SBQQ, Excel, or in-house tools are modeled again from your exports, documentation, and workshops. There is no one-click import from any prior system.
Can we migrate when product data lives only in Excel or PDF?
Yes. One-time catalog ingest from spreadsheets, price lists, and exports is part of standard implementation when source data exists. If nothing is structured yet, we scope data structuring as explicit work before go-live.
Do we need ERP or PIM connected before launch?
No. Email or CRM handoff is enough for many first launches. Ongoing ERP or PIM sync is optional and quoted separately when you need live prices or availability, not only the one-time migration ingest described in What we connect.
Can Talkulate run alongside our current quoting system during the pilot?
Yes. Many teams launch the website embed on one product line while reps keep using the existing CPQ or spreadsheets on the rest of the catalog. Talkulate does not require ripping out the old system on day one. Cutover scope is your decision after the pilot validates output.
We are on Salesforce Steelbrick — where do we start?
Open Legacy CPQ on this page and the Steelbrick block marked Common case. Read the four questions there on Revenue Cloud, rule rebuild, and CRM handoff. For criterion-by-criterion vendor comparison, use the Steelbrick vs Talkulate comparison page.