I am Baiju represented to Applab Systems and I have an excellent job opportunity for you. Please find the below job description and if you are comfortable, please reply or contact me for further discussion.
Job Title: Data Migration Lead
Location: New Jersey (Remote)
Job Type: 6-12+ Months
Job Description
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.
Co-ordinate moving of various transports from a WMS perspective.
Support Mapping and Construction of Data from Legacy Systems
Establish and Support Pre-Load and Post-Load 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 cut-over 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:
Inclusion of reversion back to PROD original state post mock cutover exercises for first site
Plan for mock cutover for 2nd site as FDC will already be in PROD
POST go-live monitoring of all data related activities and the whole cutover plan.
Some of the other specific responsibilities will also involve the following:
Verification of Data Integrity between platforms - ERP, WMS, Serialization
Coordination of delivery/ creation of BY Test data in each environment - DEV, PQA, QA and Prod
Oversight of all things data migration environment to environment strategy - configuration, master and transactions as applicable
Reconciliation of accelerator tool result for uplifts across platforms
RCA for fill-out and follow-on corrective actions
Updated approach review to not repeat history for each Component load to higher environments.
Data Conversion Strategy from lower to higher environments including BY configuration preservation where applicable and legacy MARC data conversion.
LPN's with serialized hierarchies
Inventory (LPN) by location
Orders by status
Inbound
ii. Outbound
Orders not only by status including progress quantity details at header and at line item level
Inventory by Location with LPN details regarding status, committed (all of the sub-tabs)
Inventory reconciliation with ERP and Serialization