Workplace by Meta Shutdown

This post is for organizations that have already moved off Workplace and are wondering whether they made the right call, and for the ones still deciding what comes next. We'll cover what Workplace actually was, why it failed, what Meta pushed as a replacement and why that recommendation deserves scrutiny, and what to look for instead.

What Workplace by Meta actually was

Workplace launched in 2016 as an enterprise version of Facebook: news feeds, groups, video calling, and chat, but behind a company login instead of a public profile. At its peak it had around 7 million paid subscribers. The pitch was simple: employees already knew how Facebook worked, so adoption would be frictionless.

In practice it worked better as a social engagement layer than as a structured information platform. It was good at broadcasting, reasonable at community discussion, and weak at anything requiring document management, permissions-controlled content, or structured navigation. Organizations that needed a communication tool got value from it. Organizations that needed an intranet often found it fell short.

Meta killed it because it couldn't compete with Microsoft Teams, Slack, and Google Workspace, and because Meta had decided to focus resources elsewhere. The decision wasn't a reflection of the enterprise communication market contracting. It was a reflection of Workplace specifically failing to differentiate.

The timeline, precisely

The shutdown happened in stages. Workplace continued operating normally until August 31, 2025. From September 1, 2025 onward, posting new content was disabled and accounts moved to read-only mode. That window exists for data export only. On June 1, 2026, all access ends and all data is permanently deleted.

If you still have data in Workplace and haven't exported it, do that before anything else.

What Meta Recommended and Why you should evaluate it independently

Meta designated Workvivo by Zoom as its "only preferred migration partner." That designation is a commercial partnership, not an independent assessment that Workvivo is the right fit for your organization. Workvivo requires a minimum of 250 employees and uses pricing that starts at $20,000 per year, which makes it unsuitable for smaller teams and expensive for mid-market organizations that were using Workplace on a straightforward per-user subscription.

Workvivo is a legitimate product with a strong focus on social engagement and employee recognition. If that's specifically what your organization needs, it may be the right choice. But if you're evaluating alternatives to Workplace, the preferred migration partner designation shouldn't be the reason you pick it.

What replaced what: a feature-by-feature map

The most common question from organizations migrating off Workplace is what specifically replaces each feature. The honest answer depends on whether you're replacing Workplace with another social engagement tool or with a structured intranet. Both paths are legitimate. The right one depends on what you were actually using Workplace for.

The WorkChat row is worth noting plainly: if real-time messaging was how your organization actually communicated day to day, a structured intranet platform is not the right primary replacement. You need Slack or Teams for that, and the intranet sits alongside it as the source of record for structured content rather than replacing the chat layer.

What it actually costs: a pricing comparison

Workplace was $4 per user per month, which made it accessible for organizations of almost any size. The pricing jump to most alternatives is significant and not always disclosed upfront.

The vendor lock-in row is worth sitting with for a moment. Organizations that used Workplace are currently experiencing exactly what vendor lock-in looks like: a platform you built workflows around, that housed your institutional knowledge, that employees used daily, shut down with roughly two years of notice and your data deleted permanently on a date Meta set. Open source platforms eliminate that risk entirely. If PortlandLabs disappeared tomorrow, every Concrete CMS installation would continue running on the code its customers already own.

Before evaluating any platform, it's worth being honest about what you actually used Workplace for. The common use cases were company-wide news and announcements, group-based team communication, video posts from leadership, and basic community engagement. If that's what you need, the replacement options look different than if you need a structured intranet with document management, role-based content visibility, and compliance workflow.

Most organizations that migrated from Workplace fell into one of two camps:

They needed a communication and engagement tool. If the primary use case was broadcasting company news, leadership video updates, and social recognition. Workvivo, Viva Engage (Microsoft's Yammer successor), or Staffbase are reasonable choices depending on budget and Microsoft ecosystem alignment.

They needed a real intranet. If the Workplace migration exposed the fact that the organization was using a social tool to do the job of an intranet: storing policies, onboarding new employees, managing HR documentation, giving different departments access to different resources, then the replacement should be an actual intranet, not another social engagement layer. Replacing Workplace with a more capable social tool just defers the problem.

This is the distinction worth getting right before choosing a platform. We've written about what an intranet actually is and how it works if the difference isn't clear, and about why SharePoint isn't the default answer either.

The checklist before you commit to a replacement

Whether you're still deciding or evaluating whether your current migration was the right call, these are the questions worth asking:

Who owns the content? With Workplace, Meta owned the platform and you owned the data. With any SaaS replacement, understand what happens to your content if you stop paying, if the vendor is acquired, or if they shut down again. Open source platforms give you complete ownership of the codebase and data regardless of what happens to the hosting relationship.

What does it cost as the organization grows? Per-user pricing models that seem reasonable at 200 employees become expensive at 500. Fixed hosting pricing rewards growth rather than penalizing it.

Can it handle real permissions? Workplace's permissions were relatively flat. You were in a group or you weren't, and that was the extent of it. A proper intranet permissions model controls content visibility by role, department, location, and employment type without manual gatekeeping on every update.

Will content go stale? Workplace content lived in a feed, which means old posts naturally faded out of view. A structured intranet means content stays visible until someone actively updates or removes it. That requires governance. See our guide to auditing your intranet for stale content for how to build that process.

Can you integrate it with what you already use? SSO with your existing identity provider, integration with Microsoft 365 or Google Workspace, and connection to HR systems are baseline requirements. Concrete CMS supports Microsoft Entra ID SSO for organizations in the Microsoft ecosystem.

Why Concrete CMS is worth considering

Concrete CMS is an open source web content management system that organizations use to build intranets, HR portals, and internal communications platforms. It's not a social engagement tool in the Workplace mold. It's a structured content platform designed for teams that need to manage a large volume of content across a complex organization.

What that means in practice: permissions and workflow ship in core, not as add-ons. Content owners can be assigned at the page level. Publishing goes through an approval process before reaching employees. SSO integrates with Microsoft Entra ID. The editing experience is designed for non-technical contributors, which means department heads and HR managers can maintain their own sections without IT involvement.

It's been used for internal communications at BASF across multiple business units serving over 100,000 employees, at Marvell Semiconductors for HR and employee development, and at the U.S. Army MWR across hundreds of installations. It's not a startup bet. It's been maintained and actively developed since 2003.

It also doesn't charge per-user fees. As your organization grows, the hosting cost doesn't scale against you the way a per-seat SaaS model does.

If Workplace left you with a social engagement gap rather than an intranet gap, Concrete is probably not the right fit. Go evaluate Workvivo or Viva Engage. If Workplace left you realizing you never had a proper intranet in the first place, Concrete's intranet solution is worth a serious look.