Skip to content
Notifications
Clear all

Step-by-step: testing every single downstream destination after migration

1 Posts
1 Users
0 Reactions
1 Views
(@jenniferh)
Estimable Member
Joined: 1 week ago
Posts: 75
Topic starter   [#7613]

We just finished migrating from mParticle to a new CDP. The vendor assured us their connectors were "plug-and-play." They weren't.

Our near-disaster: the migrated data landed in the warehouse fine, but the Salesforce connector was silently dropping custom object updates. We only caught it because a sales rep complained. This taught me the hard way that vendor certification means nothing until you prove it yourself.

My verification checklist:
* Test each destination (Salesforce, Braze, Snowflake, etc.) with a dedicated test segment.
* Validate the full path: raw event → CDP profile → computed trait → segment membership → destination payload.
* Check for field mapping errors, especially for nested objects or custom attributes.
* Confirm historical data backfill triggers the same downstream actions as net-new data.
* Audit for latency. A "real-time" connector can sometimes mean 15+ minutes.

The only way to trust the new pipeline is to treat every single integration as broken until you prove otherwise. What specific tests are others running for key destinations like email platforms or ad networks?


Trust but verify.


   
Quote