Most migration failures aren't caused by bad technology — they're caused by skipping the assessment that would have caught the problems first. Organizations that conduct a formal architecture readiness assessment before migration achieve 2.4x higher success rates, yet most enterprises still proceed without one. A comprehensive assessment costs 1–5% of a typical migration budget and routinely prevents overruns that average 23% above plan.
What You'll Learn
- The 10 architecture dimensions your assessment must cover before any migration begins
- The red flags and anti-patterns that signal your org isn't ready to migrate
- How to apply the 7 R's framework to classify every application in your portfolio
- What assessments cost, how long they take, and how to calculate the ROI
- A decision framework for sequencing your modernization roadmap
What Is an Enterprise Architecture Assessment?
An enterprise architecture assessment is a structured evaluation of an organization's current technology landscape — applications, data, infrastructure, integrations, and organizational readiness — conducted before a major migration or modernization initiative to identify gaps, dependencies, and risks that would otherwise surface as cost overruns or failures.
It is not a documentation exercise. Done right, it is the single most consequential investment you can make before committing to a migration.
Three Failures That Define What's at Risk
Real-world failures are more instructive than aggregate statistics.
Target Canada (2013–2015)
Target rushed an SAP implementation without validating data quality or integration readiness. Data in the system had only 30% accuracy. Three separate systems failed to integrate properly. All 133 Canadian stores closed. A basic architecture assessment would have flagged the data quality gap in week one.
UK NHS National Programme for IT (2002–2011)
The largest civilian IT program ever attempted. A top-down architecture designed without stakeholder input produced only £2.6 billion in benefits. The UK National Audit Office concluded the program was undone by "unprecedented scale and boundless complexity" — exactly the finding a proper assessment delivers upfront.
Lidl SAP Failure (~2011–2018)
Lidl's inventory system used purchase-price valuation; SAP used retail-price. A fundamental architecture mismatch discoverable in week one of any serious assessment. Instead, Lidl spent $600 million trying to force SAP to mirror legacy behavior before scrapping the entire project.
The 10-Dimension Architecture Assessment Checklist
A rigorous pre-migration assessment covers ten domains. Most organizations shortchange at least three of them.
Application Portfolio
Inventory every application: lifecycle stage, business criticality, technology stack, redundancy, technical debt, and ownership mapping. Apply the 7 R's classification to every application in scope.
Data Architecture
Map data sources, schemas, quality levels, volumes, dependencies, and data flows. Classify data by sensitivity tier. Data migration overruns budget 64% of the time — poor data architecture discovery is usually why.
Infrastructure & Technology
Inventory servers, storage, networking, cloud readiness, virtualization maturity, and container infrastructure. For 50+ servers, use automated discovery tools: Azure Migrate, AWS Migration Hub, or Faddom.
Security & Compliance
Identify security protocol gaps and regulatory requirements (HIPAA, GDPR, PCI-DSS, SOX) before they surface as blockers mid-migration. Security architecture gaps show up in 79% of failed cloud migrations.
Integration Patterns & APIs
Map the full API landscape: messaging patterns, service-to-service communication, third-party dependencies, and cloud-native protocol compatibility. Undocumented integrations are among the most expensive migration surprises.
Business Process Architecture
Identify core processes, distinguish differentiating from non-differentiating processes, and assess automation level and process maturity. Find processes embedded in legacy code that can't simply be rehosted.
Organizational Readiness
Assess team skills gaps (70% of IT decision-makers report a skills gap), DevOps maturity, change management readiness, and governance structures. Technical readiness without organizational readiness still produces failure.
Performance & Operations
Capture CPU, memory, and disk I/O baselines over 30+ days. Document peak concurrency, SLAs, and existing monitoring capabilities. Fewer than 30 days of baseline data is statistically unreliable for cloud sizing.
Business Capability Mapping
Establish traceability from strategy to technology. Map value streams to application portfolios. This is what allows a defensible conversation with your board about sequencing decisions.
Cost & Financial Analysis
Conduct full TCO analysis, including licensing costs, redundant spend, and ROI potential. IDC research shows 20–30% of applications in many organizations are redundant — representing immediate cost savings.
Applying the 7 R's: How to Classify Every Application
Apply the 7 R's framework to every application in your portfolio. Typical distribution: Rehost 40%, Replatform 30%, Retire 15%, Repurchase 10%, Retain 5%.
| Classification | What It Means | Typical Use Case | Watch Out |
|---|---|---|---|
| Rehost | Lift-and-shift to cloud with no code changes | Low-complexity apps; fast timelines | 40% higher ongoing cloud costs if overused |
| Relocate | Move to cloud without OS/runtime changes | VMware workloads moving to cloud VMware | — |
| Replatform | Minor optimizations; no core architecture change | Managed DB, containerization | — |
| Refactor | Re-architect to be cloud-native | High-value apps with long runway | 3x slower than rehost |
| Repurchase | Replace with SaaS equivalent | Commodity functions (HR, CRM) | — |
| Retire | Decommission | Redundant, unused, or obsolete apps | — |
| Retain | Keep on-premises for now | Compliance, latency, or dependency constraints | — |
Lift-and-shift completes 3x faster than refactor, but results in 40% higher ongoing cloud costs. If Rehost is your default classification rather than a deliberate choice, your architecture assessment has a sequencing problem.
Red Flags That Signal Migration Unreadiness
If several of these apply to your organization, treat them as blockers — not risks to monitor.
What an Assessment Costs — and the ROI Math
Assessment fees are consistently a fraction of migration budgets. The ROI case is nearly irrefutable: a 23% overrun on a $2M migration equals $460,000 in excess costs — exceeding a comprehensive assessment fee on a single prevented overrun.
| Engagement Type | Cost Range | Duration |
|---|---|---|
| Quick assessment / EA QuickScan | $19,000–$25,000 | 1–2 weeks |
| Focused review (single domain) | $38,000–$75,000 | 2–4 weeks |
| Comprehensive EA assessment (mid-market) | $50,000–$200,000 | 4–12 weeks |
| Enterprise-wide deep assessment | $150,000–$500,000+ | 3–6 months |
| EA Center of Excellence setup | $6,500–$13,000/month | 3–6 months |
How to Decide in the Next 30 Days
Key Takeaways
1. The assessment gap is the most actionable finding in migration research. Organizations with formal readiness assessments achieve 2.4x higher success rates, yet the majority skip or shortchange this step — directly contributing to the 70% transformation failure rate.
2. The cost asymmetry is stark. Assessments run 1–5% of migration budgets and prevent overruns averaging 23%. The ROI case is nearly irrefutable.
3. Undocumented dependencies are your highest-probability risk. 47% of migration delays trace back to legacy application dependencies not identified during assessment. Dependency mapping is not optional.
4. Lift-and-shift is a choice, not a default. Applied selectively, it's 3x faster to execute. Applied uniformly, it produces 40% higher ongoing cloud costs. The 7 R's classification forces this to be a deliberate decision.
5. Technical debt is a business performance variable, not just a maintenance cost. McKinsey's analysis shows companies in the 80th percentile for low technical debt achieve 20% higher revenue growth. The conversation with your board should be framed accordingly.
Get an Architecture Assessment
Sphere's architecture team will evaluate your technology landscape, map dependencies, and produce a sequenced migration roadmap with risk register and TCO analysis — completing most mid-market assessments in 4–8 weeks.