When Configuration Catalog migration stalls, Workday’s Object Transporter premigration check is almost always waiting on prerequisites in the target tenant. Workday flags a prerequisite as missing when the target has no corresponding instance, a missing Reference ID, or a mismatched Reference ID—and it only lists the first 50 issues until those are fixed.
This guide is the blocked-package path from Workday’s migrate topic (last updated 2026-04-03). Browse packages and their listed prerequisites first with View Configuration Catalog Content in Customer Central.
What “blocked” looks like
- You selected a target tenant and package instances in Configuration Catalog.
- Workday compared catalog instances to the target.
- You landed on a Pre-Migration Check report (or a Diff Report Not Generated page that sends you back to review the check).
- The table lists missing prerequisites. Until the first 50 are resolved, Workday will not identify and display additional issues.
If there are no missing prerequisites, Workday skips Pre-Migration Check and opens View Pre-Migration Diff instead—that package is not blocked on prerequisites.
How Workday classifies each row
| Signal | Meaning | Action Workday documents |
|---|---|---|
| SignalNo corresponding instance on target | MeaningPrerequisite object absent | Action Workday documentsCreate it in the target with a matching Reference ID |
| SignalMissing Reference ID | MeaningInstance exists without the ID OX needs | Action Workday documentsAdd the Reference ID to match the source |
| SignalMismatched Reference ID | MeaningIDs differ between source and target | Action Workday documentsUpdate the target ID to match the source |
| SignalNon Mappable = Yes | MeaningCannot auto-map | Action Workday documentsFix manually in the target tenant |
| SignalMap Instance button | MeaningTailored loading available | Action Workday documentsMap to a compatible target instance by Reference ID, or fix manually |
| SignalNon Mappable empty | MeaningNothing to do for that row | Action Workday documentsContinue |
For WD Setup migrations, Workday states you can only modify or map to existing target instances.
Clear the block
- Resolve each listed prerequisite (create, fix ID, or Map Instance).
- Keep Reference IDs aligned across tenants as you go.
- Click Rescan Target if you updated or mapped target instances.
- Click Retry Migration if you updated the source tenant.
- Repeat until prerequisites—including those beyond the original 50—are clear.
- Proceed to effective-date strategy (when needed), security Merge/Override choices, Pre-Migration Diff review, then Proceed with Migration.
Premigration Diff reports for migrations that never proceed remain available for 30 days, so you can resume a blocked package without rebuilding the selection from memory.
Do not confuse with later failures
| Stage | Still not a “prerequisite block” |
|---|---|
| StagePre-Migration Diff | Still not a “prerequisite block”Package cleared checks; you are choosing what to include/exclude |
| StageSecurity Edit Migration Behavior | Still not a “prerequisite block”Policies differ; choose Merge, Override, or Manual Selection |
| StagePost-Migration / Tenant Compare | Still not a “prerequisite block”Migration finished; validate results |
| StageReport downstream issues | Still not a “prerequisite block”Workday warns separately to validate migrated reports and watch alerts |
Package prerequisites on View Configuration Catalog Content are the advance warning. The premigration table is the hard stop. Fix IDs and missing instances in the target until Rescan goes quiet—then migrate.