01
Discover the structure
Build schema and relationship views from the database. Review declared and inferred relationships rather than assuming every inferred link is authoritative.
Migration Analyst capabilities
Make the legacy visible.
Make the design reviewable.
Core analysis runs locally in your environment. Schemas, quality findings and mapping decisions form an evidence base for the migration design.
Evidence for the decisions that matter.
02
Explain business domains
Use conceptual domain maps and responsibilities to connect technical structure with business conversations. Optional LLM-assisted naming is explicitly enabled per project.
03
Profile quality and readiness
Inspect quality, volumes, dependencies and compatibility risks. Readiness assessments help prioritise work and require review alongside the underlying findings.
04
Identify likely sensitive fields
Use schema hints and representative samples to identify patterns associated with personal, payment and health information. Findings inform governance review; they are not compliance certification.
05
Review transformations
Record mappings and ordered rules, then preview representative samples. Resolve failures and incomplete decisions before publishing.
06
Publish the design
Export a versioned, checksummed specification for implementation and reconciliation, with supporting reports, runbooks and diagrams.
See it in context.
Explore the guided product tour →Find the risk before the build.
Bring one representative legacy scope and agree the evidence you need from discovery.