Clear all

Bridging data between legacy and next-gen systems

Posts: 4
Topic starter
New Member
Joined: 11 months ago

What is best practice for warehousing use case of:

  • records for core business entities being migrated to new system - e.g., "contracts"
  • not *all* contracts will be migrated to new system
  • reporting will need to retain continuity between the historical un-migrated contracts (which will remain static after a go-live cutover to new system) and the contracts migrated to the new system, along with any *new* contracts generated in the new system

Thus far, the thought is that this entity will be modeled with a common hub, but separate satellites.

As far as merging or UNION-ing these datasets together for reporting, I'm supposing this needs to be deferred to the DataMart layer, or perhaps a view on top of the DataVault?

Is there an ideal point at which to marry entities such as this together within the overall context of the end-to-end warehousing and reporting solution?

Again, legacy data will become static, while the records translated into the new system will be "living" records - but the complete set of business keys is the composite between legacy and next-gen systems.


3 Replies