FinOps Academy · Resource

Migration Playbook

A controlled approach for moving workloads, pipelines or operating models safely.

Discover current state

Apply this section specifically to FinOps Academy. Record assumptions, commands, screenshots, decisions, validation results and rollback evidence where relevant.

□ State the objective and expected outcome.
□ Identify dependencies, risk and failure signals.
□ Execute the smallest safe validation step.
□ Capture evidence that another engineer can review.

Classify dependencies and risk

Apply this section specifically to FinOps Academy. Record assumptions, commands, screenshots, decisions, validation results and rollback evidence where relevant.

□ State the objective and expected outcome.
□ Identify dependencies, risk and failure signals.
□ Execute the smallest safe validation step.
□ Capture evidence that another engineer can review.

Design target and rollback

Apply this section specifically to FinOps Academy. Record assumptions, commands, screenshots, decisions, validation results and rollback evidence where relevant.

□ State the objective and expected outcome.
□ Identify dependencies, risk and failure signals.
□ Execute the smallest safe validation step.
□ Capture evidence that another engineer can review.

Pilot and validate

Apply this section specifically to FinOps Academy. Record assumptions, commands, screenshots, decisions, validation results and rollback evidence where relevant.

□ State the objective and expected outcome.
□ Identify dependencies, risk and failure signals.
□ Execute the smallest safe validation step.
□ Capture evidence that another engineer can review.

Migrate in waves and stabilise

Apply this section specifically to FinOps Academy. Record assumptions, commands, screenshots, decisions, validation results and rollback evidence where relevant.

□ State the objective and expected outcome.
□ Identify dependencies, risk and failure signals.
□ Execute the smallest safe validation step.
□ Capture evidence that another engineer can review.

Quality standard

Reusable by someone who was not present.

A strong resource removes ambiguity. It states prerequisites, decision points, commands, validation, rollback and ownership clearly enough for another engineer to execute safely.