What your report looks like

QuoteLineTriggerHandler — ApexClass QuoteLineTriggerHandler (line 42).

The CPQ calculator API does not exist in Revenue Cloud. Pricing is evaluated by the Pricing Procedure engine, which has no drop-in equivalent for programmatic calculator invocation. Re-express the pricing intent as a Pricing Procedure. Expect this to be rewritten, not ported.

Enterprise volume tier override — 8 conditions (threshold is 5).

Condition sets this large rarely map cleanly onto a Pricing Procedure element and usually need to be decomposed by hand.

Enterprise volume tier override — Custom boolean logic, 140 characters.

Advanced conditions encode boolean expressions CPQ evaluates at runtime. Revenue Cloud has no equivalent expression slot, so each one has to be restructured.

Enterprise volume tier override — 8 conditions reference Quote.Custom_Segment__c.

This field is not on the maintained allowlist of fields with a known Revenue Cloud equivalent. It may be a custom field that needs to be recreated, or one whose semantics change.

Enterprise volume tier override — Formula of 412 characters.

CPQ formula syntax and the fields it can reach differ from Revenue Cloud's expression language. Every formula needs to be re-authored and re-tested.

Partner margin floor — Evaluation event is "On Initialization".

This evaluation point does not exist in the Revenue Cloud pricing lifecycle. The rule will need a different trigger point, which can change when it fires relative to other rules.

Partner margin floor — 2 conditions reference Quote.Custom_Partner_Tier__c.

This field is not on the maintained allowlist of fields with a known Revenue Cloud equivalent. It may be a custom field that needs to be recreated, or one whose semantics change.

Renewal uplift 3% — Looks up data from Renewal_Uplift__c.

Lookup Queries pull rule data from a custom object at runtime. Decision matrices cover the simple cases; anything conditional here is custom work.

Renewal uplift 3% — Condition references Quote.Contract_Type__c.

This field is not on the maintained allowlist of fields with a known Revenue Cloud equivalent. It may be a custom field that needs to be recreated, or one whose semantics change.

Bundle requires support SKU — 3 conditions test Quote Line.Custom_Tier__c.

This field has no confirmed Revenue Cloud equivalent, so the condition may silently stop matching.

Chassis compatibility filter — Custom boolean logic instead of All/Any.

There is no equivalent expression slot in Revenue Cloud; the logic must be restructured.

Chassis compatibility filter — Configurator rule backed by Compatibility_Matrix__c.

Bundle configuration moves to Product Configurator with a different object model, so configurator rules do not port one-to-one.

QuoteLineTrigger — ApexTrigger QuoteLineTrigger (line 1).

Triggers bound to SBQQ__ objects have no target after migration — the objects themselves are replaced. The trigger will not error; it simply never fires again. Identify the equivalent Revenue Cloud object and reimplement, or fold the logic into a Pricing Procedure.

QuoteLineTrigger — Trigger on SBQQ__QuoteLine__c, 2 SBQQ reference(s).

This is the silent-breakage case: the trigger keeps compiling and keeps being deployed, but after migration the records it expects never arrive, so it simply stops doing anything.

Enterprise volume tier override — This rule has no description.

Nobody can say what this rule is for without reverse-engineering it. That is the tribal knowledge that gets lost in a migration — and the rule most likely to be dropped or reimplemented wrong.

Enterprise volume tier override — Shares evaluation order 10 with 1 other rule(s).

When rules share an order, CPQ's tie-break is undefined. Any behaviour that depends on the current ordering is accidental and will not survive a rebuild.

Partner margin floor — This rule has no description.

Nobody can say what this rule is for without reverse-engineering it. That is the tribal knowledge that gets lost in a migration — and the rule most likely to be dropped or reimplemented wrong.

Partner margin floor — Shares evaluation order 10 with 1 other rule(s).

When rules share an order, CPQ's tie-break is undefined. Any behaviour that depends on the current ordering is accidental and will not survive a rebuild.

Legacy promo — do not delete — This rule has no description.

Nobody can say what this rule is for without reverse-engineering it. That is the tribal knowledge that gets lost in a migration — and the rule most likely to be dropped or reimplemented wrong.

Bundle requires support SKU — This rule has no description.

Validation and alert rules encode business policy. Without a description the policy exists only in someone's head.

Volume slab — hardware — Uses Slab rather than Range tiers.

Slab schedules apply each tier's rate only to the quantity within that tier. Rebuilding this as a Range schedule changes the totals, so it needs deliberate reconstruction and a numeric diff.

QuoteLineTriggerHandler — ApexClass QuoteLineTriggerHandler (line 42).

Queries against SBQQ objects compile fine but return nothing once data lives in Revenue Cloud objects. This is the classic silent-breakage case. Re-point each query at its Revenue Cloud counterpart and add assertions for empty results.

Volume slab — hardware — This schedule has no description.

Tier boundaries usually encode a commercial agreement. Undocumented, the reasoning behind the breakpoints is lost.

Volume slab — hardware — 11 tiers (threshold is 8).

Every tier boundary is a place the migrated schedule can diverge. More tiers means more numeric verification.

Quote_Approval_Routing — Flow Quote_Approval_Routing references 1 SBQQ symbol(s) across 1 line(s).

No known incompatibility matched, but this code still depends on CPQ objects and needs review before cutover.

Legacy promo — do not delete — Rule is inactive.

Inactive rules are usually dead weight, but occasionally they are seasonal. Decide explicitly whether to migrate each one rather than carrying it over by default.