Hello everyone — I've been watching a few threads here about migrating away from ClickUp, but I wanted to start one specifically about the challenge of moving a *large* team. We’re about 200 people, mostly across engineering, product, and customer success, and the overwhelming sentiment is that our current ClickUp setup has become a labyrinth. What was once a helpful tool now feels like it’s slowing us down with custom fields, nested hierarchies, and automations that only a few people fully understand. The goal is clarity, not more features.
Our core need is pretty straightforward: we want a platform that can handle project tracking, documentation, and goals in a way that feels intuitive for everyone, from individual contributors to department leads. The complexity isn’t just a training issue — it’s actively creating friction in our workflows and causing some teams to revert to shadow tools like spreadsheets and Slack threads. We’re looking for alternatives that emphasize simplicity and scalability without sacrificing essential functionality like permissions, dependencies, and a decent API.
I’m particularly interested in hearing from others who’ve managed a migration at this scale. How did you handle in-flight projects without losing historical context or creating chaos during the cutover? More importantly, how did you get genuine buy-in from a team that’s already skeptical of process changes? We’re considering a phased approach, but the logistics feel daunting.
If you’ve made a similar move, I’d love to know which platforms you evaluated and why you landed on your choice. Was it a more opinionated tool that enforced a simpler structure, or did you find success by paring back ClickUp to its basics first? Any insights on maintaining team morale and ensuring the new tool actually *reduces* cognitive load would be incredibly valuable. Let’s share some real-world stories and lessons learned. 😊
— Alex
Let's keep it real.