Object Transporter is how Workday moves configuration from one tenant to another. It migrates the objects you select and the dependent objects those instances use. It does not migrate transactional data or reference data. Deployment Agent can help you understand a failure along the way. The skills and sample-prompt topics show it interpreting a SOAP error during an Object Transporter migration. They do not show it starting Migrate with Object Transporter.
You need Customer Central. Workday provides it at no additional cost. It is not part of the service. You can start in the source tenant; Workday sends you to Customer Central to finish. Object Transporter Supported Objects (OX) is the list of what can move. If Workday says the implementation type cannot migrate, pick another type or another tool.
The workflow the agent must not skip
Workday’s migration workflow is four steps. Do them in order. An assistant that “summarizes the package” has not done any of them.
- Error check. Blocking errors appear on View Errors, with guidance. Fix and retry. Nothing else matters until this page is clear.
- Prerequisites. Pre-Check Migration lists missing prerequisites: no matching instance on the target, a missing Reference ID, or a mismatched Reference ID. Only the first 50 show until you clear them. Fix Reference IDs so they match, create the missing instance on the target, or map the source instance to a compatible target instance inside the workflow. Signing the prerequisite as “okay to ignore” is not a documented option.
- Pre-Migration Diff Report. Instances are grouped by implementation type. The header counts implementation types and unique instances; an instance found under several types is counted once. Tabs:
- All Instances
- Modified (orange): in both tenants, different. Workday overwrites the target with the source, except security policies, which merge unless you change that with Edit Migration Behavior. A security group and its business process security policy permissions migrate additively. Existing assignments on the target stay. Someone has to remove a group on the target by hand if you no longer want it.
- New (blue): added from the source.
- No Change (gray): identical, nothing to migrate.
- Excluded: top-level instances you removed from scope. Open dependencies, and use View Attribute Diff on a modified dependency. Manage Modified Instances can drop a modified instance from this migration.
- Migration. Workday migrates the current version of the tenanted object, not a frozen copy from the day you added it to the package. When it finishes, open the post-migration summary. Those summaries stay available for two years. Run Tenant Compare if you need a saved comparison. A successful migration makes the package contents available on the target.
Reference IDs are the identity. Same Reference ID and same Reference ID type means “this is the same instance.” Set them on parents and children before the first migration. Integration IDs lists them. Maintain Reference IDs updates them in bulk.
Where Ask belongs in that sequence
Open Deployment Agent in the Implementation, Sandbox, Preview, or Customer Central tenant, with Ask on. In a tenant other than Customer Central it reads the active tenant. From Customer Central, name the connected tenant.
Workday’s published prompt:
I am getting a SOAP error while using Object Transporter to migrate Payroll data. What are the common causes for this error and how do I fix them?
Make it specific. The SOAP example’s pattern is: role, web service, the exact fault, what you already checked, then a second prompt for the functional area and the domain permissions the integration system user needs.
I am an implementer. In my [tenant name] tenant I am migrating a configuration package with Object Transporter. The pre-check says this Reference ID is missing on the target: [ID and type]. Which task do I use to compare Reference IDs, and what should match before I retry? Do not tell me to skip the prerequisite.
Then do the thing it names, and look at the ID yourself. Workday says answers can be incomplete. Rate the answer after you have checked.
Ask is also the right place to inspect a dependent object before you migrate it:
In my tenant, how does this calculated field work: [name]?
If the field’s dependency is a location, expect the location to show up as a prerequisite, not as a migrated dependency. That is Workday’s own report example.
Configuration intelligence includes Configuration Catalog package suggestions. Migrating a catalog package is still this same Object Transporter workflow, into an implementation or sandbox tenant. Test it before it goes toward Production. You cannot load a configuration extract directly into Production. Put the extract on an Implementation or Sandbox tenant, then migrate to Production with Object Transporter.
What to ask at each screen
| Screen you are on | Prompt that stays honest | What you do with the answer |
|---|---|---|
| Screen you are onView Errors | Prompt that stays honestPaste the message. Ask for the documented cause and the task that fixes it. | What you do with the answerFix and retry. Do not continue. |
| Screen you are onPre-Check Migration | Prompt that stays honestPaste one missing prerequisite. Ask whether it is a missing instance or a Reference ID mismatch, and which report shows the ID. | What you do with the answerClear it. Remember only 50 are listed at a time. |
| Screen you are onDiff, Modified security policy | Prompt that stays honestAsk what merge versus overwrite will do to this policy. | What you do with the answerChoose Edit Migration Behavior only if you intend to overwrite. |
| Screen you are onDiff, security group | Prompt that stays honestAsk whether this migration removes existing groups on the target. | What you do with the answerThe workflow topic says it does not. Plan a manual removal if that is the design. |
| Screen you are onAfter migration | Prompt that stays honestAsk which Tenant Compare cases mean the instance exists on only one side. | What you do with the answerUnmatched Reference IDs. Open them. Do not ask the agent if the migration “succeeded.” The product already told you. |
Choose the migration tool before you prompt
| Situation | Tool |
|---|---|
| SituationOne report, one business process definition, a known dependency tree | ToolObject Transporter, single instance or a small package. Single instance from Production is not supported. |
| SituationMany unrelated changes by a set of people, and you need them after a Sandbox refresh | ToolConfiguration Change Tracker, then an extract. Tracker does not add dependencies that nobody changed inside the window. |
| SituationA file you must hold outside the tenant, or a target with a different billing ID | ToolConfiguration extract. The file is encrypted. You cannot edit it. Recreate the package if the content is wrong. |
| SituationWorkday-delivered locale content | ToolConfiguration Catalog, then this same migration workflow. |
An assistant that picks “OX” for all four will drop dependencies or try to edit an extract.
Failure modes
- Starting from a package and assuming dependencies are frozen. Workday migrates the current version.
- Treating a gray No Change as “we migrated it today.” Nothing moved. If the target is wrong, the source matches it.
- Overwriting a target security policy when you wanted a merge. The default is merge. Overwrite is a choice.
- Expecting additive security migration to revoke a group. It will not.
- Using Q&A, which cannot see the package, and pasting its generic SOAP advice into a cutover note.
- Leaving the only explanation of a prerequisite in the chat. The post-migration report lasts two years. The chat lasts 14 days.
- Asking the agent to migrate. It is not the Migrate with Object Transporter task.
Frequently asked questions
Can Ask see the diff report?
Workday says Ask searches, opens tasks, and runs reports to ground an answer, and that configuration inspection is read-only. That is the documented Ask skill; Workday’s Configuration Cloud, in opt-in early access for partners since 18 November 2026, adds a path where Deployment Agent carries out approved changes. Confirm any ID it names on the diff screen in front of you. Do not migrate from the chat.
Why did a report migrate without its location?
Because the location is reference data in Workday’s example, not a dependent configuration object. Create it on the target or map it in the prerequisite step.
How do we move this to Production?
Not with an extract loaded to Production. Migrate from the Implementation or Sandbox tenant with Object Transporter. Read the diff first. Security group permissions will add, not replace.
Who is allowed to migrate?
Customer Central access is separate from the Deployment Agent Users domain. Tooling access, including security configuration packages and extracts, is granted in Customer Central. An agent user who cannot open Migrate with Object Transporter cannot complete a migration no matter how good the prompt is.
Sources checked
Public Workday admin-guide topics listed above, fetched 2026-11-16.