OpenText is reintroducing itself under new leadership, new structure, and a louder AI narrative. But for marketing and content leaders, the core question isn’t whether the re-org signals a bold new future.

The real question is simple: When is the right time to move on?

From where we sit, OpenText’s content and marketing technologies aren’t just “mature” — they’re serious legacy. You would never implement their WCM, DAM, or experience technologies afresh in 2025. OpenText is a platform you inherit, not one you choose. And despite the leadership changes, that fundamental calculus hasn’t shifted.

The “New” Leadership Is Still the Old Guard

OpenText removed its long-time CEO/CTO and reshuffled the org, but the new leadership layer is made almost entirely of long-standing insiders. They know the products well, but they also shaped the strategy that led to today’s sprawling, overlapping, aging portfolio.

This isn’t an outsider turnaround, It’s the same team trying to steer the same ship in slightly different water.

That’s not a knock on the leaders themselves, it’s just important context. Continuity means stability. It also means you shouldn’t expect radical acceleration or bold simplification.

AI Won’t Unify the Portfolio — Because AI Features Can’t Unify Any Legacy Portfolio

OpenText is far from alone here. Every roll-up vendor -  not just OpenText, but Sitecore, Acoustic, Optimizely, and others - is now promising that AI will magically unify their inherited and aging technologies.

But AI can’t fix a fragmented product set.AI features can’t modernize aging codebases or align multiple generations of acquired platforms

At best, AI brings tactical efficiency to discrete tasks - summarizing, classifying, routing, recommending. Useful, yes. But nowhere near the “connect everything into one intelligent platform” narrative that every vendor is pushing. And the orchestration they promise is usually confined to their own ecosystem - more a walled garden than true, cross-stack MarTech orchestration.

So when OpenText positions AI as the glue that will finally integrate Micro Focus + ECM + CCM + DevOps + B2B + MarTech? Take that with caution. It’s the same narrative every roll-up tells when the portfolio gets unwieldy.

Where OpenText Is Actually Investing (And Why It’s Not MarTech)

One area where OpenText has been putting real attention — and seeing traction — is the contact center and broader CX operations. If you squint, you can see why:

• Less dependence on legacy web and marketing tech
• More alignment with automation, analytics, and AI use cases
• Clearer enterprise sales motions

That’s fine — and probably smart for them.  But it underscores an important point:

OpenText’s future investments are drifting farther away from the marketing and content-tech categories most of our clients care about.

So What Should MarTech Leaders Actually Do?

For most organizations still running OpenText in their content or experience layers:

Don’t expect a modern marketing platform to emerge from this re-org.

The leadership shuffle doesn’t fundamentally change the trajectory of OpenText’s legacy marketing stack.

Start planning a path off the platforms you wouldn’t re-buy today.

“Would we acquire this tool now?” is the single best test for legacy risk.

Treat the AI narrative with healthy skepticism.

It will bring productivity gains, sure, but it won’t magically solve the underlying portfolio fragmentation.

Bottom Line

OpenText’s re-org is notable, and their AI story is louder. But from a MarTech perspective, the fundamentals haven’t changed:

• Their content and experience technologies remain deeply legacy
• AI features won’t change that
• The leadership change doesn’t materially alter the strategic outlook
• And across all our enterprise research, almost no clients are actively choosing OpenText anymore

This isn’t about whether OpenText is “good” or “bad.” It’s about whether its platforms still align with a modern marketing and content strategy. For most organizations, the answer is increasingly: No, and it’s time to plan accordingly.