Phase F: Migration Planning

This phase addresses migration planning. In the Phases B,C and D, we identified the Baseline and Target Architectures. In Phase E, we identified possible ways of doing this. In this Phase, we finalize on a detailed plan of how we can do this. Here, we define and finalizing a detailed Implementation and Migration Plan.


The objective of this phase is to finalize the Architecture Roadmap and the supporting Implementation and Migration Plan. We have been updating the draft roadmap since the Phase B. This phase finalizes it. Along with that , we ensure that the Implementation and Migration Plan is coordinated with the enterprise’s approach to managing and implementing change in the enterprise's overall change portfolio.

And of course, we should never forget the stakeholders. An important objective of this phase is to ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders


In order to achieve this, the TOGAF Standard recommends the following steps

  • Any enterprise defines a management framework. We should have precisely defined points of interaction between the architecture framework and the management framework. This defines how the management will interact with the architecture development team. This is detailed in this phase.
  • Until it is finally deployed (or even after it is deployed), each line of code has to justify its existence. When we talk of implementation of an enterprise architecture, each work package in the process should clearly justify what business value it is going to add. This phase has to identify such a mapping of a work package and its business value.
  • Cost is the final bottleneck for any activity. Once we have identified the business value of each work package we plan to implement, we need to estimate its cost in terms of the resource requirements, project timings, and availability/delivery vehicle
  • For a precise and efficient planning, next step should be to prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation
  • Based on all this evaluation, we should now confirm the Architecture Roadmap and update Architecture Definition Document
  • Now, we can finalize the Implementation and Migration Plan for the enterprise architecture.
  • This phase marks the end of the architecture development cycle. This calls for a retrospection. We should clearly document lessons learnt in the process - that could be used in the future iterations.


Like the other phases we have seen, the inputs to this phase are the outputs of the previous phases, along with some generic inputs from the enterprise as a whole.

  • Request for Architecture Work (Preliminary Phase)
  • Organization Model for Enterprise Architecture (Preliminary Phase)
  • Governance Models and Frameworks
  • Tailored Architecture Framework (Preliminary Phase, Phase A)
  • Communications Plan (Phase A)
  • Statement of Architecture Work (Phase A)
  • Architecture Vision (Phase A)
  • Architecture Repository
  • Draft Architecture Definition Document, including Transition Architectures, if any (Phase B-E)
  • Draft Architecture Requirements Specification (Phase B-E, H)
  • Architecture Roadmap (Phase E)
  • Capability Assessment, including Business & IT Capability (Phase E)
  • Implementation and Migration Plan (outline), including High-level Implementation and Migration Strategy (Phase E)
  • Change Requests for existing programs and projects


This phase provides us all that we need to jump into the implementation

  • Implementation and Migration Plan (detailed), including:
    • Implementation and Migration Strategy
    • Project and portfolio breakdown of the implementation
    • Project charters (optional)
  • Finalized Architecture Definition Document, including the Finalized Transition Architectures, if any
  • Finalized Architecture Requirements Specification
  • Finalized Architecture Roadmap
  • Re-usable Architecture Building Blocks
  • Requests for Architecture Work for a new iteration of the ADM cycle (if any)
  • Implementation Governance Model
  • Change Requests for the Architecture Capability arising from lessons learned

This is the final phase before we start implementing. We finalize all the architecture documents that we had started and populated in the previous phases. We define the individual architecture blocks that will be realized in the implementation phase. We push aside for the next ADM cycle, the things that may not be feasible this time. And we define the strategy, breakdown, plan and the governance model that will be used while implementing.

Phase E and Phase F might seem similar to each other. But there are some subtle differences. The focus in phase E is in identifying what and how it can be implemented - splitting in terms of components and building blocks. The focus in phase F is on the process of moving from baseline to target.