01DISCOVER
CUSTOMERPK customer_idemailcountry_id
USERPK user_idnormalized_emailcountry_code
1:N · FIELD LINEAGEDraw the ERD that was never documented
Point Migration Analyst at a source database and it builds the entity-relationship diagram from the actual schema — keys, foreign keys and inferred relationships — not from a Visio file last touched a decade ago. If your legacy system has no current documentation, this is where the migration starts.
NO PRE-EXISTING ERD REQUIRED02UNDERSTAND
◆Customers4 tables grouped
◆Entitlements3 tables grouped
Turn tables into a domain map
Raw schemas make sense to a DBA and almost no one else. Migration Analyst groups tables and fields into a business-readable domain map, so programme leads, architects and delivery partners can review what's actually being migrated without reading DDL.
BUSINESS-READABLE VIEW03PROTECT
3FIELDS FLAGGED
email PII
date_of_birth PII
govt_id PII
Flag PII before it becomes an incident
Migration Analyst scans source schemas and representative samples to flag fields likely to hold personal or sensitive information — names, emails, dates of birth, government identifiers and more — so privacy and security review happens at design time, not after something's already landed in the target system.
SURFACED EARLY · INFORMS MASKING AND ACCESS DECISIONS04MAP
emailTRIMLOWERVERIFY✓RULES EXECUTE IN ORDER
One surface, from mapping to sign-off
Connect fields, document every source-to-target relationship, and build ordered, explainable transformation rules — trims, lookups, conversions, validation — in place of scattered spreadsheets and undocumented SQL. Run representative samples through each rule, catch failures before they reach production, and export a portable, auditable specification when it's approved.
FIELD-LEVEL LINEAGE · LIVE SAMPLE VALIDATION · PORTABLE JSON SPEC