Workday Recruiting → Ashby

Catalog plan outline

General guidance from the Afterstack catalog for Workday Recruiting → Ashby. Not Workday Recruiting or Ashby vendor documentation.

Migration friendliness

Workday Recruiting 5/10 · Ashby 6/10

Speed to live

Workday Recruiting 2/10 · Ashby 6/10

Catalog migration difficulty

Workday Recruiting high · Ashby medium

Data to export from Workday Recruiting

• pipeline and deal records
• custom objects
• synced email and calendar links
• workflow rules
• saved reports
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: ats

How the catalogs differ

• Workday Recruiting is flagged for custom objects. Ashby is not, so the map is a redesign rather than a field-for-field copy.
• Ashby is not flagged for: custom objects.
• Workday Recruiting is flagged with an open API, which is the export path to test.
• Ashby is flagged with an open API for the load.
• Workday Recruiting is cataloged as a fit for: Workday HCM campuses.
• Ashby is cataloged as a fit for: Tech TA teams that want ATS analytics without a BI project.

Phases

1. Export

   Take Workday Recruiting as the source of truth for this pair. Export pipeline and deal records; custom objects; synced email and calendar links; workflow rules; saved reports; installed marketplace apps; AI assistant configuration; records for the catalog use cases: ats. Enterprise ATS inside Workday HCM — reqs that already live next to payroll.

2. Map

   Load into Ashby only after the field map is written down. Modern ATS with analytics and AI assist — the high-signal Greenhouse alternative. Workday Recruiting is flagged for custom objects. Ashby is not, so the map is a redesign rather than a field-for-field copy.

3. Prove a sample

   Ashby scores 6/10 on speed to live and 6/10 on migration friendliness. Run one sample load and one report the team already uses in Workday Recruiting before a full cutover.

4. Cut over

   Workday Recruiting scores 5/10 on migration friendliness and is marked high difficulty in the catalog. Keep Workday Recruiting readable until the team is working in Ashby. Workday Recruiting is the incumbent when HCM is already Workday. AI features exist; the product is still an enterprise ATS. A leave-from for global talent orgs; a non-starter as a Greenhouse-for-startups replacement.

Workday Recruiting to Ashby: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not Workday Recruiting or Ashby vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from Workday Recruiting

Workday publishes Recruiting as SOAP operations, and the two pages opened on 2026-10-17 are Get_Candidates version 45.1 and Get_Job_Requisitions version 45.0 on community.workday.com. Get_Candidates says it returns information for the candidates named in the request, and it marks contextual security as yes. The request element wraps a reference, criteria, a filter, and a response group. Criteria are AND conditions: every populated criterion narrows the set. One criterion is Job_Requisition_Reference. The validation line on that page says the applied-from date must be greater than or equal to the applied-through date, and the created-from date must be less than or equal to the created-through date. The response candidate carries name data, contact data, recruiting data, and status data. A job-applied-to block requires a requisition reference, and the page's validation text says you cannot change the job requisition on an existing application and that a person who already applied to that requisition is rejected. Get_Job_Requisitions says it returns requisitions and a reference to the related position, again with contextual security. You can ask by reference or by criteria, and a response group lets the caller drop definition data it does not want. A public pricing URL at workday.com/en-us/pricing.html returned 404 on this check, so no Workday software fee is copied. The catalog's empty starting price matches that gap. A trial length was not on a page that did not load.

• Workday Get_Candidates 45.1 — checked 2026-10-17
• Workday Get_Job_Requisitions 45.0 — checked 2026-10-17

How Ashby imports

Ashby's pricing sheet, reopened 2026-10-17, still withholds a platform dollar. Bands are up to 100 employees, 101 to 1,000, and above 1,000. Annual commitments are described as 10 percent less. Plan columns are Foundations, Plus, and Enterprise. The integrations block includes a row whose text is a two-way sync of Workday positions and job requisitions into Ashby, plus hired candidates and offer letters sent back to Workday. The capture did not show which column that row is checked in, so the plan is unmarked. Separate rows say bulk import of candidates from a CSV or forwarded resumes, and bulk import of openings from a CSV that can carry team, location, dates, and compensation. Those checkmarks were also not visible, so they stay unassigned. Included SMS on the sheet is 1,000 outbound messages a month on Foundations, 2,000 per seat each year on Plus, and 3,000 per seat each year on Enterprise. Extra SMS is 90 dollars per 1,000 on every column. SSO is printed as 100 dollars a month on the Foundations column only. AI Notetaker is a paid add-on on all three. Included AI credits are 1,500 a month, 2,500 per seat each year, and 12,500 per seat each year. Email lookups show 200 included on each column. The API introduction is RPC: paths like category.method, mostly POST, JSON bodies, Content-Type application/json, Basic auth with the key as the username and a blank password. It says not to call from a browser because CORS is not configured. It does not mention Workday. No sentence on the sheet is a trial length. The catalog trial flag is therefore unverified. Payroll stays in Workday. This pair moves recruiting objects, not the HCM.

• Ashby pricing — checked 2026-10-17
• Ashby API introduction — checked 2026-10-17

Object and field mapping

• A Workday job requisition is the object Get_Job_Requisitions returns, with a pointer at the related position. Ashby's sheet describes positions and requisitions syncing in, but not the field list.
• A Workday candidate's name, contact, recruiting, and status data are what Get_Candidates returns. Ashby's candidate CSV is a different shape. The sheet does not say the CSV is a Workday extract.
• An application is tied to one requisition in the Workday validation text. Changing that requisition on an existing application is rejected. Do not plan a rewrite of the req id during load.
• Hired candidates and offer letters are the return path the Ashby row names. Interview kits, scorecards, and Workday business-process history are not in that sentence.
• Openings CSV columns the sheet names are team, location, dates, and compensation. Workday position data may be richer. Unnamed fields do not ride along.
• SSO at 100 dollars a month is a Foundations commercial line, not a migrated Workday security policy.
• The Ashby API is a backend RPC. It is not documented as a Workday SOAP client.

What will not carry over

• Payroll, benefits, and the rest of HCM. Neither page describes them moving.
• A visible plan assignment for the Workday integration row or the CSV rows.
• A Workday list price. The pricing URL 404'd.
• Browser calls to Ashby. The introduction forbids that pattern.
• A trial on either pricing check.
• Business-process history and interview packets, which the Ashby Workday sentence does not mention.
• A guarantee that criteria dates behave the way the validation sentence reads. Quote the page; do not 'fix' it.

Cutover checklist

1. Confirm the Workday integration user can call Get_Candidates and Get_Job_Requisitions under contextual security. A missing domain will return nothing and look like an empty tenant.
2. Page candidates with the request filter. Criteria are AND, so a too-narrow requisition reference hides everyone else.
3. Record the date-validation sentence before you build filters. Do not assume from-dates are earlier than through-dates just because that is usual.
4. Ask Ashby which plan owns the Workday row. The sheet describes the sync and does not show the column.
5. If you fall back to CSV, reshape people into the candidate file and reqs into the openings file. Leave the plan blank until a later capture.
6. Proxy any Ashby API call through a server. Do not put the key in a browser.
7. Leave Workday HCM licensed. Send hires and offer letters back only after a sample hire matches what the row promises.
8. Budget Foundations SMS and the 100-dollar SSO line separately from the missing platform fee.

Common pitfalls

• Calling this a payroll migration. The documents are recruiting operations and a requisition sync.
• Checking the Workday row as included on Foundations because other rows sit nearby. The column was not in the capture.
• Treating a 404 pricing URL as a price of zero.
• Posting SOAP XML at Ashby's RPC. The introduction wants JSON and Basic auth.
• Reusing one person's application against a second requisition by editing the reference. The Workday page says that change is invalid.

Related catalog pages

• What should replace Workday Recruiting? — Switch narrative
• Ashby product page — Modern ATS with analytics and AI assist — the high-signal Greenhouse alternative.
• Ashby vs Workday Recruiting — Head-to-head already in the catalog
• Recruiting category — Catalog hub for this category