Migration scenario
Demo Rivers Health (DRH): All Age MH Access moves from Legendary Care to PathwayOne while reporting shifts to DemoRivers Cloud DWH.
What I hope to achieve
Migration reporting risk register, must-not-fail report list, fallback routes, feed cutover clarity, and protected local performance products during parallel running.
My approach to succeed
Map phases explicitly — parallel running is not the same event as feed discontinuation. Track risks with owners; reconcile while both worlds exist.
Phased timeline — parallel run vs feed cutover
| Phase |
When |
Legendary Care |
PathwayOne |
Performance experience |
| A Old only | Sep–Nov 2025 | System of record | Pilot only | Single definition world |
|---|
| B Parallel | Dec 2025 – Jan 2026 | Both feeds active | Rolling go-live | Dual-world reconciliation risk |
|---|
| C Referral cutover | 1 Feb 2026 | Weekly referral feed stops | New access only | Dashboard may still refresh |
|---|
| D Extract tail | Feb–Mar 2026 | Open cases only | System of record | Definition crunch — Mar reporting |
|---|
| E Legacy ends | 31 Mar 2026 | Extracts stop | Sole source | Embed agreed definitions |
|---|
| F New only | Apr–May 2026 | History in warehouse | Primary | Agreed logic from actions |
|---|
feed_cutover_log.csv
Migration reporting risk register (extract)
| ID | Risk | Owner | Mitigation |
|---|
| R001 | Definition drift during parallel run | Performance lead | Agreed KPI register |
| R002 | Dashboard refreshes with wrong meaning | BI lead | Reconciliation + confidence flags |
| R003 | Referral feed discontinued Feb | IM&T | Feed cutover log |
| R005 | MHSDS-like uses legacy logic | Mandatory reporting owner | Side-by-side test |
Full risk register · Reporting assurance deliverable · Definition migration centrepiece