Incremental Migration for Large Campaign Sets

For large campaign sets, run the Migration Application in smaller, non-overlapping batches by changing siebel.campaign.searchspec for each run. This reduces the size of each run and makes validation and rerun handling easier.

Batch Option	Example	When to Use
Name prefix	Name LIKE 'Customer Demo*'	Demo or planned migration waves that use a shared campaign naming prefix.
Name sub-prefix	Name LIKE 'Customer Demo - A*'	Split a large named set into smaller alphabetical batches.
Created date window	Created >= '05/01/2026' AND Created <= '05/31/2026'	Partition campaigns by creation period.
Created-by owner	Created By Name = 'SADMIN'	Migrate campaigns owned or created by a specific user.
Explicit small subset	(Name = 'Customer Demo - Spring Loyalty Outreach' OR Name = 'Customer Demo - Winback Engagement')	Retry or validate a small known group.
Combined scope	Created By Name = 'SADMIN' AND Name LIKE 'Customer Demo*'	Narrow a large prefix or owner set.
Status-based scope	Status = 'Planned', Status = 'Active', or Status = 'Completed'	Use only if those campaign status values are present in the target environment.

Keep explicit OR lists short. For large campaign sets, use campaign name prefixes, creation date ranges, campaign owners, or verified status values to partition the migration into smaller batches. Because each migration run is stateless, each subsequent run evaluates the current Siebel and OAS state for the campaigns returned by the configured search specification.