DATA MIGRATION VALIDATION

A financial data migration validation project comparing transaction records between two systems (System A → System B) to identify discrepancies, missing records, duplicate entries, and financial impact — ensuring data integrity during migration.

Problem Statement

When financial systems are migrated, data can be lost, duplicated, or altered.This project aimed to independently validate that all transaction records from System A were correctly and completely transferred to System B, and to quantify any financial risk from discrepancies

Dataset

• 5,049 total transactions across both systems
• Fields validated:Transaction ID, Amount, Date, Status
• Two systems compared: System A (source) vs System B (destination)

My Approach & Methodology

Step 1 — Data Loading & Cleaning

• Loaded both system datasets into Excel
• Removed duplicate headers and standardized date formats
• Used COUNTIF to identify duplicate Transaction IDs in each system

Before

After

Step 2 — Missing Transaction Check

• Used VLOOKUP/IFERROR formulas to check if each System A transaction existed in System B
• Flagged missing records as "Missing in B"