This post explains what actually changes when you move off a standalone SharePoint Online or OneDrive for Business plan, and why treating it as a routine license swap is where organizations get caught. It covers Microsoft’s confirmed retirement timeline, the difference between settings that carry over and entitlements that silently stop working, the storage ceilings that shrink without warning, the compliance capabilities that have to be rebuilt in Microsoft Purview rather than migrated, and where the unbudgeted costs actually come from. If you hold SharePoint Online Plan 1 or Plan 2, or OneDrive for Business Plan 1 or Plan 2, the decision point is closer than the 2029 end-of-service date suggests.
The Timeline, and Where We Already Are
Microsoft’s Partner Center advisory, dated January 28, 2026, sets out the chain. End of sale was June 2026, with no new tenants or customers after May 31, 2026 and renewals for existing customers only. End of life is January 2027, when renewals stop and existing contracts continue until expiration. End of service is December 2029, when the standalone plans are fully retired and customers must move to Microsoft 365 suites, capacity packs, or pay-as-you-go storage.
Two of those matter right now.
The first has already happened. You cannot buy these plans as a new customer any more. If your organization is holding them, you are holding something that is no longer sold.
The second is the one that forces a decision. After January 2027, renewals stop. Your contract still runs to its expiry, but there is no renewal on the other side of it. Whatever your renewal date is, that is the date you need a destination plan chosen, licensed, and validated.
December 2029 is the date most coverage leads with. It is also the least useful one, because by the time it arrives the decision was made years earlier, either deliberately or by default.
Why “It’s Just a License Change” Is the Expensive Assumption
Here is the part that catches people, and it is subtle.
Change a user’s license inside the same tenant and your content does not move. Sites stay. Files stay. Libraries, permissions, sharing policies, site storage limits, and version history settings all stay exactly where they were. Nobody has to migrate anything.
So the belief that everything carries over is not wrong, exactly. It is right about configuration and wrong about capability.
Several things that look like settings are not settings. They are entitlements attached to the specific plan you hold. When the plan changes, the entitlement changes, and the setting that references it stays visible in the admin center while quietly doing nothing.
That gap between “the toggle is still there” and “the feature still works” is where the surprises live.
What Carries Over, and What Does Not
The right column is the work. Four items deserve detail.
OneDrive Storage Ceilings Move on Their Own
For most subscription plans the default OneDrive storage per user is 1 TB, and depending on the plan and number of licensed users you can raise it to 5 TB. If you change a user’s license, the available storage space updates automatically within 24 hours after they next access OneDrive.
Read that second sentence again. The quota follows the license, without anyone touching a setting.
And the consequence when it goes the wrong direction is documented plainly: if you decrease the storage limit and a user is over the new limit, their OneDrive becomes read-only.
Picture how that lands. A long-serving project manager has accumulated 1.4 TB in OneDrive over eight years, mostly site photographs and video. The organization moves to a plan whose ceiling sits below that. Within a day of her next sign-in the quota recalculates, and she can open and share everything she has but cannot save anything new. Nothing was deleted. No warning was configured because nobody knew to configure one. From her side it looks like OneDrive is broken, and the ticket that reaches the service desk describes a sync failure rather than a licensing change.
The people most exposed to this are the ones least likely to be consulted about a licensing decision. Anyone holding large media files, long project archives, or years of scanned records is a candidate. That is why the measurement comes before the plan choice rather than after it.
OneDrive for Business Plan 2 historically supported considerably more per user than current suite plans start at. No destination plan matches the old allocation on day one. If you have users sitting on large personal stores, measure that before you pick a plan.
The Frontline Plan Trap
Microsoft 365 F3 and F1 users have 2 GB of OneDrive storage. If you bought OneDrive for Business Plan 1 to give frontline staff usable personal storage and then move those users to a frontline plan because it looks like the closest match, you take them from 1 TB to 2 GB, and anyone above the new ceiling lands in read-only. Office 365 E1 is worth pricing against F3 for that reason. It is not a frontline plan, but it carries a full 1 TB.
Do you know how much OneDrive each of your users actually holds?
That measurement comes before the plan choice, not after. We can tell you exactly who’s at risk of landing in read-only before you commit to a destination plan.
The Tenant Storage Pool Recalculates
Total SharePoint storage per organization is 1 TB plus 10 GB per license purchased for most plans, while Microsoft 365 F1 or F3 and Office 365 F3 tenants get a flat 1 TB. OneDrive standalone plans contribute 0.50 GB per license to tenant limits.
So your pool is a function of your license mix, and changing the mix changes the pool. Swap a set of standalone licenses for frontline SKUs and the total can come down rather than up.
What makes this worse is that the pool is usually fuller than the file count suggests, because active documents are not the only thing consuming it.
Version history is the largest hidden consumer. Every retained version of a file occupies storage, so a frequently edited document can hold many times the space of the copy anyone actually opens. Deleted content keeps consuming too. Items sit in the recycle bin for 93 days from the moment of deletion, and that window spans both stages rather than restarting, so a file deleted today is still occupying space well into December. Note one detail people get wrong: the first-stage recycle bin contributes to the storage used figure while the second-stage bin does not, which is why a site’s reported usage can drop without anyone recovering any actual capacity.
Retention policies add a third layer. Where content is under a retention policy or hold, modifying or deleting it writes a preserved copy into a hidden library that also consumes storage, and that copy stays until the retention period expires regardless of what users do.
The practical implication for a plan decision: measure what your pool actually contains before you assume a smaller allocation will fit, and trim versions and empty bins before concluding you need to buy capacity. Both are free, and both are usually worth more than people expect.
IRM and Compliance Are Entitlements, Not Configuration
IRM relies on the Azure Rights Management service from Azure Information Protection to encrypt and assign usage restrictions, and some Microsoft 365 plans include Azure Rights Management while others do not.
A library with IRM enabled keeps its IRM settings through a license change. Whether IRM still protects anything depends entirely on whether the destination plan carries Azure Rights Management. Business Basic and Business Standard do not. Business Premium does.
The same logic applies to the Plan 2 compliance capabilities. In-place holds and advanced eDiscovery become Microsoft Purview entitlements gated by the destination plan. Even a careful, like-for-like move requires recreating holds and policies in Purview. They do not travel as settings.
Where the Unexpected Costs Come From
Not from the sticker. From the recount.
Standalone plans were bought per user for a narrow purpose. Suites are bought per user for everything. Anyone who only needed SharePoint now needs a full base license, and there is no license-free storage-only route.
Then the storage math resurfaces. If your pool shrinks or your users were sitting above the new ceilings, you need capacity on top of the suite. Microsoft’s options here include capacity packs and consumption-based storage meters, and the consumption meters were still in preview at the time of writing with a general availability target that has moved more than once. Anything you budget against them should be treated as provisional.
The cheaper lever is usually the unglamorous one. Reduce and archive before buying more active capacity. Most tenants carrying years of standalone-plan content have more recoverable space than they expect.
What to Do Before Your Renewal Date
Find your renewal date first. That, not December 2029, is your deadline.
Then measure three things. How much OneDrive each user actually holds, so you know who is at risk of read-only. What your tenant storage pool is today and what it becomes under the license mix you are considering. Which compliance capabilities you currently rely on, specifically holds, IRM, and any data loss prevention rules, so you know what has to be rebuilt rather than assumed.
Choose the destination plan against those three answers rather than against the closest price match. The plan that looks equivalent on a comparison page is frequently not equivalent on entitlements.
Do it with runway. Delayed planning is the failure we see most often, and it is the one that removes your options. A renewal that arrives with no destination chosen turns a considered review into a rushed swap.
WME runs standalone-plan transition reviews covering entitlement mapping, storage forecasting, compliance continuity, and a migration plan timed to your renewal.
A renewal that arrives with no destination chosen turns a considered review into a rushed swap.
WME runs standalone-plan transition reviews covering entitlement mapping, storage forecasting, and compliance continuity, timed to your renewal.
