Cutover Readiness Reviews: Exit Criteria for a Small Data Center Move

1 Matrix Tech editorial ·

Wikimedia servers for the ULSFO caching data center being racked on June 6th, 2013 in San Francisco.
Illustrative image. Mutante · CC BY-SA 3.0 · Cropped and resized. Image source

Before any rack is unplugged, a small business should be able to say in plain terms what done looks like. 1 Matrix Tech publishes this guide at 1matrixtech.net for small teams planning a data center migration who want a clear way to decide whether a cutover is ready, not just whether the calendar says it should happen. Most migration problems do not come from the move itself. They come from unclear success conditions, untested dependencies, and approvals that nobody wrote down. A readiness review turns those vague worries into specific yes-or-no questions that a person can answer before the date arrives.

Define exit criteria before you touch hardware

An exit criterion is a measurable statement that must be true before you consider a system moved and safe to rely on. Examples include: the application loads for a test user from the new location, a scheduled job completes and writes its output, backups restore a sample file to a clean target, and the people who depend on the system can complete their most common task. Write these down for each system in scope, not for the project as a whole.

Avoid criteria like 'everything works.' Nobody can verify that. Instead, name the specific checks, the person responsible for each one, and the evidence that proves it passed. A simple table in a shared document works: system name, check, owner, evidence location, and status. If a check cannot be written this way, the system probably needs more mapping before cutover.

Run a dress rehearsal with a rollback decision point

A dress rehearsal is a trial run of the cutover steps against a copy or a staging environment. Its purpose is to reveal sequencing errors, missing credentials, and timing surprises while the production systems are still untouched. Record how long each step actually took, not how long you hoped it would take. Those timings drive the real schedule.

Every rehearsal should also define a rollback decision point: the last moment at which you can return to the original environment without losing data written since the move began. Decide in advance who has the authority to call that rollback, what evidence triggers it, and how long the team will wait before deciding. Writing these answers during calm planning prevents hesitation and arguments during a stressful window.

Check approvals, contracts, and third-party dependencies

Many moves stall because someone discovers on the day that a license is tied to the old hardware, a vendor requires notice before a change, or a support contract does not cover the new location. Build a short inventory of every licensed product, service agreement, and external integration that touches the systems being moved. For each one, record who holds the account, whether a notice period applies, and whether the new location is covered.

This is also the point to confirm internal sign-offs. Who approves the window? Who must be notified if a business process is interrupted? Who can authorize spending on an unexpected part? Writing these names down removes ambiguity. This guidance is general planning practice; check any contractual or legal questions with the appropriate professional for your business.

Use a short go or no-go checklist

On the final day before cutover, hold a brief go or no-go meeting. Walk through a checklist and require a clear answer to each item. A practical list includes: Are current backups verified within the agreed window? Has the rollback point been confirmed with its owner? Are all rehearsal exit criteria marked passed with evidence attached? Are the people needed during the window available and reachable? Are vendor notices sent and acknowledged? Is there a written communication plan for users if the window runs long?

If any answer is 'probably' or 'I think so,' treat it as a no. Delaying a move by a week costs far less than discovering a missing credential at two in the morning. A go decision should be recorded with the names of the people who made it and the time it was made, so the team can review what they knew at that moment if questions come up later.

Close the move with a verification record

Cutover is not finished when the last server powers on. It is finished when the exit criteria are verified against the new environment and the verification is recorded. Keep the old environment in its agreed holding state until the business confirms that nothing depends on it, then document when and how it was decommissioned.

Store the readiness checklist, the rehearsal timings, the approvals, and the final verification record together. A small business that repeats a move in a few years will benefit enormously from knowing what was assumed, what was tested, and what surprised the team the first time.

Part of the ToddMichael.tv network.