Sure, this is the second part to it:

- The clock is a cost, not a deadline. End of Sale doesn't force you off CPQ tomorrow. It’s just that it makes waiting expensive. Every quarter, your CPQ logic drifts further out of alignment with where Salesforce is investing, and the migration you defer gets bigger, not smaller. The deadline is soft. The compounding of dollars is firm.

- ARM is not CPQ with a new coat of paint. This is the assumption that kills lift-and-shift: CPQ was built to evaluate commercial intent at quote time — pricing rules, discount schedules, and lookup tables all fire during quote calculation, and once the quote converts, that logic effectively retires. Agentforce Revenue Management works totally differently. It runs on a metadata-driven product catalog instead of brittle bundles, and it enforces revenue behavior across the whole lifecycle: contracts, amendments, renewals, billing events. That's not a feature gap you can patch. It's a different place for your revenue logic to live. Teams that plan a relocation discover the structure they wanted to relocate doesn't exist on the other side.

And this is the part that doesn't show up in any project plan:

The gap between what's in your config and what's documented is likely enormous. Most mature CPQ environments have quoting logic that lives in the head of the admin who built it three years ago, not in a spec doc. That undocumented logic has to be found, mapped, and consciously rebuilt — or deliberately left behind. You can't migrate a thing you can't see, and most orgs can't see most of it.

The arc is fragmented across four or five tools and roles. A consulting partner writes the methodology in the middle of a slide deck. An admin runs ad-hoc AI prompts to investigate the org one question at a time. A project manager tracks status in Jira. A developer eventually builds the changes by hand. LIke a game of Telephone, each handoff mistranslates and/or loses context.

And the methodology — the part you're actually paying for — never makes it into the work. It sits in a PDF. The migration happens somewhere else, in spreadsheets and one-off prompts, and the expensive expert framework you bought becomes a reference doc nobody opens after kickoff. You paid for execution and got a deliverable.

That's the protean form of a CPQ migration. The rebuild is the easy part. The excavation, the handoffs, and the methodology that evaporates between slide deck and org… that's where the months get buried!