SDLC activities and data migration: In which phase of the Software Development Life Cycle is file (data) conversion typically planned and executed to move from the old system to the new system?

Introduction / Context:File conversion (or data migration) is the process of extracting, transforming, cleansing, and loading data from legacy sources into a new system. Its timing within the SDLC matters because it must align with cutover plans, user acceptance, and operational readiness to ensure a smooth go-live without data loss or corruption.

Given Data / Assumptions:

• Legacy data structures differ from the target schema.
• Users expect historical and open transactional data to be present at go-live.
• Conversion must be controlled, validated, and repeatable.

Concept / Approach:Although the analysis and design phases define what to convert and how to map fields, the actual execution of conversion runs during System Implementation (also called deployment or cutover). Activities include rehearsal migrations, reconciliation reports, defect remediation, and the final production cutover window. Implementation integrates technical scripts with operational steps such as user freezes, backups, and sign-offs.

Step-by-Step Solution:

Verification / Alternative check:Project plans typically schedule mock conversions before go-live, then a final “T-minus” conversion during the implementation weekend, aligning with operational readiness checklists.

Why Other Options Are Wrong:Analysis/design/development prepare the mappings and tools; the actual production migration occurs in implementation.

Common Pitfalls:Insufficient data cleansing; lack of reconciliation; attempting one-shot conversion without dress rehearsals.

Final Answer:System Implementation