Phase F: Migration Planning

Finalize the roadmap and produce a costed, sequenced Implementation and Migration Plan agreed with the wider portfolio.

About this phase

Phase F finalizes the Architecture Roadmap and turns the outline plan from Phase E into a detailed Implementation and Migration Plan, coordinated with the enterprise's portfolio, program, and project management frameworks.

The phase assesses the business value, cost, and risk of each work package; prioritizes migration projects; assigns resources and timings; and confirms the plan with the stakeholders who will fund and deliver it. Nothing should be in the plan that the delivery organization has not agreed to.

Phase F also closes the architecture development cycle for this iteration: the Architecture Definition Document, Requirements Specification, and Roadmap are completed, lessons learned are documented, and the baton passes to implementation governance in Phase G.

Objectives

Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan.
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.
Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders.

Steps in this phase

0/7 · 0%

1.Confirm management framework interactions for the Implementation and Migration PlanCoordinate with business planning, portfolio/project management, and operations management frameworks so the plan lands inside existing enterprise processes.
2.Assign a business value to each work packageEstablish business value using techniques such as the Business Value Assessment; agree performance measures with stakeholders.
3.Estimate resource requirements, project timings, and availability/delivery vehicleEstimate effort, cost (capital and operational), and timing for each project; identify the delivery vehicle (project/program).
4.Prioritize the migration projects through cost/benefit assessment and risk validationRank projects by net benefit and validated risk; confirm priorities with stakeholders.
5.Confirm the Architecture Roadmap and update the Architecture Definition DocumentFinalize the roadmap (e.g., using an Architecture Definition Increments table) and update the ADD, including Transition Architectures.
6.Complete the Implementation and Migration PlanIntegrate all projects, dependencies, resources, and schedules into the finished plan within the enterprise's portfolio framework.
7.Complete the architecture development cycle and document lessons learnedClose this iteration of architecture development, hand deliverables to governance, and record lessons learned for the next cycle.

Key inputs

Request for Architecture Work, Statement of Architecture Work, Architecture Vision
Communications Plan and Capability Assessment
Organizational Model for Enterprise Architecture and Tailored Architecture Framework
Governance models and frameworks
Architecture Repository
Draft Architecture Definition Document, including Transition Architectures
Draft Architecture Requirements Specification
Architecture Roadmap v0.1 and Implementation and Migration Plan v0.1 (from Phase E)

Key outputs

Implementation and Migration Plan v1.0 (detailed, approved) — including the Implementation and Migration Strategy and project charters as appropriate
Finalized Architecture Definition Document — including finalized Transition Architectures
Finalized Architecture Requirements Specification
Finalized Architecture Roadmap
Reusable Architecture Building Blocks stored to the Architecture Repository
Requests for Architecture Work for a new iteration of the ADM cycle (if any)
Implementation Governance Model (produced with Phase G in view)
Change Requests for the Architecture Capability arising from lessons learned

Worked example — Meridian Retail Group

Generated sample documents for a fictional company, showing what this phase consumes and produces. They are illustrative study aids, not templates from the standard.

Example inputs

PFrom Preliminary Phase

AFrom Phase A: Architecture Vision

BFrom Phase B: Business Architecture

CFrom Phase C: Information Systems Architectures

DFrom Phase D: Technology Architecture

EFrom Phase E: Opportunities and Solutions

RMFrom ADM Architecture Requirements Management

Prepared for this phase

example inputDeliverablefrom PreliminaryThe document from the sponsoring organization that triggers an ADM cycle — the key handoff from the Preliminary Phase into Phase A.

Request for Architecture Work

Sponsoring organization: Meridian Retail Group — Office of the COO Date: 2 April 2026 Reference: RAW-2026-001 Addressed to: Architecture Board (submitted via the Lead Architect)

Organization sponsors

Chief Operating Officer (business sponsor); Chief Information Officer (executive sponsor for architecture).

Mission statement

Deliver the "One Meridian" unified customer experience: any customer, recognized in any channel, served from a single view of orders, inventory, and preferences.

Business goals and changes

Increase repeat-purchase rate from 31% to 40% within 24 months
Enable buy-online-pickup-in-store (BOPIS) in all 240 stores
Consolidate 4 customer databases into a governed single customer view
Reduce integration spend by 20%

Strategic plans

Responds to the One Meridian strategy (FY26–FY28) and Board Directive 26-04. Goals map to drivers DRV-01 to DRV-04 in the Driver/Goal/Objective catalog.

Time limits

Architecture definition (Target Architecture and roadmap) approved before the 1 Nov 2026 peak trading freeze
First Transition Architecture in production before the FY27 peak freeze

Changes in the business environment

Competitors now offer click-and-collect as standard; digital revenue at 26% and rising; POS v9 reaches end of life in 2027.

Organizational constraints

Peak trading freeze: no production change 1 Nov – 15 Jan
Franchise stores operate their own POS until contract renewal (FY27)

Financial constraints

Indicative program envelope of $18M over 2 years, subject to Investment Committee approval per tranche.

External and business constraints

GDPR and PCI-DSS compliance mandatory
3PL logistics contract fixes EDI message formats until 2027

Current business system description

Channel-based operating model: Digital Commerce, Store Operations, and Customer Care each run their own customer processes and service standards.

Current systems description

4 customer databases, 3 order management systems, in-store POS (v9, EOL 2027), monolithic e-commerce platform, nightly-batch warehouse integration.

Developing organization and resources available

Meridian EA team (Lead Architect plus 4 domain architects), working under the Tailored Architecture Framework v1.0 and Architecture Principles v1.0. Business subject-matter experts released for up to 2 days per week during Phases B–D.

Success criteria

An approved Target Architecture and Implementation and Migration Plan for the One Meridian program, with the first Transition Architecture delivered before the FY27 peak trading freeze.

Submitted by: COO, 2 April 2026 · Accepted for Phase A: Architecture Board, 9 April 2026

Study notes

Used in: Step 3: Estimate resource requirements, project timings, and availability/delivery vehicle · Step 6: Complete the Implementation and Migration Plan · Step 7: Complete the architecture development cycle and document lessons learned

The indicative $18M envelope, 'subject to Investment Committee approval per tranche', is the budget the costed plan is tested against. Plan v1.0 totals $18.3M and records why the $0.3M variance was accepted.
The success criteria (an approved Implementation and Migration Plan, with the first Transition Architecture live before the FY27 peak freeze) are exactly what Phase F has to deliver before the cycle can close in step 7.
Constraints recorded here become hard scheduling rules in step 3: no production change from 1 Nov to 15 Jan, and franchise stores only after the FY27 contract renewal, which puts them in P7's final wave.

Example outputs

example outputDeliverableThe finalized, costed, and sequenced plan integrated with the enterprise portfolio.

Implementation and Migration Plan v1.0 — One Meridian (excerpt)

Approved: Architecture Board + Investment Committee, 28 Oct 2026 Owner: J. Okafor (Lead Architect) with Head of PMO · Supersedes: v0.1 (Phase E)

1. Implementation and Migration Strategy (confirmed)

Evolutionary change through three Transition Architectures (TA-0, TA-1, TA-2) to the FY28 Target. Each project is chartered through the PMO (charters PC-P1 to PC-P7) and runs inside the existing stage-gate model. No production change in the peak freeze (1 Nov – 15 Jan).

2. Project portfolio and schedule

Project (delivery vehicle)	Work packages	Start	End	Cost est.	Business value (score /25)	Priority
P1 Platform Foundation (program: Digital Core)	WP-08, WP-11	Nov 2026*	Feb 2027	$2.8M	14 (enabler)	1
P2 Integration Migration wave 1	WP-06a	Jan 2027	Mar 2027	$0.9M	12	2
P3 Customer Foundation	WP-10, WP-01, WP-04	Feb 2027	Jun 2027	$4.6M	21	1
P4 One-step Returns	WP-03	May 2027	Jul 2027	$0.8M	18	2
P5 Commerce Core	WP-05, WP-02, WP-04b	Apr 2027	Oct 2027	$5.1M	23	1
P6 POS Pilot (20 stores)	WP-07a	Jun 2027	Oct 2027	$1.7M	15	2
P7 POS Rollout + decommission	WP-07b, WP-06b	Jan 2028	Sep 2028	$2.4M	16	3

* P1 cloud-side work only during freeze — no store or production-commerce change.

P2 starts after the freeze lifts (18 Jan 2027). P4 goes live with TA-1 on 28 Jun 2027; July is hypercare and completion of store training. WP-09 (store network and PCI segmentation) is delivered by the Store Estate Refit program from its existing capex line and is tracked here as an external dependency.

3. Funding tranches

Tranche	Projects	Value	Release condition
T1	P1–P4	$9.1M	Approved 28 Oct 2026
T2	P5–P6	$6.8M	TA-1 acceptance evidenced (Jun 2027)
T3	P7	$2.4M	TA-2 acceptance evidenced (Oct 2027)

Total $18.3M against the indicative $18M envelope. The Investment Committee accepted the $0.3M variance, offset by avoiding the FY27 DC hardware refresh.

4. Resource and dependency notes

Store field force capped at 40 refits/month → P7 rollout wave plan of 6 months
Data migration (P3) gated on Data Governance Council survivorship sign-off
P5 cannot enter production before TA-0 platform acceptance (P1 exit criteria)
P5 and P6 share the SI partner; P6 uses a separate POS vendor team
Jul–Oct 2027 field-force load: 30 network refits + 5 POS pilot stores a month, within the cap

5. Key risks (validated in step 4)

Risk	Rating	Mitigation	Owner
Customer data migration quality (REQ-D-01)	High	Two trial migrations before cutover; council sign-off	Customer Data Steward
P5 slips into the 2027 peak freeze	Medium	Go/no-go on 4 Oct 2027; fallback is web-only Order Hub	P5 Program Director
Franchise renewal delays P7 franchise waves	Medium	Franchise stores scheduled in last wave	Store Ops Director

6. Benefits realization

Benefit owners and measures agreed per project; tracked quarterly by the Investment Committee (e.g., P5: BOPIS revenue/store/week; P3: duplicate-profile rate, care handle time).

7. Lessons learned (cycle closure)

Engage franchise partners in Phase A next cycle — late discovery of contract constraints reshaped POS sequencing.
Consolidated gap matrix maintained continuously (not only in Phase E) would have saved rework between Phases C and D.

See the lessons-learned record for the resulting Change Requests.

Study notes

Produced in: Step 3: Estimate resource requirements, project timings, and availability/delivery vehicle · Step 4: Prioritize the migration projects through cost/benefit assessment and risk validation · Step 6: Complete the Implementation and Migration Plan · Step 7: Complete the architecture development cycle and document lessons learned

This is the main Phase F deliverable. It turns work packages into chartered projects with costs, dates, owners, and funding, so the delivery organization can run it.
The 'delivery vehicle' column matters. TOGAF expects Phase F to identify whether each piece of work runs as a project or within a program, inside the enterprise's existing portfolio framework.
Tranche release conditions are tied to Transition Architecture acceptance. That links funding decisions to architecture milestones that Phase G will govern.
Priority does not simply follow value score: P1 scores only 14 but is priority 1 because everything depends on it. Exam questions often test that enablers are ranked by dependency, not standalone value.
Lessons learned are captured at cycle closure (step 7) and lead to Change Requests for the Architecture Capability, which go to Phase H and the Preliminary Phase.

Study tips & key concepts

Phase E creates the initial roadmap and outline plan; Phase F costs it, sequences it, and gets it agreed — 'finalize and coordinate' are the Phase F verbs.
The Implementation and Migration Plan must fit the enterprise's existing portfolio/program/project frameworks — architecture doesn't get its own parallel delivery machinery.
Business Value Assessment: a technique to position each project by value vs. risk (often drawn as a matrix) with agreed measures reviewed periodically.
The Architecture Definition Increments table shows which deliverables/state each project reaches per Transition Architecture — a classic Phase F artifact.
Phase F ends the 'architecture development' half of the cycle; deliverables are finalized here and governed through implementation in Phase G.