Pricing
See the risk free. Pay when you need the detail.
Scanning an org and seeing how bad the migration looks costs nothing. You pay when you need the rule-by-rule breakdown, the code dependencies, and the exports.
One org, one report
FreeOne org, summary only
$0
Connect one Salesforce org and see the complexity score, inventory and top issues. Full reports are bought one at a time.
No card. Read-only access, revocable from Salesforce at any time.
Full migration report
$499
Rule-by-rule breakdown with reasoning, remediation actions grouped by workstream, and PDF, CSV, JSON and Jira export.
Re-scan this org
$149
Re-run the scan against the same org and unlock the new report. Re-scanning after you have fixed things should be an easy decision, not a second purchase.
Running migrations for clients
Paying per report stops making sense once you are scanning several orgs and re-scanning through a project.
PracticeTen client orgs, small team
$599/month
Up to 10 client orgs and 3 team members. Every report unlocked, re-scan as often as you like, no per-report charges.
$5,990/year prepaid — save 17%
FirmFifty client orgs, whole practice
$1,499/month
Up to 50 client orgs and 15 team members. Every report unlocked, unlimited re-scans, and priority support.
$14,990/year prepaid — save 17%
What every plan includes
- Read-only access — nothing is ever written to your Salesforce org
- No package to install, and no sales call to book
- Two OAuth scopes, revocable from Salesforce Setup without us
- Raw metadata discarded once the report is built
- PDF, CSV, JSON and Jira export on any paid report
Questions people ask before paying
›What breaks when migrating from Salesforce CPQ to Revenue Cloud?
Price rules using custom (advanced) conditions, lookup-query-driven rules, formula price actions, slab discount schedules, and any Apex or Flow referencing the SBQQ namespace. Triggers on CPQ objects are the most dangerous case: they keep compiling but silently stop firing, so the failure shows up later as wrong prices on real quotes.
›Is Salesforce CPQ being discontinued?
Salesforce has moved new investment to Revenue Cloud, and existing CPQ customers face a migration. The configuration can be copied; the reasoning behind each rule usually cannot, which is where migrations overrun. Stock CPQ provides no description field on price rules or product rules at all, so rule intent is undocumented by construction rather than by neglect.
›How do I assess Revenue Cloud migration readiness?
Inventory every price rule, product rule and discount schedule, then find the code that depends on them. Score each for whether it can be moved mechanically or has to be rebuilt, and group the work so it can be staffed. Doing this by hand across a large org takes days; this tool does it automatically, read-only, in a few minutes.
›Does this write anything to my Salesforce org?
No. It requests two OAuth scopes, api and refresh_token, and the Salesforce client has exactly one HTTP verb — GET. There is no create, update or delete path anywhere in it. Raw metadata is discarded once your report is generated, and you can revoke access at any time from Setup → Connected Apps OAuth Usage.
›How long does a scan take?
A few minutes for most orgs. It runs in the background, so you can close the page and come back — the report will be waiting. Larger orgs with hundreds of rules and thousands of Apex classes take longer, and scans are capped per org so they cannot exhaust your daily Salesforce API allocation.
See what you would be buying
A complete example report, with nothing held back.
Prices are in US dollars. Refunds explains what happens if a report is not what you expected, and subscriptions can be cancelled from your workspace at any time.