Most enterprise migrations don't fail during execution. They fail three months before the first line of code moves — when the team skipped the assessment and assumed they understood what they had.
The database looked manageable. A few hundred tables, some stored procedures, a couple of batch jobs. Then the project started, and the real inventory surfaced: 4,000 stored procedures, 800 of which contain business logic that hasn't been documented since 2003. A COBOL batch job that reconciles the entire ledger every Sunday night. Seventeen downstream systems that depend on a database view no one knew existed.
According to McKinsey and the University of Oxford, large-scale IT projects run 45% over budget and 7% over time on average, while delivering 56% less value than predicted — and 17% of projects go so badly they threaten the organization's existence. The leading cause of those overruns is not technical complexity. It is underestimated scope — which is exactly what a rigorous migration readiness assessment is designed to eliminate.
This is not optional paperwork. It is the intelligence injection that makes the rest of the project predictable.
What Migration Readiness Assessment Is
A migration readiness assessment is a systematic technical and organizational audit conducted before any migration work begins. Its purpose is to produce three things:
- a verified inventory of what you're migrating
- a complexity classification of what that inventory contains
- a credible estimate of what the migration will cost and how long it will take
AWS formalized this approach as the Migration Readiness Assessment (AWS MRA), a structured evaluation framework used by AWS Professional Services before any large-scale cloud engagement. The underlying logic is universal: you cannot price or plan a migration without knowing what you're moving. Whether the destination is AWS, Azure, Google Cloud, or a self-managed PostgreSQL cluster, the assessment methodology is the same.
The stakes are real. Gartner has reported that 83% of data migration projects either fail or exceed their budgets and schedules. And according to recent analysis, organizations that conduct a formal readiness assessment before migrating have 2.4x higher success rates than those that don't.
The difference between a project that delivers and one that derails almost always comes down to whether a serious migration readiness assessment happened before commitments were made.
Six Pillars of a Credible Assessment
A surface scan is not an assessment. A credible audit covers six pillars. Shortcut any of them, and you're building your migration plan on incomplete data.
Database Object Inventory
Tables, views, stored procedures, triggers, indexes, sequences, packages, and every dependency between them. For Oracle-to-PostgreSQL migrations — currently the highest-volume enterprise migration path, driven by Oracle licensing costs that compound at 8% per year under standard Oracle support renewal terms — this means cataloging PL/SQL logic that may have been accumulating for two decades.
The same discipline applies to SQL Server, Sybase ASE, DB2, Informix, and MySQL environments where business rules have been accumulating in the databases for years. Our comprehensive Oracle to PostgreSQL migration guide covers what this inventory reveals in practice.
Complexity Classification
Not all objects migrate at the same cost. A mature migration readiness assessment tool classifies each object into tiers:
- simple (high automation)
- medium (automatable with minor adjustment)
- complex (requires configuration or customization)
- manual (requires direct human intervention)
This classification is the foundation of every downstream cost and timeline calculation. Without it, your budget is fiction.
Embedded SQL and Application Code
The database doesn't live in isolation. Applications written in COBOL, PowerBuilder, Delphi, Progress 4GL, Informix 4GL, Visual Basic, and C++ frequently contain Embedded SQL (ESQL) blocks that interact directly with the schema. A migration that only assesses the database while ignoring the application layer produces a number that is wrong by a factor of two or three.
Dependency Mapping
Cross-database references, linked server queries, ETL pipelines, API consumers, and third-party integrations. Undocumented dependencies are the single biggest source of post-migration production incidents.
Cloud Readiness
If the target is a cloud-native platform — AlloyDB, Aurora PostgreSQL, Azure Database for PostgreSQL, or Amazon RDS — the assessment must evaluate the cloud readiness of the source environment. Latency profiles, connection pooling requirements, data residency constraints, and the implications of a move to the cloud all affect the target architecture.
This is distinct from assessing the database itself; cloud migrations introduce an infrastructure layer that must be scoped separately.
Risk Profile and Identified Gaps
Every assessment should conclude with a clear enumeration of identified gaps:
- objects that cannot be automatically converted
- deprecated syntax without a direct equivalent in the target platform
- missing schema elements
- broken references
These gaps define the manual effort bucket — which is where all project cost uncertainty lives.
5 R's Are Only Useful If You Have the Data
The 5 R's of migration — Rehost, Replatform, Refactor, Repurchase, and Retire — are a strategic framework for deciding what happens to each workload. AWS extends this to 7 R's, adding Retain and Relocate. The framework is well-known. The problem is that most teams pick a strategy before they have the data to justify it.
A Rehost decision (lift-and-shift) is defensible when the assessment shows high structural compatibility and minimal custom logic. A Replatform decision is appropriate when the schema is portable but stored procedures require moderate rework.
A Refactor decision — the most expensive and highest-risk — is indicated when the assessment reveals deep proprietary dependencies, extensive use of database-specific features (Oracle packages, Sybase row-level security, DB2 temporal tables, Informix SPL), or architectural patterns that don't translate to the target environment.
A strategic migration assessment and readiness tool gives you this data before you've spent six figures on engineering time. Without it, you're choosing a migration strategy based on instinct.
Read more: Rehost, Refactor, or Rebuild? 8 Ways to Modernize Legacy Systems
Manual Audit vs. Automated Assessment: Numbers Don't Lie
The traditional pre-migration audit involves a team of consultants spending weeks reviewing source code by hand, sampling stored procedures, documenting what they find, and producing a scoping report that is already partially outdated by the time it's delivered.
The problem with manual audits is not effort. It is accuracy and completeness. Human reviewers sample; they don't enumerate. They miss ESQL blocks embedded in application code. They miss undocumented stored procedures that only run under specific conditions. They miss deprecated syntax that surfaces as a blocker at the worst possible moment — during user acceptance testing, not during planning.
Automated migration readiness assessment tools eliminate this by connecting to the source database with read-only access, systematically enumerating every object, and generating a structured report in minutes rather than weeks. For a migration portfolio assessment covering dozens of databases across a complex enterprise, there is no credible manual alternative. The scale simply doesn't permit it.
This is also why a detailed assessment report — whether delivered as a structured PDF or a dashboard — carries more weight in a board-level business case than a consulting estimate derived from sampling. The numbers come from the actual code. If you're working from a migration readiness assessment template to structure your evaluation criteria, it only adds value when the underlying data comes from automated analysis of the real source system, not manual review.
What Professional Assessment Deliverables Look Like
At the end of a rigorous assessment process, you should have the following in hand:
- A complete object inventory by type — tables, procedures, triggers, views, packages, sequences — with object-level complexity ratings.
- A projected automation rate for the target migration toolchain, and the delta between the baseline automation rate and the maximum achievable rate with tool configuration.
- A clear enumeration of manual adjustment requirements.
- Embedded SQL analysis across all relevant application code.
- A migration project timeline range and cost estimate derived from assessed complexity, not analogous benchmarks.
- And a risk register of identified gaps and potential blockers.
Anything less is a conversation starter, not a migration plan. A cloud readiness assessment checklist can supplement this output when the target involves cloud migrations, but it should never substitute for automated technical analysis of the source environment.
InsightWays: Assessment Before Migration
Ispirer InsightWays is a strategic migration assessment and readiness tool purpose-built for this problem. It operates in offline mode with read-only database access — no data leaves your environment, no modifications are made to the source system. It connects to Oracle, SQL Server, PostgreSQL, Sybase ASE, DB2, Informix, MySQL, MariaDB, and AlloyDB source environments.
The output covers 44+ analytical dimensions:
- Full object count by type with complexity classification (simple / medium / complex / manual)
- Projected automation rate using SQLWays
- Manual adjustment requirements and tool customization recommendations that increase automation coverage
- Embedded SQL analysis within COBOL, PowerBuilder, Delphi, Progress 4GL, Informix 4GL, and C++ application code
- Time and effort estimates for the migration project that can be used for cost planning
The latest InsightWays release added ESQL support, meaning application-embedded database code is now analyzed alongside the database schema — a critical capability for any migration involving COBOL or legacy application stacks. Script analysis speed has also been increased by up to 6x, so large codebases no longer require overnight runs.
InsightWays is free. No payment required to run an assessment. You download the tool, connect with read-only credentials, and generate your report. The full scan completes in under five minutes for a standard database environment.
Before you evaluate data migration tools, before you engage database migration services — run the assessment. It is the methodology that separates migrations that deliver from migrations that derail.
For organizations evaluating automated infrastructure modernization at scale, or broader IT infrastructure transformation programs, the InsightWays output feeds into the business case, the project governance framework, and the migration strategy document.
The database migration problem is always harder than it looks from the outside. InsightWays makes it look exactly as hard as it is — before you're committed.
Pre-Assessment Checklist
Before running your assessment, confirm the following:
- Read-only access credentials to the source database
- Application source code repository access (for ESQL and embedded code analysis)
- Documentation of known integrations and downstream system dependencies
- Identified target platform and migration path
- Stakeholder alignment on acceptable downtime windows and data freeze requirements
This cloud readiness assessment checklist also applies when the target is a managed cloud database. The source environment's network architecture, compliance posture, and licensing model all need to be documented before the migration strategy is finalized.
Stop Guessing. Start Knowing.
The cost of skipping a migration readiness assessment is not hypothetical. It shows up as a blown budget in Q3, an emergency freeze on a half-migrated production database, or a regulatory incident triggered by undocumented data flows that nobody mapped.
InsightWays gives you the complete picture in five minutes, for free. Run the assessment. Know your number. Then decide.
Download InsightWays — free forever, no registration required. Or book a 30-minute demo to walk through your assessment report with an Ispirer migration expert.
Frequently Asked Questions
What is a migration readiness assessment?
A pre-migration technical and organizational audit that inventories your source system, classifies complexity, maps dependencies, and produces a credible timeline estimate before any migration work begins.
How does an automated migration readiness assessment tool differ from a manual audit?
An automated tool enumerates every object systematically with read-only access and generates auditable output in minutes. Manual audits rely on sampling, miss embedded code, and take weeks. For any project above a few hundred objects, automated assessment is both more accurate and faster.
What red flags in legacy code indicate high migration risk?
Heavy use of database-specific proprietary features (Oracle packages, Sybase-specific syntax, DB2 temporal tables), extensive Embedded SQL in application code, undocumented stored procedures with cross-database dependencies, and missing or broken schema elements. A professional migration readiness assessment tool surfaces all of these automatically.
What deliverables should you expect at the end of a professional assessment?
A complete object inventory with complexity tiers, projected automation rate, manual effort estimate, identified gaps and blockers, platform compatibility analysis, and a project timeline and cost estimate. InsightWays produces all of these in a single downloadable report.
How long does an enterprise-level assessment take?
With an automated tool like InsightWays, a standard database scan completes in under five minutes. A full application and database assessment for a complex enterprise environment — covering COBOL, Embedded SQL, and multiple source databases — can be completed in hours, not weeks.
