The starting point
I use dependency analysis to examine versions, components and system connections. We record which technology constraints need to be addressed and which behavior must be preserved.
02 / WORKING TOGETHER
How the work proceeds
Comparing options
I consider total cost of ownership (TCO) and migration risk. I assess the Strangler Fig pattern for incremental replacement, allowing the system to be modernized piece by piece.
The target architecture
I use the C4 model to clarify system boundaries, key application components and connections. The target architecture reflects load, security and operational requirements.
Planning the migration
I plan regression testing for each migration step to verify existing behavior. I define the conditions for proceeding and a rollback plan in case the change causes problems.
I choose the migration approach to suit the system and business constraints. With developers and operations staff, I clarify testing options, data migration and acceptable downtime.
03 / DELIVERABLES
What do you receive, and how can you use it?
- Technical assessment: what can be retained and where intervention is needed.
- Comparison of alternatives: evaluate further development, incremental replacement and a rewrite.
- Target architecture and dependencies: the team can review the planned behavior and migration risks.
- Phased migration plan: agree steps, checks and rollback conditions.
Your development team or supplier can implement the plan. By separate agreement, I can support the work through technical reviews, decision support or focused prototypes.
04 / GETTING STARTED
What is needed to get started?
- The business objective, deadline and known constraints of the change
- System documentation and specialists familiar with the technical details
- Operational and integration requirements
- Decision-makers involved in evaluating the main options
05 / FREQUENTLY ASKED QUESTIONS
Frequently asked questions
How long does planning take?
Typically 2–8 weeks, depending on system size and the required level of detail.
When is a rewrite justified?
It may be justified when extending the existing system would involve greater risk and effort. I assess this against the system's condition, business objectives and migration options.
Can our existing supplier work from the plan?
Yes. The plan records the technical direction, task dependencies and acceptance criteria so that both the internal team and suppliers can use it.
Can you also help with implementation?
Planning is a standalone engagement. By separate agreement, I can support implementation through technical reviews, decision support or focused prototypes. We agree roles and availability in advance.