The credible migration plan, as leverage.
The credible migration plan is the document that does the work of the exit destination at the renewal table. The seller side reads the plan for a small set of specific signals; the signals the plan demonstrates determine the seller side response. A plan that demonstrates the signals can rewrite the renewal sheet without ever being executed. This note sets out what makes a plan credible, the five signals the account team reads for, the structural features of the document itself, and how the calendar does its work.
The plan, as deliverable.
The credible migration plan is the deliverable of the exit planning service. Across the cohort of engagements that the practice has carried in the trailing twelve months, the document that landed on the desk between the discovery phase and the renewal table was the artefact that the seller side read and the artefact the buyer side commercial team referenced through signature. The execution of the plan was a separate decision the buyer side reached at a later date, frequently in the negative, on the strength of the rewritten contract that the plan had already produced. The plan was the deliverable; the migration was the leverage.
A buyer side reading of the plan therefore reads the plan as a commercial document first and an engineering document second. The engineering content is necessary; without it the plan is not credible. The commercial content is what produces the rewritten renewal sheet. Drafting the plan with both readings in mind is the discipline that distinguishes a plan that does its work from a plan that produces a steering committee deck and nothing else.
The companion notes on the exit planning service, on how leaving Red Hat changes the current contract, on communicating the migration plan internally, and on migration timing relative to the renewal cycle sit on adjacent surfaces. This note covers the document itself.1
The five signals the seller side reads for.
The Red Hat account team, faced with a migration plan placed on the renewal desk, reads the plan for a small set of specific signals. The signals determine the seriousness of the response. Each signal is observable in the document itself, each is something a serious plan can demonstrate, and each is something a careless plan typically fails to demonstrate without the buyer side being aware.
The first signal is the named destination. A plan that says alternative without specifying which alternative is structurally weaker than a plan that names Rocky Linux, AlmaLinux, Oracle Linux, SUSE Liberty, a specific cloud managed Kubernetes destination, or another credible target by name. The name tells the seller side that the discovery phase has run, that the engineering organisation has reached a candidate, and that the procurement organisation has a path to a contract on the alternative side. The name does not commit the buyer to execute; it commits the buyer to seriousness.
The second signal is the dated calendar. A plan that says soon is structurally weaker than a plan with dates against named milestones. The dates tell the seller side that a project plan exists in writing, that the milestones have been sized against the available capacity, and that the project organisation has reached a defensible reading of the timeline. Round dates ending in calendar quarters are stronger than vague horizons; specific dates against specific tasks are stronger still.
The third signal is the owner column. A plan that names tasks without naming owners is structurally weaker than a plan that names an owner against every milestone. The owner column tells the seller side that the project organisation has been stood up, that the budget has been allocated against named line items, and that the execution does not depend on a single individual whose departure would shelve the project. The plan with named owners survives the account team first question about staffing.2
The fourth signal is the contingency posture. A plan that says we will migrate is structurally weaker than a plan that says we will migrate under these conditions and we will hold under these other conditions. The contingency column tells the seller side that the buyer side has thought through the failure modes, has documented the resilience case in writing, and is not bluffing on either the trigger or the hold conditions. The seller side can rebut a bluff; the seller side cannot rebut a documented contingency.
The fifth signal is commercial readiness. A plan that has been read by procurement, signed off by finance, and reviewed by legal carries materially more weight than a plan that lives inside the platform team. A plan that has the alternative vendor on a call sheet, a draft contract from the alternative side under review, and an executive sponsor against the migration line item carries the maximum weight the document can carry. Commercial readiness is the signal that moves the seller side from visible response to structural contract rewriting.
| Signal | What the plan demonstrates | What the seller side cannot say |
|---|---|---|
| Named destination | Discovery phase complete, candidate selected | That the plan is hypothetical |
| Dated calendar | Milestones sized against capacity | That the project is unscoped |
| Owner column | Budget allocated, staff assigned | That the project will shelve |
| Contingency posture | Failure modes documented | That the buyer is bluffing |
| Commercial readiness | Procurement, finance, legal aligned | That the buyer is not serious |
The structural features of the document itself.
Beyond the five signals, the document itself has structural features that determine whether the plan reads as credible or as performative. The plan is a document; the document is read by humans on the seller side who are professionally trained to assess seriousness; the structural features the document carries are what those humans read against.
The first structural feature is a written executive summary that names the destination, the calendar, and the contingency posture in the opening paragraph. The summary is the only section the senior seller side reader will consume in full on first reading; the summary has to carry the load. The companion note on communicating the migration plan internally covers the summary discipline in detail.
The second structural feature is a workload classification table that names every load bearing application in scope, the destination assigned to it, the ISV matrix status, and the calendar quarter the workload moves in. The table tells the seller side that the discovery phase produced a real reading rather than an estimate, and that the plan is drawn from the actual estate rather than from a generic template.
The third structural feature is a cost model that names both the recurring saving and the one time execution cost, and that reads the cost across at least three years rather than one. A cost model that reads only the first year is structurally weak because the seller side knows the first year of any migration is the most expensive year; the three year model is the model the seller side cannot rebut on the first year cost line. The companion note on the hidden cost of migration covers the cost model itself.3
The fourth structural feature is a section on the seller side relationship and the renewal posture. This is the section that, more than any other, signals that the plan is a commercial document rather than only an engineering document. The section names the contract on the desk, the terms the buyer side is willing to accept, and the posture under which the migration would be held in favour of the renegotiated renewal. The seller side reads this section closely; it is the section that signals what response will close the conversation without the migration executing.
How the plan does its work.
The plan does its work through a structural mechanism that is worth naming directly. The Red Hat account team operating in 2026 carries a compensation structure that rewards revenue retention and revenue growth across the named account portfolio. The compensation structure does not reward losing the account at a steeper discount; the compensation structure does penalise losing the account entirely. The credible migration plan moves the account team from a posture in which the discount is the variable to a posture in which the retention is the variable. The shift is the leverage.
A plan that carries all five signals and the four structural features puts the account team in a position in which the plausible outcomes are a rewritten contract or a lost account. The rewritten contract is materially better for the account team than the lost account. The discount the account team can accept under that framing is materially larger than the discount the account team can accept under the framing in which the discount is the only variable. The plan does not negotiate the discount directly; it changes the structure of the conversation in which the discount is negotiated.4
The observed concession bands across renewal contracts that landed on a plan carrying all five signals fell between 41% and 71% off the opening Red Hat number, across the eighteen engagements in the trailing twelve months that produced a credible written plan. The bands across renewal contracts that carried only three of the five signals fell between 19% and 38%. The difference is not the size of the buyer, the product mix, or the region. The difference is the document.
The buyer side discipline that produces the upper band outcome is the discipline that drafts the plan, reads the plan as the seller side will read it, and revises the plan until every one of the five signals is present in writing. The plan is not the destination; the plan is the deliverable. The renewal is the outcome. The companion notes on the rest of the exit planning surface, including the practice hub at exit planning, sit adjacent. The contact form at the engagement section returns a desk response on the plan question typically inside the business day.5
When the plan fails to do its work.
Not every plan does its work. Across observed engagements that produced disappointing renewal arithmetic despite an exit planning posture, the recurring pattern was a plan that read as performative rather than as credible. The plan was placed on the desk; the seller side read it; the seller side did not respond with the structural rewriting that the plan was intended to produce. Reading the failure modes in advance is the discipline that prevents the document from becoming the artefact of an unsuccessful posture.
The first failure mode is the plan that names a destination but cannot demonstrate the discovery phase that selected the destination. The seller side reads the gap as evidence that the candidate is notional rather than considered. The remedy is to attach the discovery output to the plan as a structured appendix rather than leaving it inferred. The second failure mode is the plan with no owner column. The seller side reads the absence as evidence that the project will not survive the first staffing change on the buyer side. The remedy is to insert the owner column and to populate it with names that the seller side recognises as senior enough to carry the project through.
The third failure mode is the plan with a calendar that does not survive the question why this calendar. The dates have to be drawn from the available capacity, the ISV constraints, the residual term of the Red Hat contract, and the strategic horizon of the wider organisation. A calendar that reads as arbitrary is a calendar the seller side rebuts. The remedy is the discovery phase, the workload classification, and the realistic capacity reading covered in the companion note on the hidden cost of migration.
The buyer side line that holds across every plan engagement is the line that holds across every credible commercial document. The plan that defends in writing is the plan that does its work. The plan that does not defend in writing is the plan that produces a partial concession at best and a confirmation of the opening number at worst. The five signals and the four structural features are the discipline. Drafting the document to carry all of them is the work the exit planning service is engaged to do.
Notes & references
- 1. The credible migration plan is the principal deliverable of the exit planning service. The execution of the plan is a separate decision the buyer side reaches downstream; the document is what produces the rewritten renewal sheet. See practice notes on document construction.
- 2. The owner column is the structural feature most often missing in plans that fail to do their work. A plan that survives a staffing question is a plan that names the owner against every milestone. A plan that does not survive that question reads as a project that will shelve before execution.
- 3. The three year cost model is the model the seller side cannot rebut on the first year cost line. Plans that read only the first year invite seller side rebuttal on the realised execution cost; plans that read three years carry the full arithmetic of the migration.
- 4. The structural mechanism through which the plan does its work is the shift in the account team framing from discount as the variable to retention as the variable. The shift is what produces the upper band concession outcome; without the shift the discount remains the variable and the band remains narrower.
- 5. Concession bands reflect the practice observation across signed renewal contracts in the trailing twelve months. Sample size for the cohort that carried all five signals is eighteen engagements; sample size for the cohort that carried three signals is twelve engagements. Bands are observations, not promises.
- 6. The plan that does not defend in writing is the plan that produces a partial concession or none. The remedy is structural: insert the missing signal, populate the missing column, attach the missing discovery appendix. The plan can be revised across the discovery phase; the signals do not have to be present at first draft.
Preparing a response? The practice keeps a one-page Red Hat audit response checklist — what to acknowledge, what to preserve, and what not to volunteer in the first fourteen days after the letter arrives.