Workday vs SuccessFactors vs Oracle
Ratings Based on Experience Integrating HR Tech for People Analytics
To build a people analytics platform, you need to extract mountains of raw data from an HR system. Every HRIS promises seamless integration, but their underlying architecture tells a different story. After more than a decade of HR analytics integration architecture experience (try saying that 5 times fast), we know what we’re talking about.
In this living guide, we’ll share our take on which HRIS vendor is easiest to pull data from. You’ll find out what it’s really like to extract, transform, and model workforce data from the likes of Workday, SAP SuccessFactors, and Oracle HCM Cloud–straight from the frontlines of data engineering. At the top of each section, we’ll give the platform a grade based on how easy or difficult it was to extract their data, which we called their Data Accessibility Score.
But before we dive in, let’s get one thing out of the way: Every rating below assesses how cooperative and flexible the vendor’s ecosystem is if you try to extract data from it. It is us grading them. It is not a grade on One Model’s integration quality. The fact that data extraction can be challenging is exactly why you need One Model - we have already figured out how to work with all these platforms. We did the hard part, so that you don’t have to.
Frankly, our connectors are excellent (if we do say so ourselves). We’ve built production-grade pipelines that successfully extract, model, and deliver clean historical data out of every single platform on this list. But while some HRIS vendors roll out a red carpet for data extraction, others make you crawl through glass, solve riddles, and consult ancient scrolls. A low score here simply means the vendor built a moat around your data, not that we couldn't build a bridge over it. Furthermore, if you ever try to do it yourself, this is the degree of difficulty you’d face.
Bookmark this blog, subscribe to our blog, or follow me (Chris Butler) and One Model on LinkedIn to stay up to date.
A Quick Note on Data Accessibility Scores
Ratings provided are an anecdotal and unscientific evaluation of our experience in gaining access to, maintaining, and working with the data held in the associated systems. They are my opinions.
If you would like to make use of any of our integrations in a standalone capacity: we now offer a data warehouse only product. This allows you to use our data pipeline and modeling engine to extract and transform data into a data warehouse hosted by One Model, or your own data warehouse. If your company prefers to handle your own analytics, and just need some help with the data side, we can certainly help. Contact us.
Cloud HRIS Comparison
Workday
- Data Accessibility Score - 2.5/5
- Method - API for standard objects, built-in reporting for custom objects (via reporting-as-a-service, or "RaaS") and SOAP API
- The Good - Great documentation, easy to enable API access and control of accessible fields, and good data structures once you have access. The RaaS option does a good job but is limited.
- The Bad - Slow, no custom fields available in API, geared towards providing a snapshot, number of parallel connections limited, constant tweaking required as new behaviors identified, expert integration skills required; true incremental feeds require you to read and interpret a transaction log.
Workday Requires a Custom-Built People Analytics Integration Architecture
Workday analytics embedded into the product is underwhelming and we've yet to see Prism Analytics make a dent in filling the needs that people analytics teams or HR analysts have beyond convenience analytics. So in the meantime, if you are serious about improving reporting and people analytics for Workday, you're going to need to get the data out of it and into somewhere else.
On the surface, Workday looks to have a great API, and the documentation available is excellent. However, the single biggest downfall is that the API is focused on providing a snapshot, which is fine for simple list reports but does not allow a people analytics team to deliver any worthwhile historical analysis. You don't get the bulk history output of other systems or the ability to cobble it together from complete effective-dated transactions across objects. To capture the complete history, we had to build an intense process of programmatically retrieving data, evaluating, and running other API calls to build the full history that we need. If you want more detail, take a look at my blog post on the subject –The End of the Snapshot Workday Edition.
The complexity of the integration, therefore, is multiplied and the time taken suffers immensely due to the object-oriented architecture that requires you to load each object into memory in order to be able to retrieve it. A full destructive data extraction means you're looking at 8+ hours for a small-medium enterprise and expanding to a week if you're a giant. The problem is exacerbated by the number of parallel connections allowed to run at a fraction of the stated limit. A full historical API integration here is not for the faint of heart or skill, we have spent 12+ months enhancing and tweaking our integration with each release (weekly) to improve performance and solve data challenges. Our integration, to give a sense of scale, generates some 500+ tables that we bring together in our modeling engine in preparation for analytics.
Beware of Oversimplifying the API Integration
Out-of-the-box integration plugins are going to be focused on the snapshot version of data, too. If you don't have the integration resources available, I wouldn't attempt an API integration. My advice is to stick with the built-in reporting tools to get off the ground. The RaaS tools do a good job of combining objects and running in a performant manner (better than the API). However, they will also be snapshot focused. As painful as it will be to build and run each timepoint, you will at least be able to obtain a basic feed to build upon. You won't have the full change history for deeper analysis until you can create a larger integration, or can drop in One Model. Robert Goodman wrote a good blog looking at both the API and his decision to use RaaS at the time, take a read here.
Regardless of the problems we see with the architecture, the API is decent and one of our favorite integrations to work with. It is, however, little wonder that with the data challenges we have seen and experienced, half of our customers are now Workday customers.
One Model Integration Capabilities with Workday
One Model consumes the Public Web Service API's for all standard objects and fields. One Model configures and manages the services for API extractions, so customers need only to create and supply a permissioned account for the extraction.
Custom objects and fields need to use a Raas (Report as a service) definition created by the customer in the Enterprise Interface Builder (EIB). The Report can then be transferred by SFTP or can be interacted with as an API itself.

Figure 1: One Model's data extraction from Workday
SuccessFactors
- Data Accessibility Score - 4/5
- Method - API
- The Good - A dynamic API that includes all custom MDF data, runs relatively quickly, and comprehensive module coverage.
- The Bad - Several API endpoints that need to be combined to complete the data view, can drop data without indication, at times confusing data structures. Also, major parts of the ecosystem aren’t included in the one OData interface and require separate connectors, e.g. SuccessFactors Learning Management System (LMS) and new acquisitions like SmartRecruiters aren’t included at all.
4 out of 5 is a pretty phenomenal rating in my book. I almost gave SuccessFactors a perfect 5, but there are still some missing pieces from the API libraries and we've experienced some dropped data at times that have required some adaptations in our integration. Overall, the collection of SF APIs is a thing of beauty for one specific reason: it is dynamic and can accommodate any of the Meta Data Framework (MDF) custom changes in its stride. This makes life incredibly easy when working across multiple customers and means we can run a single integration against any customer and accurately retrieve all customizations without even thinking about them. Compared to Workday, where the API is static in definition and only covers the standard objects, this facet alone is just awesome.
This dynamic nature though isn't without its complexities. It means you need to build an integration that can interrogate the API and iterate through each of its customizations. However, once it is complete it functions well and can adapt to changing configurations as a result.
Prepare to Merge API Integrations for People Analytics
Multiple API endpoints also require different integrations to be merged. This is a result of both upgrades in the APIs available in the case of the older SuccessFactors API and the OData API as well as providing an API to acquired parts of the platform (i.e., Learning from the Plateau acquisition). We're actually just happy there is now an API to retrieve learning data as this used to be a huge bug bear when I worked at SuccessFactors on the Workforce Analytics product. The only SF product I know of right now that doesn't have the ability to extract from an API is Recruiting Marketing (RMK) from the jobs2web acquisition, hopefully, this changes in the future.
Full disclosure, I used to hate working with SuccessFactors data when we had to deal with flat files and RDFs, but with the API integration in place, we can be up and running with a new SuccessFactors customer in a few hours and be confident all customizations are present.
Another Option - Integration Center
I haven't spoken here about the new Integration Center release from earlier last year as we haven't used it ourselves and only have anecdotal evidence from what we've read. It looks like you could get what you need using the Integration Center and deliver the output to your warehouse. You will obviously need to build each of the outputs for the integration which may take a lot of time but the data structure from what I can tell looks solid for staging into an analytics framework. There are likely a lot of tables to extract and maintain though, we currently run around 400+ tables for a SuccessFactors customer and model these into an analytics-ready model. If anyone has used the Integration Center in an analytics deployment please feel free to comment below or reach out and I would be happy to host your perspective here.
One Model Integration Capabilities with SAP SuccessFactors
One Model consumes the SF REST API's for all standard fields as well as all customized fields including any use of the MDF framework. One Model configures and manages the service for API extractions. Customers need only to create and supply a permissioned account for the extraction.
SF has built a great API that is able to provide all customizations as part of the native API feed. We do use more than one API though as the new OData API doesn't provide enough information and we have to use multiple endpoints in order to extract a complete data set. This is expertly handled by One Model software.

Figure 2: One Model's data extraction from SuccessFactors
Oracle HCM Cloud (Fusion)
Oracle's underlying HR data is well structured and reliable, and we have a repeatable way to get it into an analytics-ready warehouse. Historically that meant HCM Extracts, and it was hard-won. Today our primary method is Oracle's HCM Cloud REST API, which we've upgraded to Oracle's current 26C release and are running with large enterprise customers. That shift is why we've raised Oracle's score. The story below covers how we got here, because hands-on experience is exactly what you want from an integration partner. If you're evaluating One Model as an Oracle shop, talk to us. We can show you exactly what the API delivers today.
- Data Accessibility Score: 2.5/5 (up from 2/5). Our original rating was based on HCM Extracts and an older API version (19D). Oracle's 26C REST API closes most of the field and history gaps that held it back, though some objects remain hard to reach.
- Method: Oracle HCM Cloud REST API (26C) as primary. As with all systems, not everything is available through the API, so in some cases we use HCM Extracts to supplement the API data.
- The Good: Oracle's data integrity and structure are strong. The 26C API fills many of the gaps we hit in earlier versions. It supports standard OAuth, effective-dated history, and descriptive flexfields through child objects. Once an extraction is built, it's reliable and maintainable.
- The Bad: Oracle still makes you work for it. Not every object is open to third parties, since some endpoints are reserved for Oracle's internal use. Some sub-objects are complex to request. Paging limits vary by endpoint. Incremental changes need careful effective-date handling to avoid overlapping history.
Bottom line up front: Oracle's underlying HR data is good, and we have a repeatable, production-tested way to get it into any people analytics warehouse. Getting there was hard-won and we think that history is worth telling, because it's exactly the kind of hands-on experience you want from an integration partner. Below is that story, plus where things stand today.
The History: How We Originally Solved Oracle Extraction
I think I lost a lot of hair and put on ten pounds (or was it ten kilos?!) working through a suitable extraction method for the HCM Cloud suite that was going to give us the right level of data granularity for proper historically accurate people analytics data. We tried every method of data extraction from the API to using BI Publisher reports and templates. I can see why people who are experienced in the Oracle domain stick with it for decades, because the experience here is hard-won and akin to a level of magic. The barriers to entry for new players are just so high that even as a software engineer, data expert, and a career spent with HR data, I could not figure out how to get a piece of functionality working that in other systems would take a handful of clicks.
In looking to build an extraction for people analytics, you have a number of methods at your disposal. There's now an API and the built-in reporting could be a reasonable option for you if you have some experience with BI Publisher. There are also the HCM Extracts built for bulk extraction purposes. During our initial build, we spent days and probably weeks trying to get the built-in reporting and BI Publisher templates to work correctly and deliver us the data we're used to from our time using Oracle's on-premise solutions (quite a good data structure). Alas, this was one of the most frustrating experiences of my life. It really says something when I had to go find a copy of MS Word 2006 in order to use a plugin that for some reason just wouldn't load in MS Word 2016, all to edit and build a template file to be uploaded, creating multiple manual touchpoints whenever a change is required. Why is life so difficult??
Even with a bunch of time lost to this endeavor, our experience was that we could probably get all the data we needed using the reporting/BI publisher route. However, it was going to be a maintenance nightmare if an extract had to change, requiring an Oracle developer to make sure everything ran correctly. If you have experienced resources this may work for you still.
We eventually settled on the HCM Extracts solution provided that while mind-numbingly frustrating to use the interface to build and extract will at least reliably provide access to the full data set and deliver it in an output that with some tooling can be ingested quite well. There are a number of options for how you can export the data and we would usually prefer a CSV style extraction but the hierarchical nature of the extraction process here means that XML becomes the preferred method unless you want to burn the best years of your life creating individual outputs for each object tediously by hand in a semi-responsive interface. We, therefore, figured it would be easier, and enhance maintainability if we built our own .xml parser for our data pipeline to ingest the data set.
With an extract defined though there's a good number of options on how to deliver and schedule the output and reliability is good. We've only had a few issues since the upfront hard work was completed. Changing an extract as well is relatively straightforward if you want to add a field or object you can do so through the front-end interface in a single touchpoint.
Want to Better Understand How One Model can Help You? Request a Demo Today.
Other HRIS Comparisons Coming Soon
ADP Workforce Now
