Data CloudExpertmigrationcdpcutover
Plan migration from legacy CDP to Data Cloud with parallel run
Real World Scenario
Enterprise runs Adobe CDP and new Data Cloud contract; CMO wants Big Bang cutover in 90 days without losing active journeys.
Expected Answer
• Parallel run period with segment parity validation metrics
• Identify journey dependencies on legacy segment APIs early
• Migrate identity rules first — segments second — activations last
• Freeze new legacy CDP use cases during migration window
• Rollback plan with legacy segments maintained read-only
• Staff training on new segment builder before cutover
• Success criteria: match rates, activation volumes, campaign KPIs within tolerance
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Parallel run period with segment parity validation metrics Also consider: Identify journey dependencies on legacy segment APIs early In practice: Migrate identity rules first — segments second — activations last Validate against production-scale constraints and long-term platform evolution.
Architect Perspective
CDP migration fails on journey dependencies not data pipes — map activations before ingestion sprints.