Step 5: Updating downstream applications and destinations

After validating and unifying your data, update the tools that consume event data so each one reads from Hightouch Events or your unified event tables. This is the final step of the migration.

It is possible to run this step in parallel with earlier validation to shorten the migration, but you may need to repeat some steps depending on any changes made during validation or unioning with historical data.

Before you cut over, make sure monitoring and alerts are in place so you catch volume drops, contract violations, or sync errors during the transition.

Re-check your inventory of downstream applications

In your planning, you likely created an initial list of applications consuming event data. Take this opportunity to review and update that list in light of the migration so far.

Make sure your list includes any systems, tools, and processes that consume your event data, including:

• Analytics platforms (for example, Google Analytics, Amplitude)
• Marketing and advertising tools (for example, Meta Ads, Google Ads)
• Customer engagement platforms (for example, Braze, Customer.io)
• Business intelligence tools (for example, Tableau, Looker)
• Custom internal dashboards and applications

Rank your downstream systems based on their criticality to your business operations to plan a phased approach to the updates if necessary.

Update data sources

For each downstream system:

1. Identify current data source: Determine how the system is currently receiving event data (for example, reverse ETL, streaming, or direct SDKs).
2. Update configurations or set up new syncs: Depending on the downstream tool, you might:
   • Create new or update existing Hightouch syncs
   • Set up or modify streaming destinations in Hightouch
   • Modify configurations in the downstream tool to point to the unified events data.
3. Verify data flow: Confirm that events are flowing correctly into the updated system.

Adapt to schema changes

If your migration to Hightouch Events involved changes to your event schema:

1. Document changes: Create a clear mapping between your old and new event schemas.
2. Update data models: Modify any data models or transformations in your downstream systems to align with the new schema.
3. Revise queries: Update SQL queries, API calls, or other data retrieval methods to reflect the new event structure.

Validate metrics and reports

For each updated system:

1. Reconcile key metrics: Compare critical metrics between the old and new data sources to ensure consistency.
2. Update dashboards: Revise any dashboards or standard reports to use the new data source and schema.
3. Cross-check historical data: Verify that historical data is accurately represented in updated reports.

Handle data discrepancies

If you encounter differences between your old and new systems:

1. Investigate root causes: Determine if differences are due to improved data collection, schema changes, or potential issues.
2. Document explanations: For any persistent differences, document the reasons and communicate these to stakeholders.
3. Adjust baselines: If necessary, establish new baselines for key metrics based on the new data from Hightouch Events.

Manage the transition period

If you're executing your migration in a linear fashion, you'll carry out this work as a whole after validating and confirming your new event data and cutting off your prior event collection tool.

However, if you're gradually shifting traffic over to Hightouch Events, you might decide to start transitioning downstream applications to use the new data at the same time and run in parallel with your prior tool and historical. If you do so, have a clear date planned for switching all downstream applications over to Hightouch events data and communicate changes to stakeholders as you transition.

Gather feedback from users

As teams start working with the new event data, gather their feedback and refine your collection and activation setup. Early questions often surface schema or mapping gaps that are easier to fix before you turn off your previous provider.

Turn off your previous provider

Once you're confident in your Hightouch Events setup, you can begin sunsetting your previous provider. We recommend the process below.

1. Gradual cutover: Incrementally increase the proportion of traffic sent only to Hightouch Events.
2. Monitor closely: Watch for any unexpected changes in data patterns or downstream system behavior.
3. Final switch: When ready, update your tracking code to send events only to Hightouch Events. With a wrapper function, this is a one-line change.
4. Decommission old system: Follow your previous provider's instructions for account closure and data handling.

This step completes your migration. Review your event data flow regularly afterward to keep data quality and downstream consumers in good shape as your tracking plan changes.

What's next

Your collection now runs on Hightouch Events. Keep these running to maintain data quality and activate your events:

• Data contracts — enforce your event schema and catch violations as your tracking plan evolves.
• Monitor events — keep volume, violation, and sync alerts running.
• Troubleshoot events — diagnose missing events, blocked events, or unexpected warehouse columns.
• Build audiences in Customer Studio — activate your event data downstream.

For the complete set of building blocks that make up an Events implementation, see Plan your implementation.