Data Migration Consultant

Job Description

Inspiration Global is Seeking a qualified contractor to provide end-to-end Data Migration services to support the migration of customer, financial, transactional, and related operational data from existing legacy systems to Microsoft CRM, SAP S/4HANA, SAP BRIM components, Convergent Mediation, Datasphere, and associated downstream systems that are part of the Unified Back Office System (UBOS) ecosystem. The work will be performed in multiple phases, including design/mapping, iterative mock cycles, dress rehearsals, and final production cutover.

The selected contractor must have proven expertise in Microsoft CRM and SAP S/4HANA Data Migration, particularly in high-volume transaction processing back-office environments, and must demonstrate the ability to design, build, execute, reconcile, and optimize data migration activities in compliance with the client’s standards, policies, and data governance requirements.

Each Mock Cycle is to be individually priced in the contractor’s proposal and will be treated as an optional exercise at the cleint’s discretion. Contractors must propose a detailed timeline for completing each phase, including dependencies and resource requirements.

BACKGROUND

The client is engaging in an exciting and innovative technology solution to support our customer engagements; we call the solution the UBOS. UBOS is an advanced back-office system that, when developed and deployed, will allow customers to engage with the client to address all their business needs, via a multitude of channels (web, mobile app, chatbot, chat, Interactive Voice Response (IVR), phone, social media, etc.). We are dedicated to transforming the customer engagement businesses through innovative technology and strategic insights. Our team is composed of passionate professionals committed to excellence and continuous improvement, and our team is growing.

TASKS & DELIVERABLES

• Prior to commencement of work each phase, deliverables will be clearly defined, with acceptance criteria documented in the client’s work management tool (e.g., Azure DevOps).
• Maintain PCI-DSS and SOC 1/SOC 2 compliance throughout the migration.
• Implement PII masking in all non-production environments.
• Maintain audit logs for all migration activities.
  
  
  
  Phase 1 - Design and Mapping
  
  
  The contractor shall:
  
  
  
  Detailed Data Mapping and Transformation Rules
  • Map legacy source data to target Microsoft CRM and SAP structures, including Master, Transactional, and History data objects.
  • As applicable, map unstructured data object references from non-SAP systems to Microsoft CRM and SAP data.
  • Identify data gaps and propose mapping resolutions in consultation with the client’s stakeholders.
  • Define transformation logic for source-to-target conversions.
  • Define work arounds and provide options to transform legacy data to be migrated to Microsoft CRM and SAP objects providing similar functionality in the UBOS.
  • Document the project as part of Deliverable D-1 listed below.
    
    
    
    Detailed Microsoft CRM and SAP Data Migration Design Documentation
  • Create a detailed Microsoft CRM and SAP Data Migration Design following the templates and direction provided by the client.
  • Provide the documentation as part of Deliverable D-2 listed below.
    
    
    
    Archival and Retention Rules
  • Incorporate retention, relevancy, and archival rules into migration design to ensure compliance with the client’s data governance policies.
  • Provide the document as part of Deliverable D-2 listed below.
    
    
    
    Cleansing & Enrichment Rules
  • Identify cleansing rules to remove duplicates, correct invalid data, and align with Microsoft CRM and SAP master data standards.
  • Identify enrichment rules to supplement data from the client’s CRM system and other sources to meet Microsoft CRM, SAP S/4HANA, SAP BRIM components, Convergent Mediation, Datasphere, and associated downstream system’s target requirements.
  • Provide the rule specifications as part of Deliverable D-3 listed below.
  • The contractor is responsible for bringing any software tools needed for cleansing, transformation, and enrichment process.
    
    
    
    Load Schema & Mechanism Design
  • Define “load-ready” schema for Microsoft CRM, SAP S/4HANA, SAP BRIM components, Convergent Mediation, Datasphere, and associated downstream systems.
  • Design and develop load scripts for Microsoft CRM, SAP S/4HANA, SAP BRIM components, Convergent Mediation, Datasphere, and associated downstream systems.
  • The contractor is responsible for bringing any software tools needed for the load process.
  • Ensure compliance with PCI and PII handling requirements, including masking in lower environments and encryption where applicable.
  • Design approach for migrating historical (closed) transactions in manner that it is actionable in the UBOS system.
  • Provide the design documentation as part of Deliverable D-4 listed below.
    
    
    
    Unstructured Data
  • Develop an approach for linking images and financial documents in Azure BLOB storage to records in Microsoft CRM and SAP S/4.
  • Provide the design documentation as part of Deliverable D-4 listed below.
    
    
    
    Reconciliation Strategy
  • Develop reconciliation definitions, criteria, and procedures for validating migrated data by object.
  • The contractor is responsible for bringing any software tools needed for the reconciliation process.
  • Provide reconciliation templates for the client’s sign-off.
  • Provide the strategy documentation as part of Deliverable D-5 listed below.
    
    
    
    Infrastructure Requirements
  • Identify hardware, software, and network requirements to support migration activities.
  • Provide the Infrastructure requirements documentation as part of Deliverable D-6 listed below.
    
    
    
    General Requirements for All Mock Cycles
  • Each Mock Cycle will be priced individually and may be exercised at the client’s discretion.
    
    
    Contractor must:
  • Execute pre-load validation and post-load verification with business sign-off.
  • Participate in design reviews, defect triage, and testing cycles.
  • Use the client’s defect tracking system with defined SLA for defect resolution.
  • Provide reconciliation results and root cause analysis for discrepancies.
  • Perform full and incremental data migration.
  • Migrate historical (closed) transactions in an actionable/functionable manner, similar to data generated in UBOS system.
  • Unstructured Data - Develop approach for linking of images and financial documents in Azure BLOB storage to records in SAP S/4.
  • Document the activities and results of all Mock Cycle executions into Deliverable D-7 listed below.
    
    
    
    Mock Cycle 1 - Development and Execution
  • Account Types: POV, MOTORH, CVO2.
  • Develop ETL migration scripts for Mock 1 scope.
  • Load 10,000 accounts per account type.
  • Load all relevant master and transactional data objects for each of the accounts into the UBOS system.
  • Perform reconciliation against source data.
  • Support testing and fixing defects.
    
    
    
    Phase 2 - Mock 2 and Beyond Cycles
    
    
    The contractor shall:
    
    
    
    Mock Cycle 2 - Development and Execution
  • Account Types: CVO1, CVO2, CVO3, CVO-IM, CVO-H RTBP (PBP2), TBP (PBP1), along with account types from Mock 1.
  • Develop ETL migration scripts for Mock 2 scope.
  • Load 10,000 accounts per account type for new account type.
  • Load 50% of accounts for account types delivered in mock cycle 1.
  • Load all relevant master and transactional data objects for each of the accounts into the UBOS system.
  • Perform reconciliation against source data.
  • Support testing and fixing defects.
    
    
    
    Mock Cycle 3 - Development and Execution
  • Account Types: All Account Types part of Go-live.
  • Develop ETL migration scripts for Mock 3 scope.
  • Load 10,000 accounts per account type for new account types.
  • Load 80% of accounts per account type.
  • Load all relevant master and transactional data objects for each of the accounts into the UBOS system.
  • Perform reconciliation against source data.
  • Support testing and fixing defects.
    
    
    
    Phase 3 - Dress Rehearsals
    
    
    The contractor shall:
    
    
    
    General Requirements for All Dress Rehearsal
  • Execute pre-load validation and post-load verification with business sign-off.
  • Participate in defect triage, and testing cycles.
  • Use the client’s defect tracking system with defined SLA for defect resolution.
  • Provide reconciliation results and root cause analysis for discrepancies.
  • Perform full and incremental data migration.
  • Migrate historical (closed) transactions in an actionable/functionable manner, similar to data generated in UBOS system.
  • Unstructured Data - Develop approach for linking of images and financial documents in Azure BLOB storage to records in Microsoft CRM and SAP S/4.
  • Document the activities and results of all Dress Rehearsal executions into Deliverable D-9 listed below.
    
    
    
    Dress Rehearsal 1 - UAT Feed
  • Perform full migration of all data objects.
  • Execute Delta 1 and Delta 2 incremental loads.
    
    
    
    Dress Rehearsal 2 - Certifications and Go Live Feed
  • Perform full migration (Production Golden Copy).
  • Execute Delta 1, Delta 2, and Delta 3 incremental loads (Production Golden Copy).
    
    
    
    Phase 4 - Cutover
    
    
    The contractor shall:
    
    
    
    General Requirements for All Cutover Cycles
  • Execute pre-load validation and post-load verification with business sign-off.
  • Participate in defect triage and testing cycles.
  • Use the client’s defect tracking system with defined SLA for defect resolution.
  • Provide reconciliation results and root cause analysis for discrepancies.
  • Perform full and incremental data migration.
  • Migrate historical (closed) transactions in an actionable/functionable manner, similar to data generated in UBOS system.
  • Unstructured Data - Develop approach for linking of images and financial documents in Azure BLOB storage to records in Microsoft CRM and SAP S/4.
  • Capture the details and results for all Cutover Activities into Deliverable D-9 below.
• Phase 4 - Production Golden Copy and Cutover
  • Leverage DR2 full load and Deltas 1-3.
  • Execute Delta 4 and Delta 5 (Final Cutover) for Go-Live.
    
    
    
    Post Cutover Support / Hypercare / Knowledge Transfer
    
    
    The contractor shall:
    
    
    
    General Requirements for Post Cutover Support / Hypercare
  • Triage and resolve all bugs and defects identified during the first 30 calendar days following Cutover.
  • Track and fully document all bugs and defects either in the client’s ADO or ServiceNow systems as directed by the client.
  • Provide daily updates on all active bugs and defects within the appropriate system.
  • Provide runbooks for the client as defined by the client.
  • Provide the documentation and meetings necessary for a full knowledge transfer to the client’s designated resources.
  • Documentations shall meet the requirements specified by the client, either using a provided template or under the direction of the client.
  • Document the successful knowledge transfer and provide details within Deliverable D-10 below.

Why Join Us?

At Inspiration Global, we are passionate about driving innovation and delivering cutting-edge digital solutions across industries. You’ll be part of a collaborative, growth-oriented environment that encourages experimentation and continuous learning.