INFOSYS 220 Chap.11 Migration, Operations and Maintenance
Migration, Operations and Maintenance
Make readiness an evidence decision
Implementation does not end when construction passes a test. The organisation must prepare data, users, procedures, infrastructure, support and ownership for live service. Migration includes mapping, cleansing, rehearsal, validation and recovery planning. Training should address real roles and tasks, not only interface tours.
A readiness review brings these streams together and states which residual risks are accepted, mitigated or too serious for release.
Transfer a service that can endure
Operational handover assigns monitoring, incident response, access administration, backup, vendor coordination and benefit review.
Maintenance then corrects faults, adapts the system to environmental change, improves capability and prevents deterioration. The captured Week 11 material names migration, operations and maintenance but does not supply a detailed named conversion taxonomy, so analysis should use supported readiness reasoning and current course instructions rather than memorised labels presented as course fact.
What this chapter covers
- 01
Data mapping, cleansing, rehearsal and validation
- 02
Training by role and operational procedure
- 03
Technical, business and support readiness evidence
- 04
Release risk, recovery and accountable approval
- 05
Operational ownership, monitoring and incident response
- 06
Corrective, adaptive, perfective and preventive maintenance reasoning
Worked example · free
Decide readiness for a case system
- 2Separate product acceptance from operational readiness.
- 2Assess data and recovery risks.
- 2Assign ownership and evidence.
- 2State a conditional decision.
Key terms
- Data Migration
- The controlled extraction, transformation, transfer and validation of data into a target environment.
- Readiness Review
- A decision point evaluating whether product, people, process, data, technology and support evidence permit release.
- Operational Handover
- Transfer of service knowledge, controls, assets and accountability from delivery into continuing operation.
- Incident
- An unplanned interruption, degradation or security event requiring managed response and restoration.
- Maintenance
- Post implementation work that corrects, adapts, improves or protects a system.
- Benefits Owner
- The role accountable for monitoring whether expected organisational value appears and is sustained.
- Rollback
- A prepared recovery action that restores an earlier service or data state when release fails.
Migration, Operations and Maintenance FAQ
Why can a tested system still be unready?
Product tests may not prove migrated data quality, staff capability, monitoring, support coverage, infrastructure capacity or recovery. Readiness brings those evidence streams into one decision. A technically acceptable product can still create unacceptable operational risk.
What should migration validation include?
Check record counts, identifiers, required fields, transformations, relationships, permissions and representative business outcomes. Investigate exceptions rather than hiding them in an aggregate total. Rehearsal should also confirm timing, ownership, reconciliation and recovery if the transfer cannot be accepted.
What belongs in operational handover?
Handover should identify service ownership, support routes, monitoring, access administration, backup and recovery, supplier contacts, known issues, operating procedures and benefit review. The receiving team needs usable knowledge and authority, not merely a folder of project documents.
How should maintenance requests be assessed?
Trace the request to evidence and classify its effect on value, risk, architecture, data, tests and operation. A small interface change can affect training or accessibility, while an environmental change may require urgent adaptation. Use controlled prioritisation rather than assuming all post launch work is defect repair.
Exam move
Create a readiness checklist with product, data, people, process, technology and support columns. For each item, write evidence, owner, status, residual risk and decision date. Design a migration rehearsal for a small dataset: define mapping rules, expected counts, exception handling, relationship checks and rollback triggers. Write a training task for each role using real scenarios, including one error or recovery route.
Build an operational handover card naming monitoring signals, incident contacts, access administration, backups, vendor dependencies and benefits ownership. Then run a mock readiness meeting. Require every green claim to cite evidence and every exception to have an authorised disposition.
After release, classify sample changes as fault correction, environmental adaptation, improvement or prevention, but focus on the consequence rather than the label alone. Trace one change back to requirements and forward to design, data, regression testing, documentation and training.
For the final exam, stay within the available course materials: explain migration, operations and maintenance with readiness evidence, and do not present a detailed conversion method taxonomy as though it were explicitly taught. A strong answer makes ownership and ongoing value as visible as the technical launch.
Working through Migration, Operations and Maintenance in INFOSYS 220? Sia is AskSia’s AI Information Technology tutor — ask any INFOSYS 220 Migration, Operations and Maintenance question and get a clear, step-by-step explanation grounded in how INFOSYS 220 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.