Salesforce Winter ’27: What Should You Actually Be Paying Attention To?

Salesforce Winter ’27 is on its way.

If you’re responsible for Salesforce, that usually means one thing: a very large set of release notes and the slightly daunting job of working out which bits actually matter to your organisation.

The good news is that you don’t need to care about everything.

Salesforce releases new functionality three times a year, and Winter ’27 includes updates across Sales, Service, automation, analytics, security, Agentforce, Data 360, Revenue Management and more.

But the most useful way to approach a Salesforce release isn’t to ask:

“What’s new?”

It’s to ask:

“What does this mean for our Salesforce org?”

What you’ll find in this blog:

  • What Salesforce customers should be checking ahead of Winter ’27.
  • Why existing processes and integrations should come before shiny new features.
  • How to identify updates that could simplify the way you currently use Salesforce.
  • A practical way to decide what deserves action now, later or not at all.

Start with what could affect what you already have

It’s tempting to head straight for the new features.

Before you do, look at the things that could affect your existing Salesforce environment.

Salesforce’s Release Updates can include changes to performance, security, business logic and usability, and some can affect existing customisations. Salesforce specifically recommends reviewing these as part of release preparation.

Winter ’27 also gives us a good example of why this matters.

Salesforce is ending support for API traffic using incorrect instanced URLs. Shortly after an org receives Winter ’27, affected API traffic will no longer be supported, with enforcement taking place on a rolling basis.

It’s not the most exciting item in the release notes.

But if it affects one of your integrations, it’s considerably more important than a shiny feature you’ll never use.

That’s why we’d always recommend starting with impact before opportunity.

Use your sandbox for what it’s actually there for

The Winter ’27 sandbox preview began on 28 August, giving Salesforce teams an opportunity to test the release against their own configuration before production upgrades.

And that’s the important bit.

A pre-release environment can show you how a new Salesforce feature works.

Your sandbox can help you understand how that change works with your Salesforce configuration.

That means testing the things your organisation actually depends on:

  • important business processes;
  • automations and Flows;
  • integrations;
  • custom development;
  • third-party applications;
  • permissions and security;
  • critical reports and dashboards.

Salesforce recommends using the preview period to validate core business processes, custom code and third-party integrations.

The more complex your Salesforce environment is, the more important that becomes.

Then look for opportunities to simplify

Once you’ve established that nothing is likely to cause a nasty surprise, then I’d start looking at what’s new.

But with a slightly different question.

Instead of:

“What can we add?”

Try:

“Could anything new replace something we’re already doing the hard way?”

Perhaps you’ve built a custom solution because Salesforce couldn’t previously do something you needed.

Maybe your users rely on a workaround.

Perhaps you’ve got an automation that has gradually become more complicated as requirements have changed.

A new standard capability won’t always be the answer. But each Salesforce release is a useful opportunity to challenge whether the way you’re doing something today is still the best way to do it.

Sometimes the best use of a new Salesforce feature isn’t adding more to your org.

It’s allowing you to take something away.

What will your users actually notice?

Release readiness isn’t purely a technical exercise.

Some Winter ’27 changes will happen automatically when the release reaches your org, while others require an administrator to enable or configure them. Salesforce specifically recommends considering whether changes need to be communicated to users in advance.

So alongside technical testing, ask:

Will anything change the way our users work?

If the answer is yes, think about communication and adoption before the change reaches them.

A useful feature can still create frustration if nobody understands why something suddenly looks or behaves differently.

And yes, there’s plenty of AI

Unsurprisingly, Agentforce and generative AI feature heavily in Winter ’27.

Salesforce describes the release as helping businesses move AI from experimentation towards measurable business impact, with developments across Agentforce and the wider Salesforce platform.

There are some interesting capabilities in there.

But our advice remains the same:

Don’t adopt AI simply because Salesforce has made it available.

Start with the business problem.

Is there a process where AI could genuinely remove effort, improve customer experience or help people make better decisions?

Is your underlying data good enough?

Are your permissions and governance ready?

And can you actually define what success would look like?

If not, the newest feature can wait.

Adopt. Investigate. Ignore.

One of the simplest ways to make a Salesforce release manageable is to put relevant changes into three categories.

Adopt

There’s a clear use case, benefit or requirement, and you’re confident about the impact.

Investigate

It looks potentially useful, but you need to understand the implications, test it or build a stronger business case.

Ignore

It isn’t relevant to your organisation right now.

And ignore is a perfectly valid category.

The goal of release readiness isn’t to use as many new Salesforce features as possible.

It’s to make sure your organisation understands what is changing, protects the things it already relies on and takes advantage of the improvements that genuinely make Salesforce work better.

Need a second pair of eyes on Winter ’27?

If you’re unsure which Winter ’27 changes could affect your Salesforce environment, or which new functionality is actually worth investigating, Xenogenix can help you review your org and prioritise what matters.