---
title: "Object Transporter or Configuration Change Tracker: which…"
description: "Use Object Transporter to migrate selected objects and packages. Use Configuration Change Tracker when you need changes by user and time first."
url: https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker
---

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

-   **Checked** against Workday on November 17
-   Applies to **Workday Customer Central, Object Transporter, Configuration Change Tracker**
-   3 min read
-   Published November 17
-   By Kiweely

Object Transporter (OX) is the deployment tool that migrates configuration from one tenant to another. Configuration Change Tracker (Change Tracker) is the report that lists configuration changes by user and timeframe so you know what to package. You still finish the move in Object Transporter. The choice is whether you start from known instances or from a vetted change list.

## Side-by-side

| Question | Object Transporter | Configuration Change Tracker |
| --- | --- | --- |
| Primary job | Migrate selected instances, packages, security packages, extracts, catalog content, and Advanced packages | Report changes in a tenant for selected users and a date range |
| How you choose objects | You pick instances or package contents | You filter by From Moment, To Moment, users, and optional web service or REST change flags |
| Dependencies on migrate | Standard packages auto-include dependents of top-level objects | Advanced packages migrate only selected instances; OX does not add further dependents after migration starts |
| Best when | You already know the reports, calculated fields, or security objects to move | Several people changed a Sandbox and you need a safe sync of that window |
| Tabs / views | Pre-Migration Check, Pre-Migration Diff, Post-Migration Report | Ready to Migrate and Not Ready to Migrate |
| Customer Central tooling flag for Advanced packages | OX Migration: Full Object Coverage on Maintain Access to Customer Central Tooling | Same flag required before CCT packages migrate through OX |

## When to use Object Transporter alone

Use OX when Workday’s Object Transporter concept matches your case:

-   Single instances from a related action.
-   Configuration packages or security configuration packages.
-   Configuration Catalog content.
-   Translated values, X.509 private key pairs, or configuration extract `.dat` files.
-   Advanced packages that already exist from Change Tracker.
-   Security groups and their business process security policy permissions.

OX migrates top-level objects and their dependencies for standard packages. It does not migrate transactional or reference data. Example from Workday: migrating a custom report also migrates the calculated field it needs, but not the location that field references. Pre-Migration Check flags that location as a missing prerequisite.

Use Configuration Extracts only when you need to reuse the same configuration across environments with different Billing IDs, or save a copy to reload later. You cannot load configuration extracts to Production. Import to Implementation or Sandbox first, then OX to Production.

## When to start in Configuration Change Tracker

Use Change Tracker when you need the change list Workday describes: after Sandbox work, report changes during a date range, by selected users, including or excluding web service and REST changes. The report only returns changed instances that belong to a migratable implementation type. It can include up to 2 million configuration changes based on total tenant changes, not only the filtered set.

Ready to Migrate instances can go straight into an Advanced configuration package. Not Ready to Migrate covers deletions and problem cases such as missing reference IDs; those are omitted from the package unless you add them manually while configuring package instances. Workday says most Not Ready rows, such as Do Not Use or deleted instances, do not make sense to add.

Advanced packages are the safer sync path for populated tenants because OX migrates only the instances you selected. It does not pull in surprise dependents mid-migration the way a standard package can.

## Practical rule

1.  If you can name the objects, migrate with OX (single instance or package).
2.  If you can name the people and the time window, run Change Tracker, package Ready to Migrate, validate reference IDs, then launch OX.
3.  If you need Production and the path is blocked for your package type, check the migration path matrix before you rebuild the package.

## Frequently asked questions

### Does Change Tracker replace Object Transporter?

No. Change Tracker builds and prepares the Advanced package. Object Transporter performs the migration in Customer Central.

### Which tool audits better?

Change Tracker shows who changed what in a window, with View Changes audit trails on primary instances. OX adds migration history, Pre-Migration Diff, and Post-Migration reports. Use both when you need change discovery and migration evidence.

### Do I need special Customer Central access for CCT packages?

Yes. A Customer Central security administrator must select OX Migration: Full Object Coverage on Maintain Access to Customer Central Tooling for Configuration Change Tracker migrations.

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

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

-   [Why does a Workday EIB load fail, and how do you get a clean load the first time?](https://kiweely.com/blog/why-workday-eib-load-fails)
-   [Kiweely builds and runs a Workday Outbound EIB from one request](https://kiweely.com/blog/workday-outbound-eib-integration-built-and-run)
-   [How an admin sets up the Workday API client for Kiweely Bridge](https://kiweely.com/blog/kiweely-bridge-ai-admin-api-client-setup)

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