---
title: "How do I build a Configuration Change Tracker package by…"
description: "Run Change Tracker with From Moment, To Moment, and users, package Ready to Migrate, validate IDs, then migrate with Object Transporter."
url: https://kiweely.com/guides/workday-configuration-change-tracker-how-to
---

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

-   **Checked** against Workday on November 17
-   Applies to **Workday Configuration Change Tracker**
-   3 min read
-   Published November 17
-   By Kiweely

Configuration Change Tracker reports configuration changes in a tenant for the users and timeframe you select, then lets you turn that list into an Advanced configuration package and migrate it with Object Transporter. Workday positions it as the easy, safe way to synchronize changes made by specific people in a window.

## Prerequisites

1.  Maintain Access to Customer Central Tooling set up for Advanced package migration, including OX Migration: Full Object Coverage.
2.  Customer Central Object Transporter access configured.
3.  Configuration Change Tracker security domains assigned (auditor and packager as needed). See Configure Security for Configuration Change Tracker.
4.  Sign in to the tenant that holds the changes you want to sync.

## Build the change list

1.  Open the Configuration Change Tracker task.
2.  Set report criteria:

| Option | What to enter |
| --- | --- |
| From Moment / To Moment | Date and time range for the changes |
| Filtered by Users | One or more users who made the changes |
| Include Changes Made via Web Services | Check if any selected user changed config through SOAP web services |
| Include Changes Made via REST | Check if any selected user changed config through REST |

1.  Optional: filter by implementation type under Additional Filters, or open an existing saved report.
2.  Run or refresh until the report populates. Workday saves it as a Configuration Change Tracker report.
3.  Review Ready to Migrate versus Not Ready to Migrate. Use View Changes on a primary instance when you need the audit trail.

Ready to Migrate can be packaged without further edits. Not Ready to Migrate is omitted from the package unless you add rows manually later. Deleted or Do Not Use instances usually stay out.

## Create the Advanced package

1.  Click Create Configuration Package for Ready to Migrate instances.
2.  Rename, describe, or add an external change request ID if you track approvals outside Workday.
3.  Choose instance filter:

| Option | Result |
| --- | --- |
| All Instances (default) | Everything on Ready to Migrate |
| New Instances Only | Only instances created in the window by the selected users |
| Modified Instances Only | Only instances edited in the window by the selected users |

1.  Configure Package Instances to add or remove instances or implementation types. Add a Not Ready row here only when you have a deliberate reason.
2.  On Review and Prepare for Migration, run:
    -   Blank Reference IDs, then View and Fix Errors when Workday can populate blanks.
    -   System Generated Ref IDs, and rename only when you fear overwrite or accidental create on the target.
    -   Exception Audits: Calculated Field Exception, Custom Report Exception, Report Specific Calculated Field Exception, Worklet Mappings Exception.
3.  Prepare for Migration. Workday redirects you to Customer Central.
4.  Launch Object Transporter. Advanced packages use manual dependency behavior: OX does not auto-add dependents after migration starts. You may add dependents later if Pre-Migration Diff reports them missing.

## Migrate

Complete the Object Transporter flow: Include Translations if needed, resolve Pre-Migration Check (first 50 prerequisites at a time), review Pre-Migration Diff, set effective dates, choose Merge or Override for differing security policies, then Start Migration. Keep the Post-Migration report (retained 2 years).

## Limits to remember

-   Change Tracker reports only migratable implementation types. Instances without an implementation type do not appear and will not migrate.
-   Reports can include up to 2 million configuration changes based on total tenant changes.
-   Change Tracker reports direct object changes, not behavioral side effects. Example: a calculated field change that also affects a condition rule reports the calculated field only.

## Frequently asked questions

### Who can see whose reports?

Self auditors see and create their own reports. Global auditors can view others’ reports. Packaging needs the matching packager domain. Details are on Configure Security for Configuration Change Tracker.

### Why is my deletion on Not Ready to Migrate?

Workday lists deletions and other risky rows on Not Ready to Migrate and excludes them from the automatic package. Add them manually only when you intend to migrate that risk.

## Sources checked

-   [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 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)
-   [Configure Security for Configuration Change Tracker](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/configuration-change-tracker/configure-configuration-change-tracker-security.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)
-   [### Configuration Change Tracker Restricted vs Global auditor and packager Workday splits Configuration Change Tracker access into Restricted (self) and global domains. Auditors need View and Modify on the Change Management domain. Packagers need the Migrations domain. A user who creates Advanced packages needs both an auditor and a packager domain.](https://kiweely.com/guides/workday-cct-restricted-vs-global-packager-security)
-   [### How do I limit a Configuration Change Tracker package to a change window? Time-bounded CCT packages start with From Moment and To Moment, then Filtered by Users. Narrow further with New Instances Only or Modified Instances Only when you create the Advanced package. Advanced packages migrate only selected instances, so the window you choose is the window you ship.](https://kiweely.com/guides/workday-configuration-change-tracker-time-bounded-packages)
-   [### 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)

### More guides on More Workday guides

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

-   [Do You Need a Workday AMS Partner, or Can a Small In-House Team Run Workday?](https://kiweely.com/guides/workday-after-go-live-in-house-team)
-   [Workday Implementation Cost, November 2026: Public Ranges, Rates and Budget Splits, Dated](https://kiweely.com/guides/workday-implementation-cost)
-   [Set the Workday HCM foundation before you automate it](https://kiweely.com/guides/ai-workday-foundation-data-model)
-   [How Workday Data Conversion Works, and Why It Takes So Many Loads](https://kiweely.com/guides/ai-workday-data-conversion-mapping)
-   [Pre-Hire Windows That Create Directory Users Before Anyone Is Hired](https://kiweely.com/guides/pre-hire-windows-that-create-directory-users-early)
-   [Why Workday to Microsoft Entra Incremental Sync Misses Changes](https://kiweely.com/guides/why-workday-to-entra-incremental-sync-misses-changes)
-   [Remap Workday Benefit Codes When a Carrier Companion Guide Changes](https://kiweely.com/guides/remap-workday-834-codes-after-companion-guide-change)
-   [Full File or Changes-Only 834 After Workday Open Enrollment](https://kiweely.com/guides/workday-834-full-file-or-changes-only-after-open-enrollment)

### From the blog on More Workday guides

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

-   [Are there open-source Workday MCP servers on GitHub, and can you use one?](https://kiweely.com/blog/open-source-workday-mcp-servers-github-reviewed)
-   [Claude, ChatGPT and Gemini with Workday: every option compared (November 2026)](https://kiweely.com/blog/claude-chatgpt-gemini-workday-options-compared)
-   [How to secure a Workday MCP server: four gates, a yes before every change, and the teams it takes](https://kiweely.com/blog/secure-workday-mcp-server-four-gates)

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