Workday has not published a configuration workbook, a workbook import, or an AI job that fills one. Implementers still keep spreadsheets because a project needs a list of decisions. Those spreadsheets go stale the hour someone edits the tenant and does not edit the sheet. The records Workday actually keeps are the tenant, the migration diff, and Tenant Compare.
Deployment Agent can help you read a non-Production tenant so the sheet starts from configuration instead of memory. It is not the workbook, and it deletes the conversation after 14 days.
What to treat as the record
| Need | Workday object | What people wrongly put in a workbook instead |
|---|---|---|
| NeedDelivered starting content | Workday objectA Configuration Catalog package in Customer Central. Filter by SKU or country. Read prerequisites on the package. | What people wrongly put in a workbook insteadA tab of “we will build these reports” that duplicates a package you could migrate. |
| NeedYour configuration, object by object | Workday objectThe instance in the source tenant, migrated with Object Transporter when it is a supported object | What people wrongly put in a workbook insteadA row that says “done” with no Reference ID. Object Transporter treats the same Reference ID and Reference ID type as the same instance. |
| NeedProof two tenants differ | Workday objectTenant Compare. Unmatched Reference IDs are instances that exist on only one side. Matched instances with attribute differences share an ID and differ in configuration. Domain security policy compares can include suspended domains and subdomains. | What people wrongly put in a workbook insteadA color-coded column nobody regenerates after the next migration. |
| NeedA pile of unrelated project edits that must survive a Sandbox refresh | Workday objectConfiguration Change Tracker, then a configuration extract | What people wrongly put in a workbook insteadA workbook plus hope. Tracker does not invent dependencies you changed outside the window you selected. |
| NeedHow a calculated field or report actually behaves | Workday objectDeployment Agent Ask, in that tenant, confirmed by opening the object | What people wrongly put in a workbook insteadA prose description pasted from a chat that may have been documentation Q&A. |
Customer Central is the tenant Workday gives you for this tooling. It is not part of the service, and data stored there is not customer data. Object Transporter finishes in Customer Central even when you start from the source tenant.
Post-migration summaries remain available for two years. That is a longer record than a Deployment Agent thread.
How Ask fits, and where it stops
With Ask enabled, Workday says the agent has configuration intelligence grounded in tenant context: steps for calculated fields, linking compensation grades, and Configuration Catalog suggestions, including help with catalog setup. It can also troubleshoot a rule that did not run, and explain a concept in lay terms with citations.
Use it to seed a workbook, one object at a time, in a new chat:
In my tenant, how does this calculated field work: [name]? Name the business object, the function, and the fields it uses. I will check your answer in View Calculated Field.
Open the field. If it matches, write those three facts on the row and name the tenant and the date. If it does not match, do not “fix” the row to agree with the agent. The skills topic does not say Ask writes the workbook, and the setup topic says history is deleted after 14 days. A summarized thread will drop the function name you needed.
There is no indicator that Ask is on. A workbook built from Q&A without “in my tenant” is a documentation summary. Q&A cannot see your instances.
Do not ask the agent to mark the workbook complete. Completeness is a migration result: the pre-migration diff’s New, Modified, and No Change tabs, then a Tenant Compare you saved.
A workbook shape that does not fight the tools
If you keep a sheet, give it the columns Workday’s tools already use. Anything else is commentary.
| Column | Rule |
|---|---|
| ColumnImplementation type | RuleThe type you will select in Object Transporter or Tenant Compare. |
| ColumnReference ID and Reference ID type | RuleRequired before first migration if you want the next migration to find the same instance. |
| ColumnSource tenant and target tenant | RuleAn extract cannot be loaded straight to Production. Implementation or Sandbox first, then Object Transporter to Production. |
| ColumnPackage or single instance | RuleSingle-instance migration is not supported from Production. Packages are how you move a set. |
| ColumnPrerequisite | RuleFrom the pre-check, not from memory. Missing instance, missing Reference ID, or mismatched Reference ID. |
| ColumnDiff result | RuleNew, Modified, No Change, or Excluded. For Modified security policies, say whether you merged or overwrote. |
| ColumnCatalog package, if any | RuleSKU, country, and the prerequisite the package describes. Test before Production. |
| ColumnConfirmed in the task | RuleThe person and the task name (View Calculated Field, the business process definition, the domain policy). Not “the agent said.” |
Kiweely Vine can write a design document from the tenant you are signed in to and file it on the project. That is Kiweely’s product behavior, not a Workday workbook feature. It still has to be checked against the task. Vine asks before it changes the tenant. A document is not a migration.
Failure modes
- The workbook says a report migrated, and Tenant Compare shows it only on the source. Unmatched Reference IDs are that case. The sheet was ahead of the tool.
- The workbook lists a location as part of a report migration. Object Transporter will flag the location as a prerequisite, not migrate it as a dependency of the calculated field in Workday’s example.
- Two tenants, two ID schemes, one sheet. Fix IDs with Maintain Reference IDs before the first migration, not after the diff is full of mismatches.
- A Sandbox refresh. The sheet still describes last week’s Sandbox. The tenant is a copy of Production again unless you reloaded an extract.
- Catalog content edited in the sheet and never in the tenant. The package that migrates is the package in Customer Central, after you test it.
- Asking a desktop chat with no Workday sign-in to invent the configuration inventory. It can draft a template. It cannot see the Reference IDs.
Frequently asked questions
Should we ban workbooks?
No. Ban workbooks that do not carry Reference IDs, tenant names, and a diff result. The tenant remains the configuration. The sheet is the index.
Can Deployment Agent keep the workbook up to date?
No. It can answer in the moment, in a non-Production tenant, and Workday then deletes the chat. Regenerate a Tenant Compare when you need the current difference.
Is the Configuration Catalog our workbook?
It is Workday’s delivered packages, not your design history. Use it so the workbook does not restate content you can migrate. You still test it. Workday says regulatory and business confirmation is yours.
Where do decisions live if not in the chat and not in a tab?
In the tenant you migrated, in the post-migration summary, and in a short decision record you file the day you decide. Fourteen days of chat is not a design baseline.
Sources checked
Public Workday topics listed above, fetched 2026-11-16. Kiweely Vine’s design-document behavior is from kiweely.com product copy, not from Workday. Workday does not publish a configuration workbook on the pages checked.