Objective

Safely replace the public Ruby version with the new haih-cms website. After the transition, the old application will be kept as a backup and a reference source for verification, but not as a parallel production system.

What to do

• Verify the readiness of the new version regarding data, pages, forms, SEO, and redirects.
• Prepare the sequence for a one-time switch.
• Define control checks immediately after launch.
• Maintain the capability for a short-term technical rollback in case of a critical error.
• Do not design continuous data synchronization or long-term operation of both websites simultaneously.
• After successful stabilization, consider haih-cms as the sole active production website.

Result

There is a simple plan to replace the legacy website with the new implementation and a fallback scenario in case of a critical issue during launch.

Definition of Done

• Necessary data is migrated before the switch.
• The new version has passed testing.
• Post-launch control checks are defined.
• Parallel operation of the two systems is not required.