Migration Analyst →
Discover risks, review mappings and publish a versioned specification.
The migration workflow
A reviewed design.
A controlled move.
A verified result.
Carry the intended design into implementation, then compare it with the observed outcome. Each approval answers a different question.
From legacy data to approval evidence.
A shared specification connects design, execution and verification.
Migration Framework →
Run supported batch or CDC migrations with progress, checkpoints and exceptions in view.
Recon Sentinel →
Compare source and target, track discrepancies and collect technical and business approval.
Each tool has a distinct responsibility. Supported fields and paths are validated at hand-off; reconciliation can derive additional checks from mappings and live database catalogues.
Explore the hand-off and approval workflow →What crosses each boundary.
01
1. Discover and design
Analyst discovers structure, profiles risks and records mappings, transformations and dependencies. Design review confirms what should move and how.
02
2. Publish the specification
Publish a versioned, checksummed artifact. It describes connections, entities, business keys, mappings, dependencies and supported execution or reconciliation settings.
03
3. Validate and execute
Framework validates the import and supported execution path. Operators review prerequisites, start runs and investigate checkpoints or exceptions.
04
4. Verify the outcome
Recon Sentinel imports a read-only version and generates checks. Missing information may be derived from live catalogues or reported as a gap; tolerances and scope are reviewed.
05
5. Compare rehearsals
Track fixed, newly failing and persistent discrepancies. Results refer to the input version being verified so design changes remain visible.
06
6. Approve the evidence
Freeze a result package. A technical reviewer and a different business approver record the migration outcome approval; this is separate from Analyst design approval.
Transparent hand-offs.
The published specification is the preferred hand-off. Integration covers supported fields and execution paths; it does not imply every design rule is automatically executable or every reconciliation rule is explicitly supplied. Validation, derived checks and surfaced gaps keep those boundaries visible.
Batch and CDC are available separately. Coordinated hybrid cutover remains planned.
Review supported systems and modes →Agree the evidence before the migration.
Define the pilot scope, execution path, tolerance policy and approval criteria together.