Salesforce Winter '27 for Agentforce and Data 360: What Actually Changes

The Winter '27 rollout is already partly done. Sandbox preview opened 28 August 2026, the first production wave went out on 4 September, and the remaining waves land on 2 October and 9 October 2026. Your own instance's date is on Salesforce Trust — check it rather than assuming, because "your org upgrades in October" and "your org upgraded last week" lead to very different Monday mornings.

If Agentforce and Data 360 are your patch, this release reads differently from the last few. Here is how to read it, what the naming changes mean, and the two things worth doing before your wave.

Dates and features verified 13 September 2026. Release notes move; check yours before acting.

Why the Data 360 section looks thin (and isn't)

The first thing most people notice is that the Data 360 part of the Winter '27 release notes seems short. It is not that the product stopped shipping.

Data 360 no longer follows the seasonal release train. Its changes are documented under monthly release periods, not against Spring / Summer / Winter version numbers. So the seasonal document gives you a partial view by construction — whatever happened to land inside the seasonal window, and nothing else.

This is the single most important operational change for anyone who owns Data 360, and it is easy to miss because it is a documentation change rather than a feature.

What to do: treat the seasonal release notes as necessary but not sufficient for this product, and put the Data 360 monthly release-notes stream on a recurring calendar entry. If your change-management process is built around three release reviews a year, it now has a blind spot roughly nine months wide.

The naming consolidation is wider than Data Cloud

Everyone absorbed Data Cloud → Data 360 last October. Winter '27's documentation continues the pattern across the app portfolio: