Migration Architect Playbook
Discovery
- Estate inventory complete
- Business owners identified
- Dependencies mapped
- Data volumes and SLAs measured
- Security requirements captured
Strategy
- Target pattern selected per workload
- BW bridge suitability assessed
- Native Datasphere redesign candidates identified
- BDC integration options considered
- Coexistence model defined
Engineering
- Source connectivity validated
- Delta strategy proven
- Semantic mapping documented
- Performance benchmark completed
- Security equivalence tested
- Operational monitoring implemented
Cutover
- Reconciliation thresholds approved
- Business acceptance complete
- Rollback technically tested
- Cutover owner and timeline confirmed
- Hypercare plan ready
Retirement
- Consumers migrated
- Interfaces removed
- Jobs disabled
- Retention obligations satisfied
- Legacy access removed
- Architecture catalog updated
Interview questions
- When would you choose BW bridge instead of native Datasphere?
- When should a BW workload be rebuilt rather than converted?
- How do you prove semantic equivalence?
- How do you design coexistence without creating permanent duplication?
- What are your objective rollback triggers?
- What evidence allows you to decommission the legacy platform?
Architect principle: migrate business capability, not objects.