---
title: "Which Object Transporter migration paths does Workday…"
description: "Use Workday’s OX source and target matrix for single instances, Advanced CCT packages, and configuration extracts."
url: https://kiweely.com/guides/workday-object-transporter-migration-paths
---

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

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

Object Transporter supports migrations between specific tenant types for single instances, Advanced configuration packages from Configuration Change Tracker, and configuration extracts. If your source and target pair is not on Workday’s matrix, OX will not complete that path.

## Supported paths

Copied from Workday’s Object Transporter Migration Paths reference:

| Source tenant | Target tenants |
| --- | --- |
| Implementation | Implementation, Sandbox, Preview |
| Sandbox | Implementation, Sandbox, Preview |
| Preview | Implementation, Sandbox |
| Wdsetup (Configuration Catalog only) | Implementation, Sandbox |
| Workday App Development tenant | Implementation |
| Production | Sandbox, Implementation, Preview |

## Path rules that block real projects

**Preview as source.** If the content relies on functionality Workday has not yet delivered to Production, wait until that delivery finishes. Workday often ships updated web service versions, data models, configurations, or implementation types to Preview first. Those gaps make migration unlikely to succeed until the target tenants have the same functionality.

**Development as extract target.** When you migrate a configuration extract, Workday can offer Development as a target. Migrating extracted content from Implementation to a Development tenant is not supported and results in an error message.

**Production single instances.** The path table lists Production as a source for Sandbox, Implementation, and Preview. The same Workday page notes that Workday currently does not support migration of single instances from Production tenants. Migrate Single Instances repeats that limit. Workday’s single-instance topic still uses Sandbox to Production as its worked example for non-Production sources.

**Standard packages to Production.** Concept: Object Transporter and Migrate Packages describe moving configuration to Production from Implementation or Sandbox. That Production cutover path is separate from the narrower single-instance / Advanced CCT / extract matrix on the Migration Paths reference.

**Configuration extracts into Production.** Concept: Object Transporter says you cannot load configuration extracts to Production tenants. Import to Implementation or Sandbox, then migrate to Production with Object Transporter.

## What the matrix applies to

Workday states the table covers:

-   Single instances.
-   Advanced configuration packages in Configuration Change Tracker.
-   Configuration extracts.

Standard configuration packages and security configuration packages still run through OX and Customer Central; confirm the tenant pair against this reference and against any release note linked from the page (including the 2026R1 note on Production to non-Production migrations) before you promise a cutover path.

## How to read a blocked attempt

1.  Confirm source and target types against the table above.
2.  If the source is Preview, check whether the implementation type or web service version exists on the target yet.
3.  If the source is Production and you used Migrate with Object Transporter on one instance, switch to a package or CCT Advanced package path that Production supports.
4.  If you tried to load a `.dat` extract into Production, stage through Implementation or Sandbox first.

## Frequently asked questions

### Can I OX from Sandbox to Production?

Yes for ordinary configuration packages. Concept: Object Transporter tells you to stage extracts on Implementation or Sandbox and then use Object Transporter to migrate to Production. Migrate Packages describes Merge as the default when you move routine updates from preview, sandbox, or development environments to Production. The Migration Paths table on Workday’s reference page is scoped to single instances, Advanced CCT packages, and configuration extracts; confirm that narrower matrix separately when you use those three types.

### Can Production send config to Sandbox?

Yes for the Production row’s package-style targets: Sandbox, Implementation, and Preview. Not for single-instance migration from Production.

### Where do I see objects OX can migrate?

Run the Object Transporter Supported Objects (OX) report in Customer Central or non-Production tenants with Customer Central access.

## Sources checked

-   [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)
-   [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)

## Related guides

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

-   [### Sandbox to Production Object Transporter checklist Confirm Customer Central access, build a supported Sandbox package or single instance, clear Pre-Migration Check, review Pre-Migration Diff, keep Merge for security unless you mean Override, then migrate to Production and keep the Post-Migration report.](https://kiweely.com/guides/workday-object-transporter-sandbox-to-prod-checklist)
-   [### 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)
-   [### 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.](https://kiweely.com/guides/workday-ox-production-single-instance-limits)

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

-   [Turning Your Existing Workday RaaS Reports into Governed AI Tools](https://kiweely.com/blog/exposing-existing-workday-raas-reports-to-claude-and-chatgpt)
-   [Embedding Live Workday Time Off, Pay, and Approvals Inside DingTalk, Feishu, and Lark](https://kiweely.com/blog/embedding-workday-self-service-inside-dingtalk-feishu-lark)
-   [Connecting ChatGPT Enterprise and Team to Workday Without a Shared Service Account](https://kiweely.com/blog/connect-chatgpt-enterprise-to-workday-mcp-without-isu)

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