JPMorgan Chase · Data Owner · 2026
Alerts 2.0 Migration
Migrating the bank's alert preferences application from a legacy platform to Alerts 2.0, including a new database and an entirely new data pipeline.
Context
The alert preferences application stores how customers choose to receive alerts and notifications from Digital Communications, a product that sends more than 5 billion of them to customers across the bank. The application was moving from a legacy system to the new Alerts 2.0 platform, and its data had to keep flowing to downstream consumers throughout the move.
My role
As data owner, I worked closely with the product, technology and data technology teams to plan and run the transition, making sure the data side moved in step with the application.
What we did
- Application database: moved the application from its legacy database to CockroachDB.
- New pipeline: built a new pipeline from the ground up to move data from CockroachDB into the AWS S3 data lake, and from the data lake into Snowflake.
- Testing: took part in every stage of testing, validating that data in the new platform, the data lake and Snowflake was complete and correct.
- Collaboration: coordinated across teams on requirements, sequencing and sign-off for a smooth cut-over.
Outcome
Alert preference data now flows from Alerts 2.0 to the data lake and Snowflake through a single, modern pipeline, ready for analytics and reporting.