wiki/knowledge/project-management/clickup-migration-failure-2026-02-02.md · 697 words · 2026-04-05
ClickUp Migration Failure — 2026-02-02
Overview
On the morning of 2026-02-02, a ClickUp migration failure was discovered that hid the majority of tasks across all client folders. The issue surfaced during the team standup and was treated as an emergency blocker. Melissa escalated immediately to the ClickUp consultants and issued a team-wide directive to halt new task creation pending resolution.
This incident disrupted sprint planning and forced team members to rely on personal notes, email trails, and paper records to track their work.
Status at time of meeting: Unresolved — consultants contacted, awaiting emergency response.
What Happened
A recent ClickUp workspace migration left most tasks invisible across client folders and personal inboxes. Key symptoms observed:
- Client folders severely depopulated — e.g., the Cordwainer folder showed only 2 tasks instead of the expected dozens.
- Migration validation folder hidden — the dedicated migration folder that had been used to verify task presence was no longer visible.
- Personal inboxes nearly empty — Melissa's inbox showed only 8 items; Karly's showed approximately 10. Both knew their actual workloads were far larger.
- Sprint folders out of date — scrum folders were not reflecting current sprint state.
- Individual task links broken — at least one task (Adavacare's Feb 26 Wisconsin Guide landing page) returned a "task not found / task not acceptable" error when accessed directly.
The migration folder had previously served as a reliable fallback for confirming task existence. Its removal as part of the migration cleanup eliminated that safety net.
"I cannot only have eight things in my inbox." — Melissa Cusumano
Impact
| Area |
Impact |
| Sprint planning |
Blocked — team could not confirm what was due |
| Client deliverables |
At risk — missing tasks for Cordwainer, Adavacare, and others |
| Design team |
Needed AM intervention to identify active projects |
| Individual task tracking |
Broken for all team members |
- Do not create new tasks in ClickUp until the issue is resolved. Risk: newly created tasks may not persist or may compound the data integrity problem.
- Notify your AM of any specific tasks you know are missing so they can be tracked manually.
- Monitor the
#ops-hub Slack channel for updates from Melissa as the consultant response comes in.
Workarounds in Use
- Gilbert — maintaining a personal notepad with all open items.
- Sebastian — reconstructing the Cordwainer task list from a paper trail / email history.
- Raphael — searching email to recover missing task references.
- Avoke — asked to hold off on adding new tasks; working from known agenda items.
- Karly — working from tasks she could recall; bookmarked a Google Drive folder directly via invite link after it stopped appearing in her shared drives list.
Actions Taken
- Melissa sent an initial email to ClickUp consultants before the standup, then sent a follow-up during the meeting requesting an emergency call.
- Melissa will post all updates to the
#ops-hub Slack channel.
- Mark recommended escalating to an emergency call rather than waiting for the scheduled consultant sessions (originally planned for the 5th).
Root Cause (Hypothesized)
The migration process appears to have moved tasks into a new folder structure but left them inaccessible — possibly hidden under the migration folder that was subsequently removed from view. The tasks are believed to still exist "in the ether" rather than being permanently deleted, but this was unconfirmed at the time of the meeting.
Related Incidents & Context
- A separate pre-existing issue: Karly could not see a specific Google Drive folder in her shared drives list despite being re-added as a manager. Workaround: log out of Google account fully and log back in. Unresolved at time of meeting.
- The Adavacare Feb 26 Wisconsin Guide task had already been experiencing notification delivery issues prior to the migration failure — the designer (Andre) had stopped receiving updates on it. The migration failure then caused the task itself to disappear entirely.
Related Articles