Workday publishes these limits openly. This page puts them in one place, in the order you need them, before the one deadline that does not move.
Source: Workday’s Survey Answer Export API page and raw data export FAQ.
Source: Workday’s Peakon data privacy page.
| Data | How it comes out | Format | Worth knowing |
|---|---|---|---|
| Raw survey answers | Survey Answer Export API, switched on by Workday Customer Care | JSON, up to 20,000 records per request | Only answers given after it was switched on |
| Summary reports | Read from the Peakon screens | On screen | Scores, drivers, participation and comparisons; a backup if the API stalls |
| Comments | Export to Excel from the comments view | Excel | Conversations and acknowledgements are not included |
| Employee records | Export from employee records | File with all record fields | Ties past answers to the right segments |
| Question wording | Copy from the survey setup | A simple list | Our team uses it to map questions to drivers |
| Benchmarks | Not part of the account data | None | Aggregated from other companies, so they stay with Peakon |
Raw answers cover the whole Peakon account as JSON, with no way to pick a team, so someone with a data tool shapes them after export.
| # | Step | What to do |
|---|---|---|
| 1 | Confirm the date your Peakon service ends | The six-month deletion clock starts on that date, not at your renewal meeting. Get it in writing and add it to a shared calendar. |
| 2 | Check whether the export was ever switched on | The export only returns answers given after it was switched on. This tells you how much raw history you can get. |
| 3 | If not, raise a case with Workday Customer Care | Switching it on is a support request, not a button. Raise it early, because you cannot control how long the queue takes. |
| 4 | Name the person who will run the export | Admins do not get raw access automatically. Find the analyst with API access and data tools, and make sure they have time for it. |
| 5 | Set up the integration with the Answer permission | That permission only appears once the export is switched on. Setting it up early saves a day of confusion later. |
| 6 | Save the summary reports from the Peakon screens first | Scores, drivers, participation and comparisons can be read in Peakon without a developer. They are your backup if the API route stalls. |
| 7 | Plan for several requests, not one download | The answer export returns at most 20,000 records per request, and segment data comes out one attribute per call. |
| 8 | Save the comments as carefully as the scores | Comments explain the numbers, and they are the hardest thing to rebuild later from a summary report. |
| 9 | Write down what each field means | A data field nobody can explain becomes useless within a year. Keep the notes in the same folder as the files. |
| 10 | Open and spot-check every file before access ends | A broken export can only be redone while Peakon is still live. Compare a few numbers with what the Peakon screens showed. |
| 11 | Store the files where your team will find them later | If the person running the export is also leaving, finish the export before their last day. |
Still deciding where to go? Our roundup of Peakon alternatives compares the field. The export steps work the same whichever one you pick.
Sourced to Workday’s own public documentation.
Bring the files to a working session and we will walk through what carries across, what does not, and what your first cycle on a new platform looks like.
4.7 / 5 on G2