MicroStrategy end of support, for an on-premises customer, means one date: Strategy's on-premises Strategy Enterprise Platform (MEP) loses mainstream support on 31 December 2026. Extended Lifecycle Support, at added cost, then runs to 31 December 2028, covering critical security patches and limited technical help. After that, Strategy provides no support of any kind.
This post sets out Strategy's own dates, what changes for the tools your team uses, and the ways off the platform. MicroStrategy is now called Strategy; its release notes record that "Strategy One is renamed to Strategy" in July 2026. We use both names, because most teams still say MicroStrategy.
- Mainstream support for Strategy's on-premises platform (MEP), the product most teams still call MicroStrategy, ends on 31 December 2026.
- Extended Lifecycle Support runs from 1 January 2027 to 31 December 2028 at added cost, with critical security patches and limited technical help only.
- Developer, Object Manager, Command Manager and other legacy tools are not included in releases after December 2026. Workstation replaces them.
- Whether you move to Strategy's cloud or to another BI tool, the work is in the semantic layer: schema objects, metrics, filters, prompts, VLDB settings and security filters.
What does MicroStrategy end of support actually mean?
It means a change in support level for the on-premises platform, set out in Strategy's Legacy Tools and Platform: End of Support Reference (updated June 2026). The release notes put it in one line: "The on-premises Strategy Enterprise Platform (MEP) will no longer have mainstream support starting December 31, 2026."
| Period | Support level, in Strategy's words |
|---|---|
| Through 31 December 2026 | Mainstream Support: full technical support, feature updates, security patches and bug fixes at your contracted tier |
| 1 January 2027 to 31 December 2028 | Extended Lifecycle Support, at added cost: critical security patches and limited technical help only, no new features or updates |
| After 31 December 2028 | No support: no updates, patches or technical assistance of any kind |
Checked 27 October 2026 against Strategy's End of Support Reference and its What's New release notes, both linked above.
The dates attach to the on-premises platform as a whole, not to a release, so a fully patched installation is on the same clock as an old one. The reference describes support levels, not a shutdown. What happens to your right to run the software after 2028 is a question for your license agreement, so ask your Customer Success Manager in writing.
Is MicroStrategy on premise end of life different from end of support?
Strategy titles its timeline "On-Premises Platform (MEP) End of Life", but the first date in it, 31 December 2026, is the end of mainstream support. The true end is 31 December 2028, when paid Extended Lifecycle Support stops too.
So if someone says MicroStrategy goes end of life at the end of 2026, they're half right. Your security team will want to know which of the two you're on; we cover what each means for audits in the risks of running end-of-life software.
Which MicroStrategy tools stop after December 2026?
Strategy is also retiring its older administration tools in phases as Workstation takes over. Workstation runs on the desktop and, since the June 2026 release, in the browser.
| Phase | Tools | Timing |
|---|---|---|
| Phase 1 | Narrowcast Server, Service Manager, Project Source Manager, XQuery Editor and Generator, Cube Advisor, Test Listener, Connectivity Wizard, User Merge Wizard | June 2026 |
| Phase 2 | Developer, Command Manager, Object Manager, License Manager, DB Query Tool, Import Package Tool, Project Merge Wizard, Repository Translation Wizard, Configuration Wizard, Diagnostics Configuration | In releases through December 2026, not after |
| Phase 3 | System Manager, Integrity Manager, Workstation Desktop | Timeline due by Q1 2027 |
Phase 2 is the one that touches migration plans. Developer is where many teams edit schema objects, Object Manager is how they move objects between environments, and Command Manager scripts often run unattended. Strategy says customers "should complete their transition to Workstation before upgrading beyond December 2026." Any script or runbook that calls these tools is part of the migration, whichever route you take.
MicroStrategy on premise vs cloud: what changes
Strategy's answer for on-premises customers is its cloud. The reference tells MEP customers to "Contact your CSM to begin MCE migration planning." MCE is Strategy Managed Cloud Enterprise.
| On-premises (MEP) | Strategy Managed Cloud Enterprise | |
|---|---|---|
| Who runs the platform | Your team, on your servers | Strategy |
| Support after 2026 | Paid Extended Lifecycle Support to 31 December 2028, then none | The route Strategy recommends |
| Legacy tools | Available through the December 2026 release | The June 2026 notes list legacy tools "no longer available in MCE environments" |
Moving within Strategy keeps the semantic layer in the same product. It still isn't a copy: connections have to reach your data from the cloud, and customizations have to survive current releases. The July 2026 release moved to Spring Framework 7, and Strategy published guidance on the impact for Web and Library customizations.
Why the semantic layer is the hard part
Dashboards are what users see, so they're what people count. But a MicroStrategy dashboard sits on the project's metadata, which Strategy's documentation calls the Universal Semantic Layer. That's where your business definitions live:
- Schema objects. Attributes, facts, hierarchies and the tables they map to. They decide how the SQL joins.
- Metrics. Revenue, margin, active accounts, often with conditions or levels that change the number.
- Filters and prompts. Reusable conditions, and the questions users answer when a report runs.
- Custom SQL. Freeform SQL reports and hand-written expressions that bypass the model.
- VLDB properties. Settings that change the generated SQL for a particular database, often set years ago to fix one report.
- Security filters. Row-level rules that decide who sees which data.
Move to another BI tool and every one of those has to be expressed again in the new tool's model, then reconciled against the old reports, number by number. A forgotten VLDB setting can be why two tools disagree on a total. A security filter rebuilt slightly wrong is a data exposure, not a cosmetic bug.
It's the same pattern as other reporting estates on our list of legacy system examples: the definitions live in configuration one or two people understand. If that's you, capture what they know before the move starts.
Your options: Strategy's cloud, another BI tool, or rebuild reporting elsewhere
| Option | What changes | When it fits | Main risk |
|---|---|---|---|
| Move to Strategy Managed Cloud Enterprise | Same product and metadata, run by Strategy | The semantic layer works and the business wants to keep it | Customizations, connectivity and scripts tied to retired tools |
| Buy Extended Lifecycle Support | Nothing yet; it buys time to 31 December 2028 | A move is chosen but can't finish by the end of 2026 | Paying for critical patches only while the deadline gets closer |
| Move to another BI tool | New semantic model, new dashboards | The business wants one BI tool it already owns | Metrics and security filters rebuilt slightly differently, so numbers stop matching |
| Rebuild reporting elsewhere | Definitions move into the warehouse or a separate modeling layer, with a thinner BI tool on top | You want the definitions to outlive any one BI vendor | The largest scope: every definition rewritten and retested |
Check the database underneath too. If your warehouse runs on Oracle Database 19c, its support runs well past 2028, as we explain in Oracle 19c end of life, so the BI layer is usually the nearer deadline. And whichever route you choose, read what's there before you rewrite.
Where the 30-day assessment fits
Before you pick a route, know what's in the projects. The 30-day assessment is fixed in scope, at a price agreed before we start. Over 30 days we read the project metadata and the code around it: schema objects, metrics, filters, prompts, Freeform SQL, VLDB settings and security filters, plus the scripts and customizations that call the platform. We map which reports depend on which definitions and databases, find the hidden architectural debt, such as one metric defined three ways, and flag the security and compliance gaps, starting with the security filters.
The report says in plain language what is broken, what it would take to fix it, and what each route would mean. Your own team can act on it, or we can do the move as a separate project with its own scope and price. Either way, the report stands on its own. If a narrower check would answer your question, such as a list of scripts that call Phase 2 tools, we'll say so.
Book a scoping call to talk through your MicroStrategy projects.