---
title: "Why does Object Transporter block single-instance…"
description: "Workday does not support OX single-instance migration from Production. Use packages or CCT Advanced packages on supported paths instead."
url: https://kiweely.com/guides/workday-ox-production-single-instance-limits
---

# Why does Object Transporter block single-instance migration from Production?

Workday does not support OX single-instance migration from Production. Production can still source Sandbox, Implementation, and Preview for other supported types. Use a package or Configuration Change Tracker instead.

-   **Checked** against Workday on November 17
-   Applies to **Workday Object Transporter**
-   3 min read
-   Published November 17
-   By Kiweely

Workday currently does not support migrating single instances from Production tenants with Object Transporter. That sentence appears on both Migrate Single Instances with Object Transporter and the Migration Paths reference. If you open related actions on a Production report or calculated field and choose Migrate with Object Transporter, that path is the one Workday excludes.

## What still works from Production

The Migration Paths table still lists Production as a source with targets Sandbox, Implementation, and Preview for the migration types that table covers: single instances, Advanced Configuration Change Tracker packages, and configuration extracts — with the single-instance exception called out on the Production row.

So the practical split is:

| From Production | Supported per current Workday docs? |
| --- | --- |
| Single instance via related actions Migrate with Object Transporter | No |
| Advanced configuration package built from Configuration Change Tracker | Use only if your Customer Central path and tooling access allow Production as source for that package type |
| Configuration package / security package through OX | Confirm against Customer Central and the path matrix for your tenant types |
| Configuration extract loaded directly into Production as target | No — extracts cannot load to Production; stage elsewhere first |

Always re-read the live Migration Paths page before a Production project. Release notes linked from that page, including the 2026R1 Production to non-Production note, can change package behavior while the single-instance restriction remains stated on the single-instance topic.

## What to do instead

1.  **Reproduce in Sandbox or Implementation, then single-instance migrate from there.** Sandbox and Implementation sources may target Implementation, Sandbox, and Preview on the matrix.
2.  **Build an Advanced package in Configuration Change Tracker** for the Production users and time window that created the objects, then migrate that package through OX if Production is an allowed source for Advanced packages in your environment.
3.  **Use a configuration package** when you intentionally select the instances rather than discovering them by audit window.
4.  **Do not use a configuration extract as a Production target.** Concept: Object Transporter forbids loading extracts to Production. Load to Implementation or Sandbox, then OX onward.

## How the single-instance flow normally works (non-Production)

On a supported source tenant:

1.  Related actions > Migrate with Object Transporter on the instance.
2.  Confirm Implementation Type if Workday left it blank.
3.  Launch Object Transporter in Customer Central and choose the target.
4.  Resolve Pre-Migration Check prerequisites (missing instance, missing Reference ID, mismatched Reference ID). Only the first 50 issues appear until you clear them.
5.  Review Pre-Migration Diff, set effective dates if needed, choose Merge or Override for differing security policies, then Start Migration.
6.  Keep the Post-Migration report. Workday retains postmigration summaries for 2 years. Unused Pre-Migration Diff reports remain 30 days.

That flow is what Production single-instance is not allowed to enter.

## Frequently asked questions

### Did 2026R1 remove the Production single-instance block?

The Migration Paths page still states that Workday currently does not support single-instance migration from Production, and the Manage Workday release notes record updates that restate that limit. Treat package-style Production to non-Production support as separate from single-instance related actions.

### Can I migrate one Production object inside a package of one?

A package of one is not the same UI path as Migrate with Object Transporter on a single instance. Use the package or CCT Advanced package path Workday allows for your source and target, and verify in Customer Central before you rely on it for go-live.

## Sources checked

-   [Migrate Single Instances with Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/tmt1675299857714.html)
-   [Object Transporter Migration Paths](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/reference--object-transporter-migration-paths.html)
-   [Concept: Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/omh1634567473070.html)
-   [Concept: Configuration Change Tracker](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/configuration-change-tracker/concept--configuration-change-tracker.html)

## Related guides

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

-   [### Which Object Transporter migration paths does Workday support? Object Transporter allows migrations only between documented tenant types. Implementation and Sandbox can target Implementation, Sandbox, and Preview. Production can target those non-Production tenants for supported types, but single-instance migration from Production is not supported.](https://kiweely.com/guides/workday-object-transporter-migration-paths)
-   [### Object Transporter or Configuration Change Tracker: which moves Workday config? Object Transporter migrates configuration you select, with dependents on standard packages. Configuration Change Tracker builds a change list by user and time, then hands an Advanced package to OX without auto-adding extra dependents.](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker)
-   [### How do I build a Configuration Change Tracker package by user and time? Configuration Change Tracker builds a change list for selected users and a timeframe. Package Ready to Migrate instances as an Advanced configuration package, run blank reference ID and exception audits, then launch Object Transporter. Advanced packages migrate only what you selected.](https://kiweely.com/guides/workday-configuration-change-tracker-how-to)

### More guides on Integrations and APIs

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

-   [EIB spreadsheet mapping when an AI assistant drafts the load](https://kiweely.com/guides/ai-workday-eib-mapping-for-consultants)
-   [Custom reports and RaaS when an AI assistant is helping you build them](https://kiweely.com/guides/ai-workday-custom-reports-raas-for-consultants)
-   [Run Workday Studio AUnit Before You Accept AI Edits](https://kiweely.com/guides/workday-studio-aunit-before-ai-edits)
-   [What AI tools can a Workday consultant use to build reports, calculated fields and EIB loads faster?](https://kiweely.com/guides/ai-tools-for-workday-reports-calculated-fields-eib)
-   [Which Workday Integrations May Auto-Remediate](https://kiweely.com/guides/which-workday-integrations-may-auto-remediate)
-   [An Integration Run Book Assistants Can Query](https://kiweely.com/guides/workday-integration-run-book-for-assistants)
-   [When Workday Integrations Should Leave the Tenant](https://kiweely.com/guides/when-workday-integrations-leave-the-tenant)
-   [Workday API Rate Limits When Many Employees Ask Questions in Chat](https://kiweely.com/guides/workday-rate-limits-when-employees-ask-in-chat)

### From the blog on Integrations and APIs

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

-   [Ask Claude, ChatGPT, or Gemini About a Failed Workday Run](https://kiweely.com/blog/ask-an-assistant-about-a-failed-workday-integration)
-   [Before-and-After Diffs and One-Step Rollback for Integration Fixes](https://kiweely.com/blog/before-and-after-diffs-and-one-step-rollback)
-   [What Is an AI-Built Workday Integration Platform Outside the Tenant?](https://kiweely.com/blog/what-is-ai-built-workday-integration-platform)

## 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.
