High Level Strategy Dependencies Milestones Roles and Responsibilities Iterative Approach Multiple Legacy / Targets Scope Several different migration methods :- –Logical Blocks (chunking) –Pilot –Big Bang –Catch Up –Post Migration - Parallel Runs Redwood Systems Limited Migration Strategy

Gap Analysis Data Mapping Specifications Identifying differences in functionality between legacy and target systems in terms of data needs. Legacy database schema to interim / target database schema including any transformations needed. Driven by the output of the gap analysis and the data mapping activities above. The specifications produced allow the developers to code the extract, transform and load (ETL) modules, as well as any reconciliation and data cleanse performed during migration. Redwood Systems LimitedAnalysis

Extracts / Loads Migration (transform) Reconciliations Referential File Integrities Transferring data from Legacy and / or Target. Transferring data to interim / target Code to move data from Legacy to Target with transformation Develop tools to migrate data (e.g. DTS) End-to-end comparisons of data content to create the necessary level of business confidence. Code to extract required figures Spreadsheets to report figures Validating quality of migrated data Redwood Systems LimitedDevelopment

Iterative and Incremental Development Data Cuts Freeze These are the execution of the migration process, which may or may not include new cuts of legacy data. Synchronised cuts of data taken from all systems Subsets / selective cuts Parameters Code Redwood Systems LimitedIterations

Analyse Develop Extract/Load Transform Integrity Load IssuesIssues Data Cleanse Eyeball ReconcileReconcile

Reconciliation File Integrities Translation Table Validation Eyeballing UAT Vertical and Horizontal Independently developed Figures at all stages (legacy, interim, target) Referential Integrities Data Constraints Duplicate Data Validate ‘From’ value against legacy parameters and ‘To’ values against target parameters Scenario Testing Regression Testing Spot Testing Comparison of legacy and target applications Independent Team Integration Test Customer Acceptance Testing Redwood Systems Limited Quality Assurance

Identified by Cleansing Strategy Data Mapping Eyeballing Reconciliations File Integrities Legacy - Pre Migration During (not advised as difficult to reconcile) Target - Post Migration (manual or via data fix) Ad Hoc Reporting – Ongoing Redwood Systems Limited Data Cleanse

Implementation Freeze Dress Rehearsal Go Live window (typical migration) Dry Run Shutdown Legacy (and Target) systems Run extracts – Legacy and Target Transfer and load data to migration environment Reconcile Run migration Reconcile and File Integrity Transfer and load to Target Reconcile, Eyeballing and UAT Acceptance Signoff (Go / No Go (instigate contingency plan)) Redwood Systems Limited

Post Implementation Post migration fixes Support Redwood Systems Limited

Source Staging Area TD Schema BA’s - Support, TT’s & Legacy Knowledge Trials & UAT Billing Rec Eye Balling Target Data Overview Data Migration Overview Data Migration/Business Rules (SCOPE) Data Mappings (RULES) Static Data (TARGET PARAMETERS) Translation Tables (LOOK-UP) Redwood Systems Limited