ClickUp Migration — November 2025 Rollout
A major restructuring of Asymmetric's ClickUp environment is scheduled for the Thanksgiving weekend (November 2025). The migration moves from a sprint-centric task organization to a permanent client-folder-based structure with automated task flow. Isalia Ramirez is coordinating with external consultants; Melissa Cusumano is co-leading the rollout.
Timeline
| Phase | Dates | Description |
|---|---|---|
| Environment Build | Nov 13–22 | Consultants build out the new ClickUp structure |
| Data Migration | Nov 23–29 | Tasks migrated to new structure over Thanksgiving weekend |
| Team Training | Week of Nov 30 | Full team onboarded to new system |
Note for anyone working Thanksgiving weekend: Tasks may be actively moving between locations during Nov 23–29. Check Slack (Ops Hub) for status updates.
New Structure: Client Folders
The core change is replacing the current sprint-based organization with permanent client folders.
- Each client gets a dedicated folder that persists across all sprints
- When a new sprint opens, tasks assigned to that sprint are automatically pulled in from the client folder — no manual migration needed
- When a task is completed, it moves back to the client folder, creating a single searchable project history per client
- Eliminates the need to dig through past sprints to find historical work
This automation was a key driver of the decision to migrate — the current manual sprint-to-sprint task movement is a recurring operational burden.
What the Team Needs to Do Before Migration
Clean up ClickUp tasks before Nov 23 to ensure a smooth data migration:
- [ ] Resolve all open internal task conversations
- [ ] Update all due dates (many are stale/red)
- [ ] Add time estimates to all tasks — even a rough figure (e.g., 2 hours) is sufficient
- [ ] Follow up on tasks in Client Review and Hold Blocked statuses
- [ ] Ensure tasks are in the correct status before migration begins
Isalia summarized it plainly in the meeting: "That's essentially all you have to do until the training."
Why Time Estimates Matter
Accurate time estimates are critical for workload management. Without them, Melissa cannot gauge team capacity to assign new projects. As of the Nov 13 sprint planning, Anoop's workload appeared artificially low — likely due to missing estimates rather than actual availability.
Even rough estimates provide a useful average: a task logged at 2 hours might take 30 minutes sometimes and 4 hours other times, but the average is actionable for planning purposes.
See also: [1] (if created)
OKRs and Client Health Checks — Scope Change
The original plan to build OKR tracking and client health check functionality within ClickUp has been dropped. Mark is building a separate proprietary tool to house OKRs, client health checks, and related strategic information in a single centralized location.
The ClickUp migration scope is therefore limited to task and project management. The OKR tool will be a standalone system.
See also: [2] (if created)
Key People
| Person | Role in Migration |
|---|---|
| Isalia Ramirez | Coordinating with consultants; sent Slack announcement in Ops Hub |
| Melissa Cusumano | Co-leading rollout; primary point of contact for team questions |
| Mark Hope | Decided to build separate OKR tool; removed that scope from ClickUp build |
Related
- [3] (source meeting)
- [4] (if created)