Playbook
0 / 10 complete0%
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07
  8. 08
  9. 09
  10. 10
Step 08 of 10 4-12 months· advanced

Step 8: Decommission IBM i

Turn off IBM i. Sequence: read-only IBM i → selective subsystem shutdowns → data archive → hardware decommission (or contract termination if PowerVS) → license cancellation.

What you're doing in this step

Block writes to IBM i (writes go to new). Disable subsystems, scheduled jobs, and IWS endpoints one at a time. Archive historical data to cheap, queryable storage for compliance. Decommission hardware (or terminate the PowerVS / Skytap contract). Cancel every IBM, third-party software, scheduling, and monitoring license explicitly.

Recommended prompts

Use one of these to do the work in your IDE

Open the template to read it in full. Click Copy prompt to grab it (with your stack values pre-filled where they apply) — then paste into Claude Code, Cursor, or wherever you build.

Primary recommendation 1 day to write

Migration Cutover Runbook

Detailed step-by-step runbook for the actual cutover from legacy to new system, including verification, communication, and rollback.

View template
Template· Template 0.5-1 day

Migration Rollback Plan

Plan recovery procedures for when migrations fail at any stage — from pre-cutover bugs to post-cutover production incidents.

Use this when: Pre-flight check — make sure the rollback path is documented and rehearsed before the first shutdown

View template
Recommended skills

Drop these into Claude Code for this phase

Skills auto-trigger on the right kind of request. Install once; they apply to every prompt that fits.

Skill· Skill 5 min setup

Migration Planner Skill

Flagship migration skill that walks Claude Code through audit → strategy → slicing → cutover for any legacy system migration.

claude-code
View skill
Skill· Skill 5 min setup

Documentation Skill

Claude Code skill that generates README, API docs, JSDoc, ADRs, and other docs that match the project's existing voice and depth.

claude-code
View skill
Recommended MCP configs

Wire these tools into Claude Code first

MCP servers give Claude Code direct access to external systems (Jira, browsers, databases). Configure once.

MCP config· MCP config 10 min setup

Azure DevOps MCP for Evoke

Pre-configured Azure DevOps MCP server for Claude Code — work items, repos, PRs, and pipelines from chat.

claude-codemcp
View config
MCP config· MCP config 10 min setup

Confluence MCP for Evoke

Pre-configured Atlassian Confluence MCP server for Claude Code — search, read, and write internal documentation pages from chat.

claude-codemcp
View config
MCP config· MCP config 5 min setup

Filesystem MCP for Evoke

Pre-configured filesystem MCP server for Claude Code — safe, scoped read/write access to project files.

claude-codemcp
View config
When you're done

Verify these in your own work before moving on

This is a checklist for you to mentally tick off in your repo and IDE — the site doesn't track it, you do.

  • IBM i write traffic = 0% for 30+ consecutive days
  • All scheduled batch decommissioned
  • All subsystems / services stopped
  • All data archived to long-term storage
  • All integrations confirmed off IBM i
  • IBM i hardware decommissioned (or PowerVS / Skytap contract terminated)
  • All vendor licenses cancelled
  • Final cost reduction verified
Common pitfalls

What goes wrong at this step

  • Decommissioning too fast — read access for 6-12 months catches forgotten consumers
  • No data archive — compliance requires keeping data; archive cheaply but accessibly
  • Forgetting license costs — they keep billing until cancelled
  • Missing integrations — manufacturing floor, EDI partners, custom interfaces all need explicit redirect
← Previous step

Command Palette

Search for a command to run...