If your proposals or your website still reference Ridge, Crest, or Summit status the way they did a year ago, it's worth checking whether that language survived March 2026 — because for most of it, it didn't. Salesforce announced the single largest overhaul of its Consulting Partner Program in more than a decade that month, and the scale of the change is genuinely unusual even against 2026's broader pattern of vendor program disruption.
Two separate, equally significant shifts happened at once:
Under the old system, tier advancement was driven by a Trailblazer Score (formerly the Partner Value Score), evaluated quarterly and reflecting accumulated points from certifications and deal volume — a system Salesforce itself has acknowledged had become administratively complex and, by its own admission, let firms accumulate points through volume even without consistently strong customer outcomes. The new competency framework is explicitly designed to correct that: fewer, more concentrated credentials, weighted toward demonstrated outcomes rather than accumulated badge count.
|
THE LINE THAT SHOULD GET EVERY CONSULTING FIRM'S ATTENTION Summit Partner status now specifically requires demonstrated Agentforce delivery competency. A firm with a deep bench of traditional Sales Cloud or Service Cloud implementation certifications — genuinely strong, legitimate expertise under the old system — is not automatically positioned to retain or reach Summit status under the new one without actively building out AI and Agentforce delivery capability. |
Salesforce structured this as a phased rollout, not an instant cutover, which is genuinely helpful — but it also means the firms that treat it as a someday problem are the ones most likely to get caught flat-footed. Existing FY26 Summit partners retain Summit status through FY27 automatically, which buys real time. But the voluntary migration window for firms aiming at Summit status runs through Q3–Q4 2026, and early applicants get preferential treatment, including extra time for case study review. Firms that wait until Q1 2027 risk default placement into the framework rather than a deliberate, prepared migration — and lose the early-mover advantage in AppExchange visibility that comes with proactively demonstrating the new competencies.
This is the detail firms most often underweight: doing nothing doesn't mean staying where you are. It means Salesforce places your firm into the new structure on its own terms, at its own timing, based on whatever data it already has — not the outcome a deliberate migration, with your best current case studies and delivery evidence actively presented, would produce. For a firm with genuinely strong Agentforce or Data Cloud delivery work that simply hasn't been formally packaged and submitted yet, default placement can mean landing at Select when a proactive migration would have supported Summit.
1. Map your current badge inventory against the new 28-competency list — identify exactly which of your team's existing certifications translate directly, and which delivery areas (especially Agentforce and Data Cloud) have a competency requirement with no current credential behind it.
2. Inventory your actual Agentforce and Data Cloud delivery work, even if it was never formally packaged as a badge-earning case study under the old system — this is the evidence a Summit migration will need.
3. Decide deliberately whether to pursue the Q3–Q4 2026 voluntary migration window, rather than letting the decision get made by default in Q1 2027.
4. Update every piece of client-facing material referencing Ridge, Crest, or Summit under the old system — a prospect checking your claimed tier against Salesforce's current partner directory and finding a mismatch is a credibility problem you don't need to create for yourself.
Consulting firms that implement across multiple Salesforce clouds — Sales Cloud, Service Cloud, Marketing Cloud — have historically tracked certifications separately by cloud, since each has carried its own credential path. The competency consolidation doesn't eliminate that complexity so much as reorganize it: a firm now needs to understand which of the 28 competencies map to which cloud-specific delivery capability, and where its team's certification mix has genuine gaps versus areas that simply need to be re-mapped and resubmitted under new names.
And for the many IT consulting firms that are Salesforce partners and Microsoft or AWS partners simultaneously — exactly the dual-stack complexity that defines the segment — this Salesforce overhaul is happening in the same twelve-month window as Microsoft's own skilling updates and Cisco's complete program replacement. Three major vendor relationships, three independent sets of 2026 changes, and one firm that has to track all of them correctly at the same time.
Most certification tracking tools answer one question: is this credential still current? That's necessary, but it's not sufficient in a year where the credential itself can be retired out from under you. AltamIQ tracks Salesforce tier and competency status alongside every other vendor partnership your firm holds, and surfaces program-level changes — a tier collapse, a badge consolidation, a new competency requirement — as they happen, so a migration window like Salesforce's Q3–Q4 2026 opportunity shows up as a decision your leadership team gets to make deliberately, not a deadline you discover after it's already closed.