Migration Specialist

Job Description: • Support the end-to-end delivery of data migration activities on a Murex MX.3 banking transformation programme. • Reporting directly to the Migration Lead, the role covers hands-on execution across the migration lifecycle — source data extraction, mapping, ETL scripting, data loading into MX.3, reconciliation, and testing. • You’ll be in the data every day — running scripts, chasing breaks, investigating why a trade loaded incorrectly, and making sure the Migration Lead has clean, validated outputs to sign off on. • You’ll work closely with analysts across the FO, BO, Risk, and Finance workstreams and be expected to pick things up quickly and work with minimal hand-holding once you understand the scope. KEY SKILLS: • MX.3 Trade History Loading - Data Reconciliation & Break Investigation. • Static Data Migration (Counterparty, Instrument) - ETL Script Execution & Monitoring. • SQL / PL-SQL (Sybase & Oracle) - SIT / UAT Migration Testing. • Data Mapping & Transformation Logic - Issue Logging & Triage. • Source System Data Extraction - Requirements Documentation. • Data Quality & Cleansing - Stakeholder Support & Reporting. MIGRATION DATA SCOPE COVERAGE: • Trade History Loading — open positions, historical trades, and book-level balances across all asset classes into MX.3. • Static & Reference Data — counterparties, legal entities, portfolios, books, instruments, and standing settlement instructions (SSIs) • Market Data Seeding — rate curves, volatility surfaces, FX spot rates, credit spreads, and dividend schedules needed for valuation at the migration date. • Limit & Credit Data — credit line structures, counterparty limit configurations, and utilisation data required for MX.3 Credit Risk at go-live. • P&L Baseline — migrated P&L positions, accrual balances, and mark-to-market values required by Finance for continuity of accounting records at cutover. • Interface Reconciliation — validating that data flowing from external systems (nostro, cash, collateral) into MX.3 via interfaces is complete, timely, and correctly mapped. KEY RESPONSIBILITIES: • Data Extraction & Source System Analysis. • Extract data from legacy source systems under the direction of the Migration Lead, working to agreed extraction schedules and formats across all in-scope data tracks. • Profile source data to identify quality issues, missing fields, duplicates, and format inconsistencies, and document findings clearly for review by the Migration Lead. • Maintain source-to-target data mapping documentation, keeping it up to date as configuration decisions are made in MX.3 or as source system data changes. • Liaise with legacy system owners and data custodians to understand data structures, resolve extraction questions, and obtain data samples needed for mapping and testing. ETL Development & Migration Loading: • Write and maintain SQL scripts, Shell scripts, and Python routines for data extraction, transformation, cleansing, and loading tasks across assigned migration tracks. • Execute migration loads into MX.3 staging environments using MxML. • Exchange import workflows and bulk loading utilities, following the runbook and escalating errors to the Migration Lead. • Monitor migration job execution, capture error logs, and investigate failed records — categorising issues by root cause and either resolving them directly or escalating with a clear summary. • Implement data transformation logic as defined in mapping specifications, including cleansing rules, format conversions, defaulting logic, and enrichment from reference data. • Maintain migration control tables and audit logs to track record-level load status, error counts, and resolution outcomes across each batch run. Data Reconciliation & Quality Checks: • Run reconciliation checks between migrated MX.3 data and source system records at each migration milestone — trade counts, notional values, market values, P&L figures, and static data attributes. • Investigate reconciliation breaks, trace them back to their source (mapping error, transformation gap, MX.3 configuration issue, or source data problem), and document findings with proposed fixes. • Apply data quality validation rules within the migration pipeline to catch records that fail business rule checks before they are loaded into MX.3. • Support the interface reconciliation workstream by validating that data arriving in MX.3 from external systems (nostro, cash positions, collateral) is correctly received, mapped, and represented in MX.3 — noting that these flows are owned by the Integration workstream, not migrated directly. • Keep the reconciliation log and issues tracker up to date, flagging unresolved breaks to the Migration Lead with enough context for them to make a call. Testing & UAT Support: • Write and execute migration-specific test cases for SIT and UAT, covering record-level accuracy, referential integrity, and MX.3 module behaviour after loading. • Log, triage, and track defects through to resolution, coordinating with the relevant functional workstream where the fix sits outside the migration pipeline. • Support business users during UAT migration validation — responding to data queries, pulling validation extracts, and providing root-cause analysis when loaded data doesn’t match expectations. • Participate in migration dress rehearsals, executing assigned tasks within the cutover runbook and recording timing and outcomes accurately for post-rehearsal review. Documentation & Workstream Support: • Keep mapping specifications, transformation logic documentation, and data dictionaries accurate and current throughout the programme. • Contribute to the migration runbook by documenting the steps, inputs, outputs, and known risks for the tasks you own within the cutover sequence. • Attend daily stand-ups, design reviews, and workstream planning sessions, flagging blockers early and providing clear status updates on assigned tasks. • Support…