Data Migration Lead

Title: Data Migration Lead
Job Location : New Jersey (Remote)
Duration: 6 Month Contract

Responsibilities
Determine the scope of Data migration.
Document the data migration strategy.
Document Data Migration Protocol to go along with the data migration strategy.
Produce the Data Migration Summary report based on the data migration strategy and protocol documents.
Participate in finalizing the code migration strategy in conjunction to the data migration strategy.
Coordinate moving of various transports from a WMS perspective.
Support Mapping and Construction of Data from Legacy Systems
Establish and Support PreLoad and PostLoad Business Signoff
Support Internal and External Quality Control and Audit Processes
Lead Data Defect Triage and Remediation
Scope/Identify/guide any remediation of incomplete/incorrect Data in Legacy Systems.
Validation of all the data once its moved across the environments (DEV PQA QA Prod)
Cutover planning and Mock cutover coordination and fall over and fall out reconciliation working closely with Systems and Performance teams. Some of the points to be considered for cutover are:
o Inclusion of reversion back to PROD original state post mock cutover exercises for first site
o Plan for mock cutover for 2nd site as FDC will already be in PROD
POST golive monitoring of all data related activities and the whole cutover plan.
Some of the other specific responsibilities will also involve the following:
1. Verification of Data Integrity between platforms ERP WMS Serialization
2. Coordination of delivery/ creation of BY Test data in each environment DEV PQA QA and Prod
3. Oversight of all things data migration environment to environment strategy configuration master and transactions as applicable
a. Reconciliation of accelerator tool result for uplifts across platforms
b. RCA for fillout and followon corrective actions
c. Updated approach review to not repeat history for each Component load to higher environments.
4. Data Conversion Strategy from lower to higher environments including BY configuration preservation where applicable and legacy MARC data conversion.
a. LPNs with serialized hierarchies
b. Inventory (LPN) by location
c. Orders by status
i. Inbound
ii. Outbound
d. Orders not only by status including progress quantity details at header and at line item level
e. Inventory by Location with LPN details regarding status committed (all of the subtabs)
f. Inventory reconciliation with ERP and Serialization
g. Serialization Data
h. Clinical Data