# Boomi SuccessFactors Integrations: What Changes in 2027 and When to Move to SAP Integration Suite

> See which Boomi SuccessFactors integrations need OAuth, which APIs are changing, and when to keep Boomi or evaluate SAP Integration Suite.

Canonical: https://www.aifalabs.com/hub/boomi-successfactors-integrations
Publisher: AiFA Labs (https://www.aifalabs.com)

SAP has moved the main deadline for Basic Authentication on SAP SuccessFactors APIs. On June 12, 2026, SAP changed the deletion date from November 20, 2026 to November 12, 2027, and it plans to turn Basic Authentication off by default in the 1H 2027 release, with an opt-in for migration, before disabling it completely in 2H 2027. One related change comes sooner: the /oauth/idp endpoint that some setups use to generate SAML assertions is scheduled for deletion on May 14, 2027. SAP has no known date for ending Boomi support. For each affected integration, the immediate question is how to replace Basic Authentication. That review is also an opportunity to identify integrations where an API, packaged flow or architecture change makes a broader modernisation worth evaluating. At AiFA Labs we help SAP customers answer that for every integration in the estate. This guide is for HRIS and SuccessFactors integration leads, SAP integration architects and HR technology owners. It sets out what is retiring and when, which integrations are affected and who owns each, how to find them, what each option involves, and a plan built around SAP's published milestones.

## Key Takeaways

- Boomi SuccessFactors integrations on Basic Authentication face deletion on November 12, 2027, with Basic Authentication off by default from the 1H 2027 release.
- May 14, 2027 is the deletion date for /oauth/idp; Employee Central SFAPI entities other than CompoundEmployee are deprecated, with no decommissioning date planned yet.
- SAP KBA 2978172 confirms that updating the Boomi SuccessFactors connector leaves existing connections on Basic Authentication until each one is reconfigured.
- Per SAP KBA 3156202, customers switch their own Boomi processes, SAP updates its packaged flows, and one packaged payroll flow will not support OAuth.
- SAP has no known end date for Boomi support, so an integration that only needs an OAuth switch can stay on Boomi.
- Start now: search the SuccessFactors API Audit Log for Basic headers, check every Boomi connection, and tag each integration by API type.

## What Is Retiring in SAP SuccessFactors, and When?

Five separate SAP changes touch Boomi SuccessFactors integrations. Four have published dates between November 2026 and November 2027, and one, the SFAPI deprecation, has no decommissioning date yet. Keeping them apart matters, because each one has a different scope and usually a different owner.

What is retiring, and when

| What is retiring | What it affects | Date | Usually owned by (our reading) | SAP source |
| --- | --- | --- | --- | --- |
| Basic Authentication and direct third-party corporate identity provider integration | User sign-in and single sign-on wired directly from a corporate identity provider | Deletion November 13, 2026 | Identity team | SAP KBA 3472405 |
| Basic Authentication for Document Management with OpenText | The OpenText document integration only | Deletion November 20, 2026 | OpenText integration owner | SAP KBA 3746585 |
| OAuth IdP API (/oauth/idp) | Setups that generate SAML assertions by sending a private key to SuccessFactors | Deletion May 14, 2027 | Integration team | SAP What's New Viewer |
| Employee Central SFAPI entities, except CompoundEmployee | Integrations that read or write Employee Central data through SOAP SFAPI entities | Deprecated. Decommissioning date not planned yet. OData recommended | Integration team | SAP KBA 3043111 |
| Basic Authentication for SuccessFactors APIs | Any OData or SFAPI call sent with a username and password, including CompoundEmployee | Off by default in 1H 2027 with an opt-in for migration, fully disabled in 2H 2027, deletion November 12, 2027 | Integration team | SAP What's New Viewer |

The API date has already moved once, and SAP describes future dates as subject to change. Some SAP knowledge base articles, including the OAuth Authentication FAQ, still show the earlier November 20, 2026 date, so treat the What's New Viewer entry for Basic Authentication for APIs as the current reference. For planning, the 1H 2027 release matters more than the final deletion date. Basic Authentication stops being available by default at that release, so we treat it as the practical deadline.

The API change reaches both OData and SFAPI, including the CompoundEmployee API. End of maintenance passed on June 2, 2023, SAP first announced the sunset in the 2H 2020 release, and OAuth has been available for SFAPI since the 1H 2021 release.

The SFAPI change has no date yet but still deserves a plan, because an OAuth switch alone does not address it. SAP states that SFAPI entities other than CompoundEmployee have already been deprecated and will be decommissioned, with no date planned yet, and its training tells customers to use OData for new development and consider moving legacy integrations to OData. CompoundEmployee stays: SAP describes it as the only SFAPI entity that will not be deprecated, and it follows the same authentication schedule as every other API call. The /oauth/idp endpoint, which SAP considers unsafe because it requires users to pass private keys through an API call, is scheduled for deletion on May 14, 2027 as well.

### Why the November 2026 Dates Still Matter

Two dates remain in November 2026, and neither is the general API deadline. SAP's KBA on the deprecation of Basic Authentication and third-party corporate identity provider direct integration with SAP SuccessFactors HCM suite gives November 13, 2026 as the deletion date, with a move to Identity Authentication in SAP Cloud Identity Services as the fix. That change concerns sign-in and the way a corporate identity provider connects to SuccessFactors, and it usually sits with the identity team. Separately, Basic Authentication for the Document Management integration with OpenText is scheduled for deletion on November 20, 2026, and applies to that integration only. Give both a named owner now, then plan the Boomi work against the 2027 milestones.

## Is SAP Ending Support for Boomi?

No. SAP's support article on the question says "There are currently no plans to stop supporting Dell Boomi", and that there is no known date for ending support for Boomi SuccessFactors customers. Boomi accounts were sold together with SuccessFactors products, which is how many HR integrations came to run there. The 2027 changes apply to how those integrations authenticate and which APIs they call, so each integration can be decided on its own merits.

## Which Boomi SuccessFactors Integrations Are Affected?

Every Boomi connection to SuccessFactors that authenticates with a username and password is affected, whoever built it. Processes that reach SuccessFactors through Boomi's HTTP connector need extra work, because SAP notes that this OAuth setup is supported only with the SuccessFactors connector. Operations built on Employee Central SFAPI entities other than CompoundEmployee also need an OData plan, whatever authentication they use, because those entities are deprecated.

Updating the Boomi connector does not switch existing connections to OAuth. OAuth support for OData calls arrived in the Boomi SuccessFactors connector with the 1H 2021 release, but SAP notes that after the connector update an existing connection would not change, Basic Authentication would still be working for existing integrations, and the OAuth fields would simply become visible. A connector version number alone does not confirm which authentication a connection uses, so each connection has to be checked and reconfigured individually.

Who does the reconfiguring depends on who owns the integration, and SAP KBA 3156202 draws that line, as the next two sections set out.

### Customer-Built Boomi Processes

SAP classifies customer-built integrations running on Boomi with the SuccessFactors connector as "Ready for Migration". The switch is yours to make, using the steps in SAP KBA 2978172, and nothing further is needed from SAP. This group is often the largest, so list each process and its owner early.

### SAP-Packaged Boomi Integrations

For integrations SAP delivered on Boomi, the adopted integration flow must be made available by SAP first, and SAP states that for all standard integrations provided by SAP where SFAPI or CompoundEmployee API entities are used, SAP is responsible for changing them from basic authentication to OAuth. The customer's part is to confirm that the updated version is what actually runs. For several packaged integrations, SAP's instruction is to get the latest integration flow and follow the integration guide to switch to OAuth2.

Two packaged flows need separate attention. SAP lists the EC Payroll (HR Standard) to EC Employee Confirmation v5.0 package as "Not ready for Migration" and says it is planned to be deprecated and won't be supporting OAuth, so its replacement needs to be in place before Basic Authentication is turned off by default in the 1H 2027 release. SAP also labels the Boomi EC to EC Payroll Employee Replication v8.0 package a deprecated packaged integration, so plan its replacement within the same payroll workstream.

SAP's migration status by Boomi integration type

| Boomi integration type | SAP status | What SAP says to do | Who acts (our reading) |
| --- | --- | --- | --- |
| Customer-built processes using the SuccessFactors connector (SOAP or OData) | Ready for Migration (KBA 3156202) | Switch to OAuth following KBA 2978172 | Customer |
| Recruiting with Third Party Assessment Vendor (People Answers), Employee Central with Benefitfocus, Employee Central with Thomsons Online Benefits, SuccessFactors with Kronos, Employee Central with WorkForce Software | Ready for Migration (KBA 3156202) | Get the latest integration flow and follow the integration guide to switch to OAuth2 | SAP provides the updated flow, customer confirms it is deployed |
| EC Push Event | Ready for Migration (KBA 3156202) | Get the latest integration flow and follow the Enabling Push Replication instructions | SAP provides the updated flow, customer confirms it is deployed |
| EC Payroll (HR Standard) to EC Employee Confirmation v5.0 | Not ready for Migration (KBA 3156202) | No OAuth path: SAP plans to deprecate the package and it won't support OAuth | Customer plans a replacement and asks SAP support for interim guidance |
| EC to EC Payroll Employee Replication v8.0 (Boomi) | Labelled deprecated (KBA 2827603) | No instruction given beyond the deprecated label | Customer plans a replacement |

## How to Find Every Integration Still Using Basic Authentication

Check both ends. The SuccessFactors tenant shows which calls arrive with Basic Authentication, and the Boomi account shows which connections are configured to send them. Either list on its own misses things, because one connection can feed many processes and one process can carry different credentials in each environment.

1. Read the SuccessFactors API Audit Log. SAP's guidance is direct: if the authorization header says Basic, the API call uses Basic Authentication and should be changed. The same log records the IP address, user agent and process name, which is how a call is traced back to a specific Boomi runtime. 2. Check each Boomi SuccessFactors connection. SAP documents how to check whether a Boomi SuccessFactors Partner connection uses HTTP Basic or OAuth 2.0 authentication. For a handful of connections, this is quick to do by hand. 3. Script the check for a large estate. The Boomi Platform API makes the account searchable. The ComponentMetadata object identifies connector connections and operations through a subType field that holds the internal connector ID. The Component object returns each component's configuration as XML, with password-type fields masked using a cryptographic hash, so a password stays unreadable while its presence can still be detected. The ComponentReference object lists the components that use a connection, but it returns the immediate reference only, one level deep, so nested processes need repeated queries.

4. Check environment extensions. Credentials are often set per environment rather than on the component itself. The EnvironmentExtensions object returns extension values except for encrypted values and flags where an encrypted value has been set, which can reveal credentials on connections that look empty in the component view. 5. Reconcile and tag. Match audit log callers to Boomi connections, then tag each integration as customer-built or SAP-packaged, as SFAPI entity, CompoundEmployee or OData, and note any use of /oauth/idp. Those tags drive every decision in the next two sections.

![Find Basic Authentication from both ends: SuccessFactors API Audit Log and Boomi component APIs reconciled into one inventory](https://www.aifalabs.com/hub/figures/boomi-successfactors-integrations/figure-1.png)

## What Does Fixing in Place on Boomi Involve?

Fixing in place means moving each Boomi SuccessFactors connection to OAuth 2.0 with a SAML bearer assertion. SAP's step-by-step guidance for the Boomi SuccessFactors Partner connector has three parts.

1. Register Boomi as an OAuth client in SuccessFactors under Manage OAuth2 Client Applications, using the Boomi platform address SAP specifies as the application URL, then download the X.509 certificate and generate the API key. 2. Update the Boomi connection with the OAuth client details. 3. Decide how the SAML assertion is produced. The connector can generate it at runtime from the client ID and private key, or an external assertion can be supplied when you do not want the private key held in the connector.

Add these to the plan as well. Produce assertions in the connector or through Identity Authentication, which SAP names as a replacement for /oauth/idp, rather than through the retiring endpoint. Give certificate rotation its own procedure: an OAuth client registration can be edited, but changing or regenerating its certificate invalidates the existing client configurations until each one is updated. And make sure a local Boomi runtime is allowlisted in SuccessFactors, or its API operations will not go through.

Fixing in place has a limit for operations built on Employee Central SFAPI entities other than CompoundEmployee. Those entities are deprecated, and an OAuth switch does not change that, so they will need to move to OData before SAP decommissions them. Because Boomi operations are imported against a specific SuccessFactors entity, moving an operation from an SFAPI entity to an OData entity means importing a new operation, building a new profile and remapping the data, which is close to rebuilding the integration. That rebuild can stay on Boomi or move to SAP Integration Suite.

## When Is Moving to SAP Integration Suite Worth Evaluating?

If authentication is the only issue and the existing integration is stable, keeping it on Boomi may be the lowest-disruption option. A move to SAP Integration Suite becomes worth evaluating when the integration also requires an API replacement, major logic changes, replacement of deprecated SAP content, or alignment with a broader SAP BTP strategy. SAP maintains HR integration content on SAP Integration Suite, including versions of several vendor flows, which is useful context for that evaluation.

A native SAP route for the same scenario is another reason to compare options. Where integration logic has become difficult to document or support over time, a rebuild can also create an opportunity to simplify the design and establish clear documentation for future maintenance.

### Where SAP Already Offers a Native Route

SAP now covers the most common HR scenarios with native options:

- Employee Central to Employee Central Payroll. SAP states that point-to-point replication, without the use of a middleware, is now available for this integration, and its training describes payroll-relevant data being replicated to Employee Central Payroll via point-to-point integration.
- Employee Central to SAP S/4HANA or SAP ERP HCM. Custom replication logic can give way to SAP's standard package. It runs through SAP Cloud Integration, which supplies lean middleware content for connectivity such as authentication, session handling and protocol conversion, while the integration is based on the Business Integration Builder in the back end.
- Cost centres from SAP S/4HANA 2025. For new implementations and upgrades, SAP strongly recommends SAP Master Data Integration for replicating cost centres to Employee Central.
- Simple scheduled file and data jobs. The SuccessFactors Integration Center enables administrators to build, run, schedule, and monitor simple integrations, including outbound files to SFTP.
- Third-party benefits, time and workforce vendors. SAP's secure-authentication guidance lists SAP Integration Suite versions of the vendor integrations in the table above next to their Boomi versions.

Keep on Boomi or move, by integration type

| Boomi integration today | Near-term action | Longer-term route | Why |
| --- | --- | --- | --- |
| Custom process on OData entities | Switch the connection to OAuth before the 1H 2027 release | Keep on Boomi, and evaluate SAP Integration Suite only if a major change comes up | Only authentication changes, and the logic stays valid |
| Custom process on SFAPI entities other than CompoundEmployee | Switch to OAuth before the 1H 2027 release and plan the OData rebuild | Rebuild on OData and evaluate the best runtime for the organisation's architecture, support model and SAP roadmap, including Boomi or SAP Integration Suite | These SFAPI entities are deprecated, with no decommissioning date planned yet |
| Custom process on CompoundEmployee | Switch to OAuth before the 1H 2027 release | Keep, or compare with SAP's standard Employee Central replication content | CompoundEmployee is not deprecated |
| Any connection that generates assertions through /oauth/idp | Move assertion generation to the connector or Identity Authentication before May 14, 2027 | No change to the integration logic | /oauth/idp is being deleted |
| SAP-packaged vendor flow on Boomi, for example Benefitfocus or Kronos | Deploy SAP's latest flow and switch to OAuth2 | Keep, or evaluate the SAP Integration Suite version at the next change | SAP lists both a Boomi and an SAP Integration Suite version |
| EC Payroll (HR Standard) to EC Employee Confirmation v5.0 | Ask SAP support for interim guidance and have the replacement ready before the 1H 2027 release | Replace | SAP plans deprecation and no OAuth support |
| EC to EC Payroll Employee Replication v8.0 (Boomi) | Confirm which replication method is live and plan the replacement | Point-to-point replication (SAP scopes it to employee master data, absences and time valuation results) | The package is labelled deprecated and SAP provides replication without middleware |
| Simple scheduled Boomi export that calls SuccessFactors APIs | Switch to OAuth before the 1H 2027 release | Keep on Boomi, or use Integration Center | SAP's built-in tool covers simple scheduled integrations |

![Keep on Boomi or move? A decision tree for each Boomi integration that calls SuccessFactors](https://www.aifalabs.com/hub/figures/boomi-successfactors-integrations/figure-2.png)

### What SAP Integration Suite Adds for HR Integrations

For the integrations that do move, a few differences matter most to HR teams.

Credentials sit outside the integration logic. In SAP Cloud Integration, authentication details are maintained centrally and only referenced by integration flows, so the flows do not need to store secret data, such as passwords. OAuth2 SAML Bearer Assertion is documented for SAP Cloud Integration connecting to SuccessFactors OData and SFAPI, and the SuccessFactors adapters support snapshot-based pagination for consistent large reads.

SAP Cloud ALM also collects Integration Center exceptions and exceptions for integrations via the OData API from SuccessFactors, alongside message errors and failed integration flows in Cloud Integration, so an HR integration failure surfaces in the same operations tool from either side.

Execution can stay private where it must. Edge Integration Cell is a hybrid integration runtime that lets teams design and monitor content in the cloud while running it in their own managed private landscape. This can support architectures where private-landscape execution is required for security, compliance or data-residency reasons, subject to the organisation's specific requirements.

SAP reports more than 4,000 prebuilt integration flows and over 250 connectors in SAP Integration Suite, and SAP's clean core guidance recommends using SAP BTP to add functionality while keeping the ERP foundation intact. SAP Integration Suite runs on SAP BTP.

## A Plan Built Around SAP's 2027 Milestones

Sequence the work by the earliest date that applies to each integration, and leave room for SAP to move dates again. Payroll cycles and year-end processing limit cutover windows, so we schedule the OAuth work well ahead of the 1H 2027 release.

Phase 1: inventory both ends, now. Build one reconciled list of integrations, each with its caller, Boomi connection, owner and API type, and confirm who owns the November 2026 sign-in and OpenText changes.

Phase 2: classify, now. Give every integration a disposition from the decision table above: fix in place on Boomi, deploy SAP's updated package, rebuild on OData, move to a native SAP route, or rebuild on SAP Integration Suite.

Phase 3: prepare for the 1H 2027 release and May 14, 2027. Switch connections to OAuth, move assertion generation off /oauth/idp, replace the v5.0 package, and schedule OData rebuilds for SFAPI entity operations, testing in a non-production instance first. SAP applies product releases to production 4 to 5 weeks after deploying them to preview, so test against the 1H 2027 preview before it reaches production.

Phase 4: finish OData rebuilds and any planned moves during 2H 2027. Confirm every connection is on OAuth before Basic Authentication is fully disabled, and do not rely on SAP's opt-in for migration unless SAP confirms how it applies to your tenant. Move the integrations you chose to relocate in waves by data domain, so payroll, time and benefits each cut over as a unit, with parallel runs wherever payroll accuracy is at stake.

Phase 5: close out by November 12, 2027. Deactivate the API users that relied on Basic Authentication, record certificate rotation dates, and confirm monitoring is live for every new route.

![A plan built around SAP's 2027 milestones: five steps sequenced by the earliest date that applies to each integration](https://www.aifalabs.com/hub/figures/boomi-successfactors-integrations/figure-3.png)

## How We Help Teams Make This Decision

We are an SAP PartnerEdge partner, and we use SASA, our AI platform for the SAP delivery lifecycle, to speed up documentation and rebuilds. SASA has its own SAP partner solution page. Our SAP BTP practice migrates iPaaS platforms such as MuleSoft and Boomi to SAP BTP, and our hub includes a video demonstration of a Boomi to SAP BTP iFlow migration. In one AiFA Labs client engagement, a MuleSoft to SAP BTP Integration Suite migration involving 120 interfaces, our team reported 35% migration cost savings. We start from your SuccessFactors audit log and your Boomi account, and where an OAuth switch on Boomi is enough, that is what we recommend.

For these milestones, we can build the reconciled inventory, a disposition for every integration, the OAuth and OData work list, and a wave plan for any moves. We then support whichever path each integration needs: the OAuth switch on Boomi, the OData rebuild, or a move to SAP Integration Suite.

Talk to our SAP integration team and we will show you which of your Boomi SuccessFactors integrations need attention first.

## About the Author

Sagar Chakraborty is Director of Artificial Intelligence Innovations and Strategy at AiFA Labs, where he leads the team building SASA (SAP AI SDLC Assist), the company's AI platform for the SAP delivery lifecycle. He holds a PhD and a Master of Technology in Artificial Intelligence from IIT Jodhpur, completed a management programme at IIM Calcutta, holds two patents, and has spent more than ten years building AI products. Read Sagar Chakraborty's full profile or connect with Sagar on LinkedIn.

## Frequently Asked Questions

### Are Report Center SFTP exports affected by the Basic Authentication deletion?

No. SAP states that the change applies specifically to API access within the SAP SuccessFactors HCM Suite and does not affect internal platform services used for report scheduling, so scheduled report exports to SFTP keep running. Integrations that call the APIs to pull the same data are still in scope.

### Can one Boomi OAuth connection serve both SFAPI and OData?

Yes. SAP's Boomi guidance says the same SuccessFactors connection created for OAuth can be used for both SFAPI and OData APIs. You then have fewer client registrations and fewer certificates to rotate.

### What happens to Identity Provisioning syncs that use Basic Authentication?

They move to a different API. SAP explains that provisioning between Identity Provisioning and SuccessFactors used OData with Basic Authentication, and that customers can now use new SCIM APIs with a certificate-based approach. This usually sits with the same identity team that owns the November 13, 2026 sign-in change.

### Can SAP's Migration Assessment tool analyse a Boomi estate?

No. SAP's Migration Assessment reads SAP Process Orchestration 7.31 SP28, 7.40 SP23 and 7.50 SP06 and above. For a Boomi source, the inventory comes from the two-sided method above, which our team can run with you. SAP's Integration Solution Advisory Methodology is open to non-SAP integration technologies, so it still works for designing the target estate.

### Do SAP cloud credits apply when moving from Boomi?

Possibly. SAP's migration page offers cloud credits for moving to SAP Integration Suite, with more for select third-party solutions, but it does not name which solutions qualify and notes that additional terms may apply. Ask your SAP account executive before the business case is finalised.

## References

- SAP SE. Deprecation of Basic Authentication for APIs. SAP SuccessFactors Release Information, What's New Viewer. SAP Help Portal, accessed September 2026.
- SAP SE. Registering Your OAuth2 Client Application. SAP SuccessFactors API Reference Guide (OData V2). SAP Help Portal, accessed September 2026.
- SAP SE. Deprecation of OAuth IdP API /oauth/idp. SAP SuccessFactors Release Information, What's New Viewer. SAP Help Portal, accessed September 2026.
- SAP SE. OAuth Authentication: Frequently Asked Questions (FAQ). Knowledge Base Article 3146449. SAP Support Portal, accessed September 2026.
- SAP SE. Potential Impacts of Basic Authentication Deprecation for Report Center SFTP Schedules. Knowledge Base Article 3724884. SAP Support Portal, accessed September 2026.
- SAP SE. [1H 2021] SFAPI Supports OAuth, SAP SuccessFactors Integrations. Knowledge Base Article 3043111. SAP Support Portal, accessed September 2026.
- SAP SE. What Are the Available APIs for SuccessFactors? Knowledge Base Article 2613670. SAP Support Portal, accessed September 2026.
- SAP SE. Describing OData API and the API Center. SAP SuccessFactors Platform Advanced and Talent Intelligence Hub Academy. SAP Learning, accessed September 2026.
- SAP SE. 2H 2022: Deprecation of OAuth IdP API /oauth/idp. Knowledge Base Article 3239495. SAP Support Portal, accessed September 2026.
- SAP SE. Deprecation of Basic Authentication for Integration with Document Management and OpenText. Knowledge Base Article 3746585. SAP Support Portal, accessed September 2026.
- SAP SE. Deprecation of Basic Authentication and Third-Party Corporate Identity Provider (IdP) Direct Integration with SAP SuccessFactors HCM Suite. Knowledge Base Article 3472405. SAP Support Portal, accessed September 2026.
- SAP SE. Dell Boomi Support End Date. Knowledge Base Article 2871114. SAP Support Portal, accessed September 2026.
- SAP SE. How to Request Access to Boomi Account. Knowledge Base Article 2080177. SAP Support Portal, accessed September 2026.
- SAP SE. How to Use OAuth 2.0 Authentication in Boomi to Connect to SuccessFactors (SuccessFactors Partner Connector). Knowledge Base Article 2978172. SAP Support Portal, accessed September 2026.
- SAP SE. SAP SuccessFactors Integrations Supporting a Secure Authentication Mechanism. Knowledge Base Article 3156202. SAP Support Portal, accessed September 2026.
- SAP SE. MAX_LENGTH_EXCEEDED Caused by Deprecated Boomi Packaged Integration: EC to EC Payroll, Boomi Employee Replication v8.0. Knowledge Base Article 2827603. SAP Support Portal, accessed September 2026.
- SAP SE. How to Use SuccessFactors API Audit Log to Determine Authentication Methods Used in Your Environment. Knowledge Base Article 3138533. SAP Support Portal, accessed September 2026.
- SAP SE. How to Check Which Authentication Is Used in the Boomi Connector: SuccessFactors Partner Connection? Knowledge Base Article 3345979. SAP Support Portal, accessed September 2026.
- SAP SE. Connectivity Between SuccessFactors and Local Atom. Knowledge Base Article 2440323. SAP Support Portal, accessed September 2026.
- SAP SE. Exploring Appendix C. Implementing SAP SuccessFactors Integration with Employee Central Payroll. SAP Learning, accessed September 2026.
- SAP SE. Implementing SAP SuccessFactors Employee Central Integration with Employee Central Payroll. SAP Learning, accessed September 2026.
- SAP SE. Preparing Systems for Replication from SAP SuccessFactors Employee Central to SAP S/4HANA. SAP Learning, accessed September 2026.
- SAP SE. Replicating Cost Centers from SAP S/4HANA 2025 to SuccessFactors Employee Central: Choosing Between MDI and Cloud Integration (CPI). Knowledge Base Article 3727053. SAP Support Portal, accessed September 2026.
- SAP SE. Explore the Integration Center. SAP SuccessFactors Platform Advanced and Talent Intelligence Hub Academy. SAP Learning, accessed September 2026.
- SAP SE. Preparing Credentials for Cloud Integration. SAP Learning, accessed September 2026.
- SAP SE. How to Use OAuth2 SAML Bearer Assertion in SAP Cloud Integration Connecting with SAP SuccessFactors (ODATA and SFAPI). Knowledge Base Article 3043427. SAP Support Portal, accessed September 2026.
- SAP SE. How to Enable Snapshot-Based Pagination in SuccessFactors Adapters in CPI. Knowledge Base Article 2830254. SAP Support Portal, accessed September 2026.
- SAP SE. SAP Cloud ALM Integration and Exception Monitoring: SAP SuccessFactors. SAP Support Portal, accessed September 2026.
- SAP SE. SAP Cloud ALM Integration and Exception Monitoring: SAP Integration Suite (Cloud Integration). SAP Support Portal, accessed September 2026.
- SAP SE. Outlining SAP Integration Suite Capabilities. SAP Learning, accessed September 2026.
- Misra, Sid. SAP Recognized as a Six-Time Leader in the 2026 Gartner Magic Quadrant for Integration Platform as a Service. SAP News Center, March 19, 2026.
- SAP SE. What Is a Clean Core? sap.com, accessed September 2026.
- SAP SE. SuccessFactors HCM: Patch and Product Release Information / Contractual Maintenance. Knowledge Base Article 2287597. SAP Support Portal, accessed September 2026.
- SAP SE. Using Migration Assessment Tools. Migrating to SAP Integration Suite. SAP Learning, accessed September 2026.
- SAP SE. Migration Offers and Resources from SAP Integration Suite. sap.com, accessed September 2026.

Source-platform documentation

- Boomi. ComponentMetadata Object. Boomi Platform API Documentation, accessed September 2026.
- Boomi. Component Object. Boomi Platform API Documentation, accessed September 2026.
- Boomi. ComponentReference Object. Boomi Platform API Documentation, accessed September 2026.
- Boomi. EnvironmentExtensions Object. Boomi Platform API Documentation, accessed September 2026.

AiFA Labs

- AiFA Labs. The AI-Powered Mulesoft Migration to SAP Integration Suite from AiFA Labs Now Available on SAP® Store. Press release, July 8, 2025.
- SAP SE. AIFA LABS LLC: Cerebro SASA, AI Platform for SAP SDLC Automation. SAP partner solution page, accessed September 2026.
- AiFA Labs. SAP BTP Services. aifalabs.com, accessed September 2026.
- AiFA Labs. AI Knowledge Hub. aifalabs.com, accessed September 2026.
- AiFA Labs. Request a Demo: SASA. sasa.aifalabs.com, accessed September 2026.
- AiFA Labs. Sagar Chakraborty, Author Profile. AI Knowledge Hub, aifalabs.com, accessed September 2026.