1. Decide what you are moving, and why
Start with the reason: a new platform, a licence bill, a stalled build or a regulator’s deadline. The reason decides what “done” means.
List every report, extract and feed that depends on the old warehouse. Mark the ones with a fixed due date, because they set your cut-over window.
2. Map sources and find the gaps
For each source, record the fields you use, how they are defined and who owns them. Look for fields the old warehouse derived that the new one will not.
- A field map from old to new
- A list of gaps and who will fill them
- A short list of reports that must not change
3. Move history from raw data
Backfill from raw data where you can, so the history can be replayed if a definition changes. Decide how much history you need. Full history takes longer and costs more than a partial backfill.
4. Run in parallel and reconcile
Run the new system next to the old one. Compare balances and totals every day. Differences are normal at first. What matters is that each one is explained.
Agree a tolerance with finance before you start, and write down how each difference was resolved.
5. Plan the cut-over and the way back
Pick a quiet period away from reporting deadlines. Test the rollback before you need it. Decide who can call it off, and by when.
6. Validate, then retire the old system
Re-run a period of reports on the new system and have the owners sign them off against the old numbers. Keep the old warehouse read-only for an agreed time, then switch it off.