Salesforce Winter ’27 Release: The Biggest Changes, New Features, and Updates to Watch

Salesforce releases have followed a familiar three-release rhythm for years. But the Salesforce Winter release feels a little different this time, and not only because there are new features to explore.

The naming is changing, Agentforce is appearing across more Salesforce products, and some features are no longer waiting for the seasonal release cycle. Meanwhile, a few important changes are quietly sitting in the background, waiting for enforcement dates.

So, if you are wondering what the Salesforce Winter 27 release actually means for your org, what needs testing, and what can be ignored for now, this guide is for you. We will move through the important parts without making you read hundreds of release-note pages, because honestly, nobody has that kind of free time.

Salesforce Winter ’27: What’s New

Salesforce Winter ’27 brings several platform changes, from the growing Agentforce product naming to more frequent updates across some Salesforce products. It also includes important release updates that admins should review before enforcement.

The Release Is Changing More Than Just Features

One noticeable change is the growing Agentforce naming layer across Salesforce. Sales Cloud is now referred to as Agentforce Sales, while several other products and clouds are also being presented through the Agentforce name.

In addition to this, some products are moving away from the old seasonal-only rhythm. Sales features can arrive monthly, while Data 360 also follows a more frequent release pattern. Thus, Winter ’27 is becoming less about one giant feature drop and more about keeping track of several moving pieces.

The Dates You Should Actually Remember

Before jumping into all the shiny new features, let’s first get the dates out of the way. Because missing a Salesforce deadline and then discovering it later is not exactly a fun Tuesday.

Salesforce also recommends checking your specific instance on Trust because your actual production upgrade date depends on where your org is hosted.

Four Updates Enforce With Winter ’27

Four release updates are scheduled to enforce with the Winter ’27 release:

• Profile Filtering
• Improved Accessibility for Cards, Panels, Menus, and Containers
• Improved Accessibility for Date Pickers, Popovers, Utility Bars, and Record Headers
• Improved Accessibility for Page Headers and Modals at 200%+ Zoom

Profile Filtering is the one to pay closer attention to because it can change what profile names users can see. Users without View All Profiles can generally see their own profile name rather than other profile names.

And this is where testing with an admin can become slightly funny, because the admin may have permissions that hide the actual problem. Testing with a normal user is the better idea.

The Biggest Changes Across Salesforce

The Salesforce Winter release brings changes across Sales, Service, Marketing, Data 360, Flow, APIs, and other areas. Some are new features, some are improvements, and a few are basically Salesforce saying, “please update this thing before it becomes a problem.”

Agentforce Is Moving Deeper Into Sales

Sales Cloud is now Agentforce Sales, and the changes are going beyond a simple name update. Agentforce Engagement agents can be created in the newer Agentforce Builder, which uses Agent Script for business rules and guardrails.

Agentforce Prospecting also gets new options for scheduling agent runs, prioritizing recently engaged contacts, researching accounts outside a dedicated prospecting group, and viewing Agent Activity. These changes make sales automation more useful because the agent can work through more of the prospecting process instead of just sitting there looking impressive.

Sales Teams Get More Conversation and Forecasting Support

Einstein Conversation Insights can now surface suggested next steps after meeting transcripts become available, while Post-Meeting Voice Notes can capture details from conversations that were not transcribed.

Pipeline Forecasting also brings deal risks, methodology scores, contact insights, agent activity, and activity heatmaps into the forecasting experience. Additionally, Call Coaching expands to video calls, giving teams another way to review and improve sales conversations.

Service Gets More Practical Automation

Agentforce Service brings several smaller changes that could make everyday case handling less annoying. Case milestones can now be deleted in bulk, original case attachments can appear directly inside the case, and the enhanced case merge experience gets a refreshed setup.

Knowledge is also getting attention. Knowledge Blocks can help teams reuse content, Einstein Knowledge Creation can help draft articles, and Knowledge Similarity can compare a draft against existing articles before another almost-identical article gets created. We have all seen those duplicate articles before, and they somehow multiply.

Marketing Is Becoming More Agent-Led

Marketing Cloud Next, also referred to as Agentforce Marketing, introduces two new marketing agents focused on campaign strategy and content creation. Agentforce Marketing Goals can help determine campaign channels, content, and timing, while Agentforce Content can generate and refine marketing content.

There are also improvements around email deliverability, cross-channel personalization, language variants, landing pages, forms, and completion actions. The interesting part is that marketing automation is moving further from simply triggering a workflow toward helping decide what should happen next.

Data 360 Is Following a Different Clock

Data 360 is not following the same seasonal rhythm as many other Salesforce products. Salesforce says its changes are generally documented under monthly release periods, which means the Winter ’27 view can look lighter than expected.

One documented August change is the Snowflake Zero-Copy V2 Connector for data shares. Data Detect also expands into Data 360 data lake objects, giving teams more ways to scan and manage sensitive information across their data environment.

Automation and Development Changes Worth Watching

If your Salesforce environment contains lots of Flow, Apex, APIs, or integrations, this is probably the section where you want to stop scrolling for a minute.

Flow Builder Gets Smarter Testing

Flow Test Mode, currently in beta, combines previous testing and debugging experiences and lets teams save reusable test scenarios and mock outputs for Actions and Subflows.

Other Flow improvements include:

• Intent-based element categories.
• Smarter element search.
• Element groups for organizing larger Flows.
• Multi-record screen flows from list views and related lists.
• Save-time validation for some Create Records issues.
• User Context run options.
• A denser Flow Builder canvas with the Salesforce Cosmos theme.

These changes may sound small individually, but together they can make larger automation projects easier to build and maintain.

Apex and API Updates Are Also Part of the Release

Winter ’27 introduces API version 68.0 and several Apex improvements.

Some of the notable updates include:

• Higher Apex heap limits in supported scenarios.
• Apex integration tests that can call real HTTP endpoints.
• Apex Symbol API in beta.
• Recompiling only invalid Apex classes and triggers.
• Compiler warnings for older Apex API versions.
• Improvements to dynamic managed Apex SOQL.
• New API Catalog capabilities.

Salesforce also adds new API functionality around Composite API monitoring and Bulk API 2.0 for additional marketing objects.

User Context Makes Flow Testing More Important

A new User Context run option lets a flow enforce the permissions of the running user, regardless of how the flow was launched.

That matters because a flow that works perfectly for an admin does not automatically mean it will work for everyone else. Furthermore, testing with realistic user permissions can help teams catch access problems before users discover them first.

Some Changes Were Postponed

A few changes that people may have expected to enforce with Winter ’27 have moved.

• OAuth 2.0 username-password flow retirement: postponed to February 20, 2027.
• Update Instanced URLs in API Traffic: moved to Spring ’27.
• Adopt Authorized Email Domains: canceled and replaced by Maintain Your Email Verification Exception.
• Maintain Your Email Verification Exception: enforcement begins December 1, 2026.
• Restrict the OAuth 2.0 Device Flow to Local External Client Apps: enforcement begins November 30, 2026.

Salesforce’s release notes also point out that release updates can be postponed or canceled, so checking the current schedule before planning a migration is still important.

What Should Businesses Do Before the Release?

The easiest mistake with a Salesforce release is looking only at the new features and forgetting the existing setup.

Start With Release Updates in Setup

Open Setup, search for Release Updates, and check which updates actually apply to your org. The list can vary depending on what your organization uses, so a generic checklist found online should not be treated as your personal Salesforce roadmap.

Additionally, test the updates in a sandbox wherever possible. This is especially important for Profile Filtering and accessibility changes because your customizations may behave differently from a standard Salesforce setup.

Test With Real Users, Not Just Admins

Profile Filtering is a good example. An administrator with View All Profiles can see behavior that a standard user cannot, so simply testing the change with an admin can give you a very comfortable and very wrong answer.

Thus, use login-as or another suitable test approach and walk through the automations that depend on profile information. It takes some time, but discovering the issue after production deployment takes more time, naturally.

Build One Integration Inventory

The upcoming authentication changes should ideally be treated as one larger project instead of fifteen unrelated tasks.

Look at connected apps, OAuth flows, API endpoints, SOAP login usage, Salesforce-to-Salesforce connections, cross-org adapters, and hardcoded instance URLs. Furthermore, identify who owns each integration, because an integration without an owner tends to become everybody’s problem and nobody’s responsibility.

Do Not Ignore the Accessibility Updates

The three accessibility-related updates enforcing with Winter ’27 cover areas such as cards, containers, menus, date pickers, popovers, record headers, page headers, and modal windows at high magnification.

If your organization has custom Lightning components, this deserves actual testing. A feature can be technically available and still behave strangely inside a customized page, which is why the sandbox is sitting there waiting to be useful.

Where a Salesforce Partner Can Help

Not every organization needs outside help for a release. Some teams can review, test, and handle the changes internally without much trouble.

But if your org has old integrations, lots of custom Apex, complicated Flows, or several Salesforce products connected together, a Salesforce partner can make the preparation easier by helping identify what needs attention first.

Salesforce Services for Release Readiness

Salesforce services can cover activities such as org assessment, integration inventory, Flow and Apex review, release testing, security checks, and migration planning.

In addition to this, teams can use the release window to clean up old configurations instead of simply adding another layer on top. Otherwise, the org keeps growing like a cupboard where nobody throws anything away.

Salesforce Services for Integration Modernization

The upcoming authentication changes are a bigger concern than many of the shiny new features. Moving away from retiring authentication methods, reviewing connected apps, and preparing for external client apps can take time, especially when older integrations are involved.

A Salesforce partner can help map those dependencies and create a practical migration plan. Move forward early, because February 2027 sounds far away until suddenly it is February 2027.

Salesforce Partner Support Beyond the Release

A Salesforce partner like HIC Global Solutions can also help teams decide which Winter ’27 features are actually useful instead of enabling everything simply because it has a new label.

That means reviewing your business processes, identifying where automation can reduce manual work, and then testing the features that solve real problems. More features are not always better, and sometimes the best upgrade is the one that removes three unnecessary clicks.

Final Thoughts

The Salesforce Winter 27 release brings a mix of Agentforce improvements, automation updates, service enhancements, marketing capabilities, Flow changes, and development improvements. Some are immediately useful, while others need a little testing before they make sense for your organization.

For teams planning the Salesforce Winter release 27 transition, the main thing is not to panic and try to test everything. Start with what your org actually uses, check the enforcement dates, and then work through the changes one by one.

If your roadmap includes larger modernization work, Salesforce services can also support the assessment, development, integration, and migration work around the release. A Salesforce partner can be especially useful when the org has years of customizations hiding behind what looks like one simple update.

The Salesforce Winter release 2027 will eventually become the normal Salesforce environment, just like every previous release did. The difference is what you do before that happens. A little testing now can save a surprisingly large amount of “why did this suddenly stop working?” later.