Systems conversion strategies: the technique where the old system is removed and the new system is switched on immediately is called

Introduction / Context:
Organizations adopt different go-live strategies when replacing systems. The riskiest but fastest is to replace the old system with the new one in a single step, often called crash or direct cutover conversion.

Given Data / Assumptions:

• “Immediately implementing the new system” means no overlap or dual running.
• Risk tolerance is higher; there is no fallback after cutover except rollback plans.
• Other strategies (pilot, phased, parallel) reduce risk but increase effort/time.

Concept / Approach:
Map each conversion name to its behavior: direct (crash) = instant switch; phased = module by module; pilot = limited scope first; parallel = both systems run together.

Step-by-Step Solution:
1) Identify the described pattern: immediate replacement.2) Match to terminology: direct cutover / crash conversion.3) Select the matching option.

Verification / Alternative check:
Implementation playbooks define direct cutover as the fastest path with highest operational risk.

Why Other Options Are Wrong:
Phased: gradual rollout. Pilot: trial subset first. Parallel: both systems run concurrently for a period. Shadowing: new system mirrors old without being authoritative.

Common Pitfalls:
Choosing parallel when the prompt clearly states “totally removing the existing system.”

Final Answer:
Crash (direct cutover) conversion.