---
title: "How do I limit a Configuration Change Tracker package to a…"
description: "Set From Moment and To Moment, filter users, optionally select New or Modified only, and keep Advanced packages free of unvetted dependents."
url: https://kiweely.com/guides/workday-configuration-change-tracker-time-bounded-packages
---

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

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

A time-bounded Configuration Change Tracker package is how you migrate “what changed in this window” without sweeping the whole tenant. Workday’s migrate topic centers on From Moment, To Moment, and Filtered by Users. The Advanced package that follows migrates only the instances you keep, without Object Transporter auto-adding extra dependents after migration starts.

## Set the window before you package

1.  Open Configuration Change Tracker on the source tenant.
2.  Enter From Moment and To Moment for the change window you verified in testing.
3.  Select Filtered by Users for everyone who built in that window. Omit shared service accounts you did not intend to include unless their automated changes belong in the package.
4.  Check Include Changes Made via Web Services or Include Changes Made via REST only when those channels were used. Leaving them unchecked shrinks noise from unrelated API activity.
5.  Optional Additional Filters by implementation type when the window mixed HCM reports with finance config and you are shipping only one area.
6.  Run the report and read Ready to Migrate versus Not Ready to Migrate before you create anything.

Concept: Configuration Change Tracker’s Sandbox example is exactly this pattern: after verifying Sandbox changes, report the date range and users, then migrate.

## Narrow inside the package

When you create the Advanced configuration package, Workday offers three inclusion modes:

| Mode | Use when |
| --- | --- |
| All Instances | You want every Ready to Migrate row from the report (default, prior behavior) |
| New Instances Only | The window should ship creates, not edits to older shared objects |
| Modified Instances Only | The window should ship edits, not brand-new instances another stream owns |

Workday added this filtering so you can synchronize tenants without manually carving huge packages afterward. Prefer New or Modified when All Instances would drag in objects that merely sat in the same report.

After the package exists, Configure Package Instances is your last manual trim. Remove implementation types that rode along. Add a Not Ready row only with intent.

## Why Advanced packages keep the bound tight

For Advanced packages from Change Tracker, Object Transporter migrates only selected instances. It does not add other dependent instances after migration starts, unlike standard configuration packages. That is the control that makes a time window meaningful: dependents discovered later appear in Pre-Migration Check or Diff for you to resolve, rather than silently expanding the ship set.

Still run Blank Reference IDs, System Generated Ref IDs, and Exception Audits before Prepare for Migration. A clean window with broken Reference IDs still fails on the target.

## Avoid over-collecting

| Over-collect cause | Prevention |
| --- | --- |
| From Moment set days earlier than the real build | Align moments to the tested change window |
| Every implementer selected “just in case” | Filter to the users who touched the objects |
| Web service and REST includes left on by default habit | Enable only when those users changed config that way |
| All Instances on a report that mixed creates and churn | Use New or Modified Only |
| Standard OX package instead of Advanced CCT package | Stay on Advanced when you need no auto-added dependents |
| Behavioral side effects expected in the report | Change Tracker reports direct changes only; related condition rules may not appear |

Change Tracker can include up to 2 million configuration changes based on total tenant changes. A wide window on a busy tenant produces a report that is hard to vet. Smaller windows are easier to approve.

## Frequently asked questions

### Can I reuse a saved report for the next window?

Yes. Workday lets you select an existing report, but update From Moment and To Moment for the new window or you will package stale rows.

### Does the time filter apply after I add Not Ready instances manually?

The report criteria define the starting list. Manual adds on Configure Package Instances are deliberate exceptions outside that automatic filter. Document them in the package description or external change request ID.

### Is a time-bounded CCT package safer than selecting one report in OX?

Safer for multi-user Sandbox sync because you see who changed what, and Advanced packages do not auto-expand dependents. If you already know a single instance, related-actions OX is enough.

## 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)
-   [Concept: Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/omh1634567473070.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)
-   [### 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)
-   [### 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)

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

-   [Employee Workday Q&A in ChatGPT without oversharing](https://kiweely.com/blog/employee-workday-qa-in-chatgpt-without-oversharing)
-   [What drives Workday HCM vs Financials implementation duration?](https://kiweely.com/blog/workday-hcm-vs-financials-implementation-drivers)
-   [Why Do Workday Implementations Run Late or Over Budget? Each Cause, and How to Prevent It](https://kiweely.com/blog/workday-implementation-late-over-budget)

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