← Graph

How to migrate legacy data into an event-sourced system?

question 2 connections

Audience member (commercial real-estate company) asks how to handle migrating data from decades-old legacy systems where the good domain signal is already lost. Garofolo: build the new model first, then map legacy data to it by emitting synthetic events like 'legacy foo imported' as the start of each new stream. A dedicated legacy event type lets you distinguish old from new data. The original domain events are gone — like a lossy compression — so you make the best of what you have while still getting pub/sub benefits.

answer_summary
Build the new domain model first, then seed new streams with 'legacy imported' events. The original domain signal is lost, but a distinct event type preserves provenance and pub/sub benefits still accrue.
question How to migrate legacy data into an event-sourced system?
about
Event Sourcing concept
Question is about seeding new event streams with legacy data.
question How to migrate legacy data into an event-sourced system?
asked_at
Asked in Q&A after the talk by an attendee from a commercial real-estate company.

Provenance

Read by
4 extractions