---
title: "Configuration Catalog migrate blocked: fix the first 50…"
description: "Object Transporter shows only the first 50 missing prerequisites. How Workday defines missing Reference IDs, non-mappable rows, and rescan."
url: https://kiweely.com/guides/configuration-catalog-prerequisites-blocking
---

# Configuration Catalog migrate blocked: fix the first 50 Object Transporter prerequisites

When a Configuration Catalog package will not migrate, Workday’s premigration check lists missing instances and Reference ID problems 50 at a time. Clear those, rescan, then continue.

-   **Checked** against Workday on November 18
-   Applies to **Configuration Catalog and Object Transporter**
-   2 min read
-   Published November 18
-   By Kiweely

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

1.  You selected a target tenant and package instances in **Configuration Catalog**.
2.  Workday compared catalog instances to the target.
3.  You landed on a **Pre-Migration Check** report (or a **Diff Report Not Generated** page that sends you back to review the check).
4.  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 |
| --- | --- | --- |
| No corresponding instance on target | Prerequisite object absent | Create it in the target with a matching Reference ID |
| Missing Reference ID | Instance exists without the ID OX needs | Add the Reference ID to match the source |
| Mismatched Reference ID | IDs differ between source and target | Update the target ID to match the source |
|  **Non Mappable** = Yes | Cannot auto-map | Fix manually in the target tenant |
|  **Map Instance** button | Tailored loading available | Map to a compatible target instance by Reference ID, or fix manually |
| Non Mappable empty | Nothing to do for that row | Continue |

For WD Setup migrations, Workday states you can only modify or map to existing target instances.

## Clear the block

1.  Resolve each listed prerequisite (create, fix ID, or Map Instance).
2.  Keep Reference IDs aligned across tenants as you go.
3.  Click **Rescan Target** if you updated or mapped target instances.
4.  Click **Retry Migration** if you updated the source tenant.
5.  Repeat until prerequisites—including those beyond the original 50—are clear.
6.  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” |
| --- | --- |
| Pre-Migration Diff | Package cleared checks; you are choosing what to include/exclude |
| Security Edit Migration Behavior | Policies differ; choose Merge, Override, or Manual Selection |
| Post-Migration / Tenant Compare | Migration finished; validate results |
| Report downstream issues | 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.

## Sources checked

-   [Migrate Configuration Catalog Content with Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/qbd1670640965501.html)
-   [Concept: Configuration Catalog](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/fzu1561545120344.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Why the same account ID across tenants unlocks Object Transporter Configuration Catalog and Object Transporter require the same account ID on Customer Central, source, and target. Security Administrator names stay unique. Pair matching IDs with Migration Administrator on both tenants, then Manage Tenant Access.](https://kiweely.com/guides/workday-customer-central-same-account-id)
-   [### Object Transporter migration workflow: pre-check, first 50, merge vs override Object Transporter blocks on source errors, then lists missing prerequisites—only the first 50 at a time. Clear Reference IDs or map instances, review the Pre-Migration Diff, pick Merge or Override for security policies, migrate, then use the Post-Migration Report or Tenant Compare.](https://kiweely.com/guides/workday-object-transporter-migration-workflow)
-   [### Workday Configuration Catalog packages: filter, test, then migrate Configuration Catalog groups Workday-provided content into packages you migrate with Object Transporter into Implementation or Sandbox at no cost. Filter by SKU or country, test thoroughly, and confirm regulatory fit before Production.](https://kiweely.com/guides/workday-configuration-catalog-packages)

### More guides on Integrations and APIs

[All 89 guides](https://kiweely.com/guides#integrations)

-   [Tenant Compare after Object Transporter: when and how to run it](https://kiweely.com/guides/workday-tenant-compare-after-migration)
-   [How to find what Object Transporter can migrate](https://kiweely.com/guides/workday-object-transporter-supported-objects)
-   [Permission to launch a Workday integration: which domains Studio checks](https://kiweely.com/guides/permission-to-launch-workday-integration)
-   [What Workday Customer Central is (and isn’t) for implementers](https://kiweely.com/guides/workday-customer-central-for-implementers)
-   [What does Workday Studio “Content is not allowed in prolog” mean?](https://kiweely.com/guides/workday-studio-content-is-not-allowed-in-prolog)
-   [Why does Workday RaaS time out for non-admin users but work for admins?](https://kiweely.com/guides/workday-raas-timeout-non-admin-user)
-   [Why does a custom object update return 403 with escaped HTML in the body?](https://kiweely.com/guides/workday-custom-object-patch-403-escaped-html)
-   [Why does Create WCP API Client return 409 for an ISU?](https://kiweely.com/guides/workday-create-api-client-409-isu-already-has-client)

### From the blog on Integrations and APIs

[All posts](https://kiweely.com/blog)

-   [How to Reconcile Workday Payroll Feeds in Studio Without Days of Manual XML Diffs](https://kiweely.com/blog/reconciling-workday-payroll-studio-feeds-with-ai)
-   [Turning a Messy Client Spreadsheet into a Clean Workday EIB Load in One Conversation](https://kiweely.com/blog/messy-spreadsheet-to-workday-eib-load-with-ai)
-   [Workday REST API vs. SOAP Web Services: Why Setup Work Still Needs the Task Screen](https://kiweely.com/blog/workday-rest-api-vs-soap-coverage-gaps)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
