The Summer '26 production upgrade is landing on June 5 and June 12 for most Salesforce orgs. Sandboxes have been on preview since May 8, which means there is no excuse for surprises on production upgrade weekend. Here is the pre-upgrade checklist every admin needs before their org flips.
The mandatory items — these break things if skipped
1. SAML migration
New SAML defaults are enforced in Summer '26. If your org uses SSO via SAML — whether Salesforce is the identity provider, the service provider, or both — you need to verify your Auth Provider configuration and test the full login flow in your Summer '26 sandbox before production upgrade. A SAML configuration that worked in Spring '26 may fail after the upgrade if the new defaults require updated settings.
Additionally, Triple DES signing for SAML SSO stops working entirely in Summer '26, as announced in Spring '26. Any SAML configuration using Triple DES as the signing algorithm breaks on upgrade regardless of whether you took any other action.
2. Apex sharing and security defaults
New Apex security behaviors are enforced. Custom Apex code that relies on specific sharing model assumptions from earlier releases needs review. If your org has custom Apex classes managing record-level access or security, test them against the Summer '26 sandbox before your production upgrade date.
3. Standard Omni-Channel retirement
Standard Omni-Channel was retired June 1. If your production org has not migrated to Enhanced Omni-Channel Routing, this is now urgent — not scheduled. Completing the migration before your production upgrade date is the priority.
See the dedicated Omni-Channel migration article for the correct four-step sequence — channel migrations must happen before the routing switch is enabled.
4. Legacy PDF generation retirement
A legacy PDF rendering behavior is retired in Summer '26. Any process that generates PDFs from Salesforce — Quote PDFs, Visualforce-generated reports, any custom PDF output — should be tested in the Summer '26 sandbox to confirm the output is correct before production upgrade. PDF rendering changes are difficult to detect until something generates incorrectly in front of a customer.
The items you should do but that will not break immediately
5. Flow Orchestration is now free
Flow Orchestration is included in Enterprise, Performance, Unlimited, and Developer editions without usage limits in Summer '26. If your org has been avoiding Flow Orchestration due to licensing cost, that barrier is gone. Evaluate whether any current multi-step approval processes or cross-object coordination workflows would benefit from rebuilding in Orchestration.
6. Review Agentforce configurations
Summer '26 changes agent lifecycle defaults for orgs running Agentforce in production. If your org has agents in production — even in early access or limited deployment — review the Summer '26 Agentforce release notes and test agent behaviour in sandbox before production upgrade.
7. Confirm your exact upgrade date
Do not assume June 5 or June 12. Your specific upgrade date depends on your Salesforce instance. Check: Setup → Company Information → Instance field. Then confirm your upgrade date at trust.salesforce.com. Some instances upgraded May 15. If your org is on one of those instances and you are reading this on June 4, your production org may already be on Summer '26.
Summer '26 is the release where "I'll check the sandbox later" becomes a problem. The June 5 wave is tomorrow. If your sandbox has been on preview since May 8 and you have not looked at it yet, today is the day.
