---
title: "Copy Workday Configuration Between Tenants Safely — Kiweely"
description: "How to copy Workday configuration between tenants with Object Transporter from Customer Central, which tool fits, and how to verify the copy."
url: https://kiweely.com/guides/workday-configuration-between-tenants
---

# What is the safest way to copy Workday configuration from one tenant to another?

Use Object Transporter, launched from the object or from Customer Central, and read its error check, prerequisite check and diff report before migrating. Use Configuration Change Tracker for project work and extracts only for different billing IDs.

-   **Checked** against Workday on November 19
-   Applies to **Workday configuration, Customer Central, Object Transporter**
-   6 min read
-   Published September 19
-   By Kiweely

The safest route is Object Transporter, because it reads the source object with its dependencies, stops on missing prerequisites in the target, shows a diff before it writes, and offers a Tenant Compare afterwards. Pick the package type by the job, then read each report before you click migrate.

**Kiweely Vine** is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect: it reads configuration in the tenant you connect and makes the changes there from a plain request. See how it works below.

## Which Workday tool should I use to copy configuration?

Workday publishes a decision table in its migration tools reference.

| Job | Tool | Why |
| --- | --- | --- |
| Move one report, one business process, a few known objects | Object Transporter (single instance or configuration package) | Includes every dependent component of the object |
| Move everything a project changed | Configuration Change Tracker, then Object Transporter | Builds the package from changes by user and time range |
| Keep a copy outside the tenant, or move to a tenant with a different Billing ID | Configuration Extracts | Extract files can be reloaded later; they cannot be loaded into Production |
| Bring Workday-delivered sample content (Workday Packaged Solutions) | Configuration Catalog with Object Transporter | Free content packages, such as HCM condition rules and calculated fields |

Limits worth knowing: a configuration package takes up to 300 instances plus dependencies. Only objects in the **Object Transporter Supported Objects (OX)** report can move. Configuration Change Tracker does not add missing dependencies: if a required change falls outside the time range you chose, it does not migrate, and the migration can fail.

## How do I launch Object Transporter in Customer Central?

Customer Central is a separate Workday tenant, so the migration always completes there. There are two ways in.

1.  From the source tenant, open the related actions menu of the instance and choose **Instance > Migrate with Object Transporter**. If the Implementation Type is blank, pick a valid type. Optionally enter an External Change Request ID to track the approval. Click **Launch Object Transporter in Customer Central** and sign in.
2.  From Customer Central, open the **Object Transporter (OX)** worklet and click **Migrate with Object Transporter**. Choose the source tenant, target tenant and the instance or package.

Before either works, a Customer Central administrator has to give Customer Central access to the tenants, create accounts and grant Object Transporter permissions. To migrate to or from Production, enable Customer Central access to Production and open a session with the **My Tenant Session** task. Workday says that session stays active for 30 days. A locked, revoked or disabled Production account ends it.

If the launch ends in an error rather than a report, see [Object Transporter errors](https://kiweely.com/guides/workday-object-transporter-errors).

## How do I copy configuration from Workday Production to Sandbox Preview?

Workday’s migration paths table lists these sources and targets:

| Source | Targets |
| --- | --- |
| Implementation | Implementation, Sandbox, Preview |
| Sandbox | Implementation, Sandbox, Preview |
| Preview | Implementation, Sandbox |
| Production | Sandbox, Implementation, Preview |

The page adds “Workday currently doesn’t support the migration of single instances from Production tenants.” The single-instance page repeats it. The table does not say whether packages are exempt from that limit. The Object Transporter concept page links a 2026R1 release note titled “Migrate from Production to Non-Production Tenants with Object Transporter”. That note sits behind a sign-in, so we have not read it. Treat the exact scope of Production-sourced migrations as something to confirm in your own Customer Central.

For a Preview source, Workday warns that if content relies on functionality not yet delivered to Production, you should wait until the delivery cycle completes before migrating it to other tenants.

If your goal is simply a fresh copy of Production, that is a refresh, not a migration. See [how often the Sandbox refreshes](https://kiweely.com/guides/workday-sandbox-refresh).

## What does Object Transporter check before it changes the target?

The workflow runs four stages:

1.  **Error check.** Errors that block migration appear on the View Errors page.
2.  **Prerequisites check.** Missing prerequisites are listed on the Pre-Check Migration page. Workday flags a prerequisite when there is no corresponding instance on the target or the Reference ID is missing or mismatched. Resolve the first 50 listed before Workday shows the rest.
3.  **Pre-Migration Diff Report.** Instances are grouped as Modified (orange), New (blue), No Change (gray) and Excluded. **View Dependencies** shows what else moves, and **View Attribute Diff** compares attributes.
4.  **Migration.** Workday migrates the current version of each tenanted object, less anything you excluded.

Three behaviors catch people out:

-   Modified instances are overwritten by the source instance unless they are security policies.
-   Security policies merge by default. Under **Edit Migration Behavior**, *Merge* is additive and Workday removes nothing; *Override* replaces the target policies and suits initial deployments or tenant refreshes; *Manual Selection* chooses per policy.
-   Object Transporter migrates configuration, “it doesn’t migrate transactional or reference data.” Workday’s example: migrating a report migrates the calculated field it uses, but not the location that field references. The location shows up as a missing prerequisite.

## How do I verify a copy after it runs?

Use Workday’s own tools, then check the objects themselves.

-   Open the **Post Migration** report from the Object Transporter (OX) dashboard.
-   Click **Run Tenant Compare** on the post-migration page to compare instances between source and target. Tenant Compare matches on reference ID, so types without reference IDs, or instances missing one, show zero counts and are not proof of a match.
-   Open **Matching Instances with Attribute Differences** for objects with the same reference ID but different configuration.
-   Open the migrated objects in the target. For a calculated field, compare the function, the saved fields and the output on a worker you know. For a security change, test as a user in the affected group.

Workday also tells you to validate migrated reports and consider downstream alerts and other processes.

### Worked example

Logan McNeil has a custom report in the Sandbox that uses a calculated field built on a location.

1.  Open the report, choose **Instance > Migrate with Object Transporter**, set the Implementation Type, and click **Launch Object Transporter in Customer Central**.
2.  Pick the target tenant and click **Migrate**.
3.  The check ends on **Diff Report Not Generated**: the location has no match in the target. Under Non Mappable, the answer is “Yes”, so create the location in the target with the same Reference ID, then click **Rescan Target**.
4.  The **Pre-Migration Diff Report** now shows the report New and the calculated field New. Click **View Attribute Diff** on any Modified dependency.
5.  Migrate. Run **Run Tenant Compare**, then open the report in the target and run it.

If Workday prompts for an effective-date strategy, you can apply 01/01/1900 or pick a date; dependencies inherit the date you choose.

## Where Kiweely fits

**Kiweely Vine** is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect. It reads configuration in the tenant you connect and makes changes there from a plain request.

Vine Free is $0 on a personal developer tenant with $5 of Kiweely Credits included, and Vine Personal ($99/month) and Vine Team ($149/seat/month) connect to any Workday tenant ([pricing](https://kiweely.com/pricing)). [Start free](https://kiweely.com/download).

## Frequently asked questions

### How do I launch Object Transporter in Customer Central?

From the object, choose Instance, Migrate with Object Transporter in its related actions menu, then click Launch Object Transporter in Customer Central and sign in. Or open the Object Transporter (OX) worklet in Customer Central and click Migrate with Object Transporter.

### How do I copy configuration from Workday Production to a Sandbox Preview tenant?

Workday's migration paths table lists Production as a source for Sandbox, Implementation and Preview, but says single instances cannot be migrated from Production. Check your Customer Central for what it offers, and confirm whether a configuration package is allowed where single instances are blocked.

### Does Object Transporter copy workers and other data?

No. It migrates configuration and its dependencies, not transactional or reference data. A missing reference value such as a location shows up as a missing prerequisite in the Pre-Migration Check.

### When should I use Configuration Extracts instead of Object Transporter?

Only to reuse a configuration many times, to move between tenants with different Billing IDs, or to keep a copy for later reload, such as before a refresh. Extracts cannot be loaded into Production.

### How many objects can one Object Transporter package hold?

A configuration package holds up to 300 instances and their dependencies.

## Sources checked

-   [Concept: Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/omh1634567473070.html)
-   [Reference: Migration Implementation Tools](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/reference--migration-implementation-tools.html)
-   [Concept: Object Transporter Migration Workflow](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/concept--object-transporter-migration-workflow.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)
-   [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)
-   [Steps: Migrate Packages with Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/qjd1632744764567.html)
-   [Migrate Configuration Changes with Configuration Change Tracker](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/configuration-change-tracker/migrate-obect-changes-by-specific-users-and-timefr.html)
-   [Concept: Configuration Catalog](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/fzu1561545120344.html)
-   [Create Customer Central Sessions](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/set-up-customer-central-production-access/ssj1618327625122.html)
-   [Concept: Tenant Compare Report](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/tenant-compare/concept--tenant-compare-report.html)

## Related guides

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

-   [### Workday Object Transporter (OX) Errors: Prerequisites, Diffs, and What Moves Object Transporter runs a four-stage sequence before moving configuration between Workday tenants: error check, prerequisite check, pre-migration diff report, and migration. Here is how to fix missing Reference IDs, handle the 50-prerequisite cap, and choose Merge vs. Override for security.](https://kiweely.com/guides/workday-object-transporter-errors)
-   [### What are the types of tenant in Workday? Sandbox, Sandbox Preview, Implementation and Production compared Most Workday customers get four tenants: Production, Sandbox, Sandbox Preview and Customer Central. Implementation and demonstration tenants cost extra. Sandbox refreshes weekly from Production, Preview twice a year, Implementation on demand.](https://kiweely.com/guides/workday-tenant-types)
-   [### When does the Workday Sandbox refresh, and what does it wipe? Weekly: Workday replaces the Sandbox with a full copy of Production data and configuration. Public Workday docs give no day or hour, so ask your tenant management contact. Preview refreshes twice a year, Implementation on demand.](https://kiweely.com/guides/workday-sandbox-refresh)
-   [### Why does my Workday calculated field return blank in a report? A calculated field returns blank when its function finds nothing to return, when its business object is not reachable from the report, or when the viewer cannot see a field it reads. Test one known instance first.](https://kiweely.com/guides/calculated-field-returns-blank)

### More guides on Integrations and APIs

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

-   [Multi-Tenant FDE Access via Customer Central Manage Tenant Access](https://kiweely.com/guides/multi-tenant-fde-customer-central-access)
-   [Configuration Catalog migrate blocked: fix the first 50 Object Transporter prerequisites](https://kiweely.com/guides/configuration-catalog-prerequisites-blocking)
-   [Why the same account ID across tenants unlocks Object Transporter](https://kiweely.com/guides/workday-customer-central-same-account-id)
-   [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)
-   [Object Transporter migration workflow: pre-check, first 50, merge vs override](https://kiweely.com/guides/workday-object-transporter-migration-workflow)

### From the blog on Integrations and APIs

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

-   [Why Shared Integration System Users (ISUs) Are a Security Risk for Employee AI Chatbots](https://kiweely.com/blog/why-integration-system-users-are-dangerous-for-workday-ai)
-   [Mapping Microsoft Teams, Slack, DingTalk, and Lark Identities to Workday Worker OAuth](https://kiweely.com/blog/mapping-teams-slack-lark-sso-identities-to-workday-workers)
-   [How Workday’s Twice-Yearly Releases Break In-House MCP Servers and REST Integrations](https://kiweely.com/blog/how-workday-twice-yearly-releases-break-custom-mcp-servers)

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