Five questions before replacing a business system

1. What problem are you actually trying to solve?

A slow or unpopular system is not always the root cause. Map where work stops, duplicates or relies on manual correction before deciding the platform itself must be replaced.

2. Which integrations matter?

A replacement can fail operationally if surrounding systems, exports, imports or identity flows are treated as an afterthought.

3. What must stay the same?

Not every process should be redesigned at once. Separate essential continuity from improvements so the delivery scope remains manageable.

4. Who owns the data?

Clarify what data exists, where it is held, what quality issues are known and who is accountable for migration decisions.

5. What does good look like after launch?

Define measurable operating outcomes such as fewer manual steps, clearer reporting or reduced rework rather than treating go-live as the only measure of success.