Migration timing, against the cycle.

Migration timing relative to the renewal cycle starts with reading the cycle itself. A Red Hat enterprise renewal cycle is typically a twelve to fifteen month conversation that begins with the seller side opening a discovery call somewhere between nine and twelve months before the contract end date, proceeds through a sequence of meetings and draft proposals across the middle quarter of the cycle, and reaches a closing window in the final sixty to ninety days before contract expiry. Each phase of the cycle has its own seller side posture and its own buyer side opportunity to place leverage on the desk. The exit planning posture has to be timed against the phase the cycle is in.

A buyer side reading of the cycle therefore reads the calendar before reading the destination. The destination question is the engineering question. The calendar question is the commercial question. Both are necessary; the calendar question carries more arithmetic weight because the destination only produces a renewal effect if it is placed on the desk inside the window the cycle leaves open for it. A destination announced in the wrong phase of the cycle is structurally weaker than a destination announced in the right phase, regardless of how credible the destination itself is.

The companion notes on the exit planning service, on the credible migration plan as leverage, on how leaving Red Hat changes the current contract, and on communicating the migration plan internally sit on adjacent surfaces. This note covers the timing.1

The renewal cycle, across observed engagements, divides into four phases that the buyer side can read with reasonable consistency. Each phase has a window of weeks within which a particular kind of leverage is most effective; each phase carries its own structural limitations on what the buyer side can introduce without disturbing the cycle in counterproductive ways.

The first phase is the strategic window, running from roughly twelve to nine months before contract end. The seller side is opening discovery calls, asking about strategic direction, and beginning the qualification of the renewal as a baseline retention, a growth opportunity, or a contested account. This is the right phase to plant the seed of the exit conversation in soft terms. The buyer side does not need a plan in this phase; the buyer side needs to communicate that the renewal is contested and that the destination question is being considered. The seller side reads the early signal and begins to prepare the response.

The second phase is the discovery window, running from roughly nine to six months before contract end. The seller side is requesting deployment data, proposing technical workshops, and assembling the proposal narrative. This is the phase in which the buyer side should run the actual discovery for the destination question. The workload classification, the ISV matrix reading, the platform team capacity assessment, and the cost model construction all sit inside this window. The plan is being drafted; the plan is not yet on the desk.

The third phase is the proposal window, running from roughly six to three months before contract end. The seller side is putting numbers on the page; the buyer side is reading them against the benchmark. This is the phase in which the plan moves from the drafting room to the renewal table. The plan does not have to be complete in every detail; the plan has to carry the five signals named in the companion note on the credible migration plan. The first concession band response from the seller side typically lands inside this window.

The fourth phase is the closing window, running from roughly three months to contract expiry. The seller side is finalising terms; the buyer side is closing on language. The plan does not change inside this window; the plan is now the position from which the contract terms are negotiated. The terms that move inside this window are the durable language clauses covered in the companion note on contract movement: price protection, term length, scope, termination, and true up mechanics.2

Two timing errors recur with sufficient regularity across observed engagements that they are worth naming directly. Each carries a specific cost on the realised arithmetic; each is addressable with discipline rather than with additional engineering effort.

The first error is naming the destination too early. Buyers who announce the destination in the strategic window, before the discovery has run, before the plan is drafted, and before the calendar is set, frequently produce a worse outcome than buyers who hold the destination quiet through the discovery window. The mechanism is that the seller side has time to absorb the threat, to position the response, and to neutralise the destination through softer concessions that arrive early in the cycle and that the buyer side has not yet read the benchmark against. The early discount that lands in the strategic window is frequently smaller than the discount that would have landed in the proposal window had the destination been timed correctly.

The second error is naming the destination too late. Buyers who arrive at the closing window with a destination that has not previously been signalled produce a worse outcome than buyers who placed the destination on the desk in the proposal window. The mechanism is that the seller side, inside the closing window, has limited latitude to rewrite the deal structure; the seller side is in a posture of finalising rather than redrafting. The destination announced in the closing window can only produce a discount on the line price; it cannot move the durable language clauses because those clauses are now substantially fixed.3

The discipline that avoids both errors is the discipline that reads the cycle before the destination. The strategic window carries the soft signal. The discovery window carries the internal drafting. The proposal window carries the plan on the desk. The closing window carries the language. Each posture in its own phase. The right destination in the wrong phase produces the wrong outcome.

A separate timing question arises when the migration calendar cannot realistically complete before the renewal date. This is the question of contractual overhang covered in the companion note on the hidden cost of migration. The question for the timing surface is what to do when the discovery phase reveals that the migration cannot finish inside the residual term.

The three available answers each have their own arithmetic. The first answer is to time the migration against the renewal that follows the current one. The current renewal is signed with the destination held in posture; the actual migration executes across the term of the renewal that was just signed, with completion timed to the renewal after that. The arithmetic across the two cycles is materially better than the arithmetic of an aggressive migration against the current renewal, because the contractual overhang line is removed.

The second answer is to negotiate the current renewal at a shorter term with partial term exit language. A one year renewal at the same unit price as the prior three year deal, with explicit language permitting early termination on a quarter notice, is a stronger position for an exit calendar that needs eighteen months to complete than a three year renewal at a discounted unit price with no exit language. The companion note on three year commit protections covers the term length negotiation.4

The third answer is the hybrid posture. Migration executes on the workloads where the calendar can complete inside the residual term; the workloads where the calendar cannot complete stay on RHEL through the next cycle and migrate in the following one. The companion note on hybrid RHEL and alternative posture covers the split. Each of the three answers is honest; the right answer for any individual estate depends on the realised capacity, the residual term, and the strategic horizon.

The inverse question, less commonly observed but worth naming, arises when the migration calendar is already in flight and the renewal cycle has to be read against the migration milestones rather than the other way round. Estates with a board approved migration in execution at the start of a renewal cycle are in a different timing posture; the destination is no longer a credibility question because the migration is already happening. The renewal conversation is now about residual entitlement, term length on the residual, and exit language across the migration window.

The seller side posture in this case is materially different from the standard renewal posture. The account team is no longer trying to defend the full account; the account team is trying to defend whatever residual entitlement can be preserved. The buyer side has a strong negotiating position on the residual; the durable language clauses are highly accessible because the seller side has limited alternative posture to defend. The observed concession bands in this configuration sit at the upper end of the full exit planning range, frequently between 55% and 75% off the prior line price on the retained footprint.

The discipline that produces the upper band is the discipline that documents the migration progress against the calendar in writing, presents the documentation to the seller side at the start of the proposal window, and negotiates the residual contract against the documented progress. A migration in flight without the documentation reads as a verbal threat; a migration in flight with the documentation reads as commercial reality the seller side has to respond to.5

The companion notes on the rest of the exit planning surface, including the practice hub at exit planning and the article on the credible migration plan as leverage, sit adjacent. The contact form at the engagement section returns a desk response on the timing question typically inside the business day.

The timing discipline that produces the upper band outcome is rarely complicated; the difficulty is in the holding rather than in the execution. The discipline says start the discovery in the discovery window; do not announce the destination in the strategic window; place the plan on the desk in the proposal window; negotiate the language in the closing window. The discipline says nothing about the destination itself; the destination decision is upstream of the timing decision.

The most common reason the timing discipline fails is internal pressure to communicate the destination too early. Executive sponsors, finance teams, and steering committees frequently want to know what the plan is at the strategic window, before the discovery has produced a defensible answer. The remedy is the internal communication discipline covered in the companion note. The destination is communicated internally under controlled circulation in the discovery window; the destination is communicated externally only when the plan is in writing and the proposal window has opened.

The buyer side line that holds across every exit planning cycle is the line worth holding on the steering committee paper. The cycle is the calendar against which the plan is read. The plan is the document that does its work in the proposal window. The destination is the engineering question that the discovery window answers. Reading the three in order, and timing each against its window, is the work that converts a verbal threat into a written outcome. Reading them out of order is the work that converts a written plan into a verbal threat.

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.