SAP SuccessFactors Release Schedule: Dates and How to Prepare

When SAP publishes a new SAP SuccessFactors release schedule, many HR teams face the same question: which changes really affect our processes, and how should we respond?

SAP release notes may cover many modules, but it is not always necessary to review every single point. The most important task is to identify the changes that will affect the actions of employees and managers within a specific organisation, as well as system settings, access rights, reports or integrations, and to test them in a Test environment. This article explains when the team should take action, how each release phase works, and how to prepare for the update.

Quick Take

• The SAP SuccessFactors release schedule sets out a twice-yearly SAP SuccessFactors release cycle, with Preview taking place before Production.
• SAP SuccessFactors release dates are announced in advance as part of the SAP SuccessFactors release schedule, so that the team can plan the Preview review, testing and actions leading up to the Production date.
• Different changes require different actions. Some become available automatically, whilst others require a decision, additional configuration or testing.
• Preparing for a SuccessFactors release begins even before the Preview phase. You need to appoint a person in charge, identify the impact on processes and agree on the testing procedure.
• End-of-maintenance and deletion dates must be tracked separately from the usual release calendar to ensure that older features are not overlooked.

SuccessFactors Release Dates 2026

SAP SuccessFactors has two release cycles each year. The 2026 Preview and Production dates are as follows:

Dates checked against the SAP SuccessFactors release roadmap.

Production is shown as a start date because SAP’s production rollout dates can vary by time zone and the rollout may extend across more than one day.

How an SAP SuccessFactors Release Works

An SAP SuccessFactors release cycle consists of two stages: Preview and Production. The SAP SuccessFactors release schedule sets out when SAP’s Preview phase begins and when changes are rolled out to the Production system.

Preview is SAP’s official pre-production release phase. It gives customers time to use their Test environment to assess which changes are relevant to their organisation and to take the necessary action before they go live in Production.

During the Preview phase, your team can:

• check which changes affect the modules in use;
• decide whether to enable a new feature;
• test the most important processes;
• prepare to communicate the changes to staff and managers;
• make arrangements for the actions required after the Production date.

Production is the live SAP SuccessFactors environment that the team uses on a daily basis, and the scheduled Production date means that SAP will roll out the changes to the system according to the schedule. Some features become available automatically at that time, whilst others still require a pre-agreed decision, configuration or additional actions.

After the Production date, the team should test the most critical processes in the live environment, complete the planned tasks and document any issues that will require further resolution.

Universal, Opt-In, Opt-Out and Configuration-Required Changes

Being aware of the production dates alone is not enough, as each release change may require different actions. Some are implemented automatically, whilst others require decisions to be made, configuration to be carried out or tests to be performed. SAP indicates the type of action required for each change in its release documentation:

• Universal changes become available automatically as part of the release. If such a change affects the process you use, check that it works as expected for employees, managers and administrators.
• Opt-in changes need to be enabled. Before doing so, decide whether the feature is suitable for your current process, whether you have the necessary data, and who will be responsible for using it.
• Opt-out changes may be active by default according to SAP’s logic, but in certain cases they can be disabled. Specific terms and conditions are set out in the release documentation.
• Configuration-required features may require more than one enablement action. For example, you may need to update role-based permissions, workflow settings, fields, integrations or user instructions.

To ensure you can clearly track all changes and see what actions they will require from your team, categorise the relevant changes into these four groups when preparing a release impact assessment. That way, it will be clear which changes require testing, a decision or configuration, and which simply need to be monitored after the Production phase.

How to Prepare for a SuccessFactors Release

The SAP SuccessFactors release schedule gives the team a defined timeframe for release preparation and a clear sequence for planning the work.

Before Preview

Appoint a release owner – the person responsible for monitoring and initiating changes, and for making sure the organisation responds to them. This could be an HR process owner or an SAP SuccessFactors administrator. If the change relates to access, security or integrations, involve your IT colleagues in the plan as well.

Then draw up a short list:

• which SAP SuccessFactors modules you use;
• which processes within them are the most important;
• which actions by employees and managers may change;
• which reports, permissions or integrations depend on these processes;
• whether you are still using features for which SAP has announced end-of-maintenance and deletion dates.

This list will serve as a release impact assessment document, guiding you on where to start when SAP makes new content available during the Preview phase.

During Preview

During the Preview period, start with the changes that have the greatest impact on day-to-day work. Do not try to check everything in sequence: open the release notes for the relevant modules, identify the points that are specifically important for your environment, and agree on the tests.

Regression testing in the Test environment should be based on real-world scenarios. If the change affects Employee Central, check the actions relating to employee data, manager approvals, permissions and reports that the team currently uses. If the change affects another module, select scenarios specific to that module.

Record the following in the test log:

• Is this change relevant to our business?
• Is there any impact on our system?
• Is this a new feature we want to adopt?
• What changes have been made in test/preview?
• Do we want to use this feature in production?
• Update the Production system to mirror the changes made in test/preview.

Before and After Production

Before the Production date set out in the SAP SuccessFactors release schedule, finalise any changes that require configuration, communicate the changes to the team and update internal instructions if users’ actions within the system are changing.

After Production, check the most critical processes in the live environment. These may include a specific employee self-service request, a manager’s approval, a report or an integration. Record any issues identified immediately so that the team has a single, clear list for further action.

End-of-Maintenance and Deletion Dates

Release notes contain more than new features. SAP may also announce when support for older features is ending or when they will be removed. Legacy feature deprecation has practical implications: organisations need to ascertain whether an old feature is still in use, what alternative is replacing it, and what work needs to be carried out by the specified date.

If you see end-of-maintenance and deletion dates, make a note of:

• the specific feature or screen;
• the date specified by SAP;
• the processes in use that are affected;
• the newer alternative;
• the person responsible and the planned testing timeframe.

The SAP SuccessFactors release schedule helps the team plan the timing, and information on specific changes can be found in the SuccessFactors What’s New Viewer and the SAP SuccessFactors Release Center.

How Jigsaw Cloud Reviews Each Release

Each SAP SuccessFactors release brings changes across multiple modules, but understanding which updates matter to your organisation requires more than reading the release notes. At the start of each cycle in the SAP SuccessFactors release schedule, Jigsaw Cloud reviews and assesses the changes, categorises them as High, Medium or Low priority based on their potential impact and the actions required, and translates technical information into practical guidance to help customers prepare, test and take action where needed.

Where can you find this information? In the Jigsaw Cloud release knowledge base, we publish module overviews, recorded walkthrough videos, testing guidelines and additional resources. We highlight changes that may have a greater impact and indicate what actions may be required on your side.

Official SAP documentation remains the source for verifying specific conditions, deadlines and technical details, but Jigsaw Cloud’s resources can help you quickly identify where to start and which topics to discuss with your team.

Need to assess how a change will affect your system? We can arrange a 1:1 review. Ongoing SAP SuccessFactors support helps teams make release reviews part of regular system maintenance, rather than treating them as a standalone task twice a year.

Turning a Release into an Improvement Opportunity

The Preview period may not always be enough to evaluate new features in detail: sometimes the team needs to complete mandatory tests, whilst at other times it is not even clear whether the proposed change would solve a real process problem.

If the release documentation does not specify a separate deadline for a decision or configuration, such a feature can be revisited later, once production checks have been completed. If you wish to set aside more time for evaluating features, make a note next to each one:

• which current process it could replace or simplify;
• who in the organisation it would be relevant to;
• what configuration, data, communication or training would be required;
• who will make the decision on its implementation;
• how you will know whether the change has produced the desired result.

The feature adoption after a release process helps to distinguish essential release tasks from planned improvements. In this way, a useful feature does not simply remain on the list of release notes, but has a clear owner and a defined next step. If you wish to turn these decisions into an ongoing optimisation plan, release reviews and adoption can help you prioritise.

Frequently Asked Questions

What is the timeframe for SAP SuccessFactors release cycles?

SAP SuccessFactors has two main release cycles per year – H1 and H2. In each cycle, the Production phase is preceded by a Preview period, which is intended for reviewing and testing changes. SAP announces the exact dates separately, so the internal plan must be updated in line with the latest official information.

What are the SAP SuccessFactors release dates this year?

The 1H 2026 Preview began on 13 April, whilst Production began on 15 May. The 2H Preview began on 12 October, whilst Production begins on 13 November. These SuccessFactors release dates are subject to change, so please check the SAP release roadmap before planning a new cycle.

What is the difference between Preview and Production releases?

During SAP’s Preview phase, changes are made available for review before they reach the live system. The team can use its Test environment to review the latest information, carry out tests and make decisions regarding configuration. A Production release deploys changes to the Production system, so the most critical checks should be completed by this date.

Which release features become available automatically?

Universal changes become available automatically. The organisation enables opt-in features itself, whilst for opt-out changes, SAP may provide the option to disable them within a certain period. Some features only become active once configured. The conditions for each change are specified in its release documentation.

What should HR teams test before a production release?

The HR team should test real-world scenarios of the processes in use: the actions of employees and managers, permissions, reports, integrations and other activities affected by the change. Carry out tests in the Test environment and record the results, any issues found and the people responsible in a single test log.

Who should be responsible for release preparation?

The HR process owner is usually responsible for business impact and communication, whilst the SAP SuccessFactors administrator coordinates configuration and testing. Where a change relates to security, access rights or integrations, IT must be involved. A single designated release owner coordinates deadlines, decisions and next steps.

The SAP SuccessFactors release schedule helps the team to plan the review, testing and decisions on changes ahead of the production date. For organisations looking for additional expertise, Jigsaw Cloud can also provide release-review support to help assess relevant changes and plan appropriate next steps.