A 40-person team went from twelve subscriptions to a single Copera workspace in one quarter. This is a composite story — drawn from the migrations we see most often — of what actually changed, what was hard, and what the team wishes they’d done sooner.
We’ll call them Acme: forty people, split across product, operations, and a growing customer team, with the kind of tool stack that accumulates when a company grows fast and says yes to every reasonable request. No single decision was wrong. The sum of them had become the problem. Here’s how they consolidated, told honestly — including the parts that didn’t go smoothly.
The stack they started with
Acme’s audit turned up twelve tools doing the daily work: a chat app, a project tracker, a docs-and-wiki tool, a whiteboard app, a form builder, a scheduling tool, a lightweight CRM, a transcription service, a file-sharing tool, an internal announcements app, a poll tool, and a task app that half the team used and half ignored. Two of them overlapped almost entirely. Three were paid for and barely touched.
The monthly bill was real but not the headline. The headline was that a single customer escalation might touch five of those tools, and no one could see the whole thread. Context lived in the seams.
We didn’t have a tools problem. We had a “where does this live?” problem, twelve times a day.
The trigger
The forcing function was mundane: a renewal. Three annual contracts came up in the same quarter, and finance asked a simple question — “before we renew, can anyone explain what each of these does that the others don’t?” Nobody could, cleanly. That question turned into an audit, and the audit turned into a decision to consolidate rather than re-up.
How they migrated
The part that made it work was sequencing. Acme resisted the urge to move everything at once and instead migrated in three waves over the quarter:
- Wave one — communication. Chat and announcements moved first, because that’s where the team already spent its day. Getting everyone into one place to talk created the gravity for everything else.
- Wave two — work. Projects, tasks, and intake forms came next, rebuilt as boards and automations rather than lifted over one-for-one. This is where they deleted process, not just migrated it.
- Wave three — knowledge. Docs, the wiki, and reference logs moved last, once the team trusted the workspace enough to make it the place they’d look first.
Each wave ran in parallel with the old tool for about a week — long enough to build trust, short enough to avoid living in two systems indefinitely. The rule was: when the new home was clearly better, the old one got turned off, not left “just in case.”
What was actually hard
Two things. First, the whiteboard workflow didn’t map cleanly at first; the design team missed a specific freeform feel and needed a couple of weeks to find a new rhythm. Consolidation isn’t free — you trade some specialized depth for coherence, and it’s worth naming that honestly. Second, a handful of people had muscle memory in the old tools and quietly kept using them. The fix wasn’t a policy; it was turning off the old logins on a set date so the path of least resistance pointed the right way.
What changed
By the end of the quarter the results were concrete:
- Twelve tools became one. Nine were cancelled outright; two specialized tools were kept for genuine edge cases; one was folded in entirely.
- Onboarding got dramatically shorter. A new operations hire was productive in days, because “learn the workspace” replaced “learn twelve tools.”
- Cross-team work got visible. That five-tool customer escalation became a single thread anyone could follow, which quietly improved response time more than any process change had.
- The bill went down and got predictable. Unlimited members meant they could finally add clients and contractors to the actual work instead of forwarding them summaries.
What they’d do differently
“Sooner,” was the honest answer. The team’s main regret was spending a year adding tools to patch problems that a unified workspace would have prevented, and treating the sprawl as normal until a renewal forced the question. Their advice to teams sitting where they were: you don’t need a crisis to run the audit. Ask the finance question — “what does each of these do that the others don’t?” — and see how cleanly you can answer. If you can’t, you already have your project for the quarter.
