The mechanics, the timing, what you lose, what you gain, and how to price the move honestly. Three knowledge checks along the way, and 1 clip from a senior cloud advisor.
The presenter in this session is an AI generated avatar. The curriculum and guidance are real, produced by Redress Compliance analysts from our consulting engagements and market network.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. Once in the session the frame splits and a senior cloud advisor gives the view from inside real Oracle negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back, session thirty seven of forty. Session twenty seven taught you to spot the vehicle decision hidden inside a renewal proposal. Today we do the analysis properly, which is the migration from the Enterprise Agreement to the Microsoft Customer Agreement. And I want to state the framing carefully, because this session could easily read as advocacy in either direction and it should not. This is a structural change rather than a pricing one. Term, price behaviour, true up rhythm, and cash profile all move together, and you cannot take the parts you like and leave the rest. Which means the honest question is not whether MCA is cheaper, because on the benchmarks it usually is not. The honest question is which set of properties your estate actually needs over the next three years, and the answer to that turns almost entirely on whether you are growing or shrinking.
Five takeaways. One, it is a structural change: term, price behaviour, true up rhythm, and cash profile all move together, so this is not a pricing decision with administrative consequences, it is the reverse. Two, what you lose: the price lock across the term, the familiar annual true up, and whatever terms you negotiated into the EA that have no equivalent in the new paper. Three, what you gain: monthly billing, no default commitment, and the ability to change without waiting three years for a renewal boundary. Four, the default price gap: MCA default pricing ran six to fifteen percent above a negotiated EA on like for like seats, and transitions priced eight to seventeen percent above an equivalent EA renewal. Five, how to price it: same basket, full term, both routes, with growth and reduction scenarios and a rights diff, which cut final figures twelve to twenty eight percent.
What actually changes, three mechanisms, and they move together. Commitment becomes optional: the EA is a thirty six month commitment while the MCA is direct and monthly with no default commitment, and discounts attach to commitments you opt into rather than arriving with the vehicle. That is genuine flexibility, and it is also exactly where the price lock went. Price behaviour changes: the EA locks a rate for the term while the MCA floats closer to list, and over three years with a moving price list that difference compounds in a direction almost nobody models at signature. And the true up moves: the EA trues up annually at a known anniversary while the MCA trues up at subscription renewal instead, which changes your forecasting rhythm and every calendar entry from session twenty six. All three are the same trade seen from different angles: predictability exchanged for flexibility.
What you give up, five things that do not travel with you. The price lock: rates float rather than holding across the term, and that lock was worth eight to fifteen percent to a growing estate. Negotiated terms: clauses with no equivalent in the new paper, which is the absent price protection from session twenty seven. The known anniversary: one planned true up rather than several separate renewal points, which means rebuilding the session twenty six calendar. Volume aggregation: one large negotiation rather than many small ones, which is the session twenty nine point about scale and leverage. And familiarity, which is underrated and is a genuine transition cost, because your team knows how an EA behaves and will spend a year learning how the other one does. That second row costs the most and gets noticed the least, because a clause that is absent rather than removed is invisible to a price comparison.
First check. A migration proposal shows a lower monthly figure. What is the first thing to verify? A, that the discount percentage is competitive. B, that both figures cover the same basket over the same period, since MCA default pricing ran six to fifteen percent above a negotiated EA on like for like seats. C, that the billing frequency suits finance. D, that the migration date works operationally. Pause it, and as you think, remember that a lower monthly number can mean several different things, only one of which is actually about price.
The answer is B, and the benchmarks run against the migration rather than for it. MCA default pricing sat six to fifteen percent above a negotiated EA on like for like seats, and transitions priced eight to seventeen percent above an equivalent EA renewal. So a lower monthly figure is a signal that something differs between the two baskets, usually products quietly dropped, an introductory period, or a commitment you have not yet opted into. A negotiates a percentage on an unverified basket, which is the session ten error appearing for the last time in this course, and I hope by now it looks obvious. C and D are both real questions that belong after the comparison rather than instead of it, and D in particular has a way of absorbing all the planning attention that the pricing question needed. Rebuild both baskets, same products, same period, same rates, then compare.
What you get, five genuine advantages for the estates they suit. No default commitment: you are not locked to a three year volume, which matters enormously if headcount is falling or your structure is about to change. Monthly billing: a cash profile some finance functions strongly prefer, and a legitimate input rather than a decisive one. Change without a renewal boundary: under an EA most corrections wait for the anniversary, and removing that wait is worth real money to an estate that changes shape often. Simpler for smaller entities: subsidiaries, divested units, and populations below EA thresholds are frequently better served directly than folded into a large agreement. And it suits a shrinking estate, because shrinking estates on an EA overpaid by ten to twenty percent against a flexible profile. That last point is the honest headline: if your estate is contracting, the flexibility is the more valuable property rather than a consolation.
Guest analyst I want to describe a migration that was the right decision, because most of my stories are about ones that were not and that gives a misleading impression. A professional services firm in France, and they were being pushed toward the Microsoft Customer Agreement at their renewal, which they were initially inclined to resist purely because it was being pushed. So we did the sheet. Same basket, both routes, full term, per seat per month, and on the base case the MCA came out somewhere around seven percent more expensive. Which looked like the end of it. But then we added the row that most comparisons leave out, which was the reduction scenario. And this business had just divested a division, had another under review, and their own three year plan showed headcount falling by about a fifth. Under the EA those seats were committed for the term. Under the MCA they could release them as the business actually shrank. When we modelled the reduction against their own plan rather than against a flat assumption, the seven percent premium was overwhelmed several times over by seats they would otherwise be holding and paying for. So they moved, deliberately, and with a clear internal paper explaining why. And the part I liked most was that the CFO asked what would make this the wrong decision, and the answer was straightforward: if the business grows instead, we will have given up a price lock we would have wanted. They wrote that down too, which is what a real decision looks like.
A seven percent premium overwhelmed by the reduction scenario, and the risk written down beside the decision. Second check.
Check two. Your headcount is projected to fall fifteen percent over the next three years. Which route fits? A, the EA, because the price lock protects against increases. B, probably the flexible route, because shrinking estates on an EA overpaid by ten to twenty percent, and a locked rate on seats you no longer need is not protection. C, the EA, since it is what you already have. D, split the estate across both. Pause it, and ask what a price lock actually protects you from when your problem is volume rather than rate.
The answer is B. A price lock protects you against rate increases on the seats you keep, and it does nothing whatsoever about seats you no longer need, which on a contracting estate is the larger exposure by a wide margin. Shrinking estates on an EA overpaid by ten to twenty percent against a flexible profile, which is the same asymmetry from session twenty one: increases are easy and decreases are hard. C is the default this whole course has argued against, because inertia is not an analysis even when it turns out to be right. D is genuinely worth considering and is the session thirty five answer wherever populations differ. And notice the word probably in that correct answer, because it is doing real work: a fifteen percent decline concentrated in one division may suit a split, while an even decline across the estate suits a single move. Model per population, then decide.
When to move, if you move, three timing rules. Model it at nine to twelve months: open the EA against MCA analysis nine to twelve months before the anniversary, because renewals opened inside ninety days closed within three percent of the incumbent quote, and a structural change needs more runway than a price negotiation does. Never at eighty days, which is the session twenty seven rule: renew on the current vehicle if the terms are acceptable and model the migration properly for the next cycle, because a vehicle change made under time pressure is the definition of an unmodelled decision. And move populations rather than estates, since a migration does not have to be total, and moving one division or one volatile population is easier to model, easier to reverse, and usually closer to correct. One leverage point worth naming: an MCA quote priced beside the EA renewal is worth five to twelve points per session twenty nine, whichever route you choose.
Pricing the move honestly, the comparison sheet one more time. Same basket over the full term, both routes at your rates with identical products, and the benchmarks say expect the migration to price higher. Per seat per month, which is the comparison that survives headcount change, and headcount is precisely what is changing. Growth scenario: annual true up against renewal true up, where the rhythm change costs or saves depending on direction. Reduction scenario: what you can release and when under each, which is usually the deciding row on a contracting estate and was the deciding row in the story you just heard. And the rights diff: every negotiated clause, present or absent, which is the session twenty seven finding that absent beats removed for sheer invisibility. Those last two rows decide most real migrations and appear in almost no vendor comparison, which is why you build the sheet yourself.
Last check. You model both routes and the MCA prices nine percent higher. Is that the end of the analysis? A, yes, nine percent higher settles it. B, no, because the reduction scenario and the rights diff may reverse it, and on a contracting estate the ability to release seats can be worth more than nine percent. C, yes, unless the vendor improves the offer. D, no, you should simply negotiate the nine percent away. Pause it. Price is one row of the sheet, so ask yourself what the other four rows are likely to say.
The answer is B. Nine percent on the base case is a real number and it is not the whole sheet. If your estate is contracting, the reduction scenario can easily exceed it, because ten to twenty percent of overpayment on a shrinking EA is the benchmark and it arrives on seats you are contractually holding. In the other direction, a lost price protection clause can be worth more than nine percent across three years, which pushes the conclusion back the other way, and both of those calculations use your numbers rather than anybody's argument. A stops the analysis at the row that is easiest to compute, which is a very human thing to do. C treats the vendor's offer as the only variable when your own growth profile is by far the larger one. And D assumes a nine percent structural gap is negotiable to zero, when the benchmarks suggest it is a property of the vehicle rather than of the negotiation.
The migration method, three steps, and the first is a projection rather than an analysis. One, project the estate: headcount and seat count over the next three years, per population, with the confidence you genuinely have. Growing, flat, or shrinking is the single largest input into this decision, and your organisation already knows the answer, it simply has not been asked in this context. Two, build the five row sheet: same basket over the full term, per seat per month, growth scenario, reduction scenario, rights diff, both routes at your rates, which is about a fortnight of work to settle a three year question. Three, decide per population, because the answer can differ between the core estate and a volatile subsidiary, and a partial migration is easier to model and easier to reverse. And separate the price decision from the vehicle decision in writing whenever both arrive in one pack.
Session thirty seven, three sentences. One: migration is a structural change rather than a pricing one, exchanging the price lock, the known anniversary, and your negotiated terms for monthly billing, no default commitment, and the freedom to change without a renewal boundary. Two: the benchmarks run against the move, with MCA default pricing six to fifteen percent above a negotiated EA on like for like seats and transitions pricing eight to seventeen percent above an equivalent EA renewal, so a lower headline usually means a different basket. Three: direction decides it, because shrinking estates on an EA overpaid by ten to twenty percent while growing estates gained eight to fifteen percent from the lock, so project the estate first and decide per population. Next session takes the product this course has spent the most time on and asks what happens when it goes properly big.
Homework, about an hour, and this week you project and price. One, project three years: seat count by population, growing, flat, or shrinking, using the business plan rather than a guess and marking clearly where you are uncertain, because the uncertainty is itself an input. Two, price the same basket twice: your top SKUs by spend, under your negotiated EA rates and under MCA default pricing, per seat per month. Three, add the reduction row: what could you release under each route and when, because on a contracting estate this row usually decides the whole question. Four, diff the rights, from session thirty's list of what you hold, marking which have an equivalent under the other vehicle and which simply do not exist there. Five, write the recommendation per population, one line each with the reason, and that is the paper you take into the renewal.
Five reads before next session, all free on redress compliance dot com. First, the Microsoft EA to MCA renewal guide, which carries the fork in full: structure, pricing, audit posture, and timing. Second, the CIO level playbook on evaluating renewal proposals across EA, MCA, and CSP, which is the same basket priced three ways and is essentially this session's comparison sheet. Third, CSP against the Enterprise Agreement, for the growth direction argument with the seat band numbers behind it. Fourth, the French professional services MCA strategy case study, which is a migration that was genuinely right and sets out the reasons why, and it is the written version of the story in this session. And fifth, the EA renewal twelve month playbook, for where in the timeline this modelling actually has to happen. Next session is Copilot at enterprise scale: the rollout, the ramp, the consumption tail, and the renewal that follows the first full year. See you there.