ClickUp Migration Strategy — Simplified Structure
Overview
During the [1], the team decided to pause the in-progress ClickUp migration and request a redesigned client folder structure. The original consultant-built blueprint used granular, service-based lists (e.g., separate lists for social, SEO, email, paid, etc.) that the team found overly complex and misaligned with how they actually work.
The proposed replacement is a four-list standard applied uniformly to every client folder.
Proposed Structure
Each client folder should contain exactly four lists:
| List | Purpose |
|---|---|
| Account Management | Strategy tasks, OKRs, client service items, reporting |
| Projects | All active work tasks currently in flight |
| Historical | Completed tasks moved out of the active view to reduce clutter |
| Resources | Links to brand guides, logo folders, credentials, and other reference materials (stored as tasks with embedded links to Google Drive) |
Rationale
- The original service-based list structure was designed for a larger, more siloed team. The current team size and workflow doesn't benefit from that level of fragmentation.
- Team members primarily work from the sprint view, not individual client folders. The folder structure is most useful for account managers needing a bird's-eye view and for anyone looking up resources.
- Collapsing service categories into a single Projects list reduces confusion about where to file cross-functional work (e.g., "Is a page rewrite SEO or content?").
- A dedicated Historical list keeps the active Projects view clean without permanently archiving completed work.
Tagging Strategy
To preserve the service-level granularity that the original list structure was meant to provide, the team will use tags instead of separate lists. This supports time-tracking and reporting by service type without multiplying folder complexity.
Planned tag categories include services such as #social, #SEO, #content, #paid, #email, and #design.
Action required: Clean up the existing tag library. The current tags are inconsistent (e.g., a lone #P that should be #paid or #PPC). Tags should be standardized and the ability to create ad-hoc tags should be governed going forward.
Task Creation Protocol
A key process decision made alongside the migration discussion:
All new tasks must be created inside the client folder (not directly in the sprint view).
When a task is created in the client folder with a future due date, it will automatically pull into the correct sprint when that sprint window opens. This enables long-term planning — for example, building out a full quarter of social content tasks in advance — without manual sprint management.
Creating tasks in the sprint view directly is acceptable for urgent items but should not be the default habit.
Migration Status
As of 2026-02-05, the data migration has been paused pending consultant review of the new structure.
Open questions for the ClickUp consultant:
- Can the folder structure be condensed to four lists before migration runs?
- Does restructuring affect existing automations (e.g., sprint pull-in, task naming conventions)?
- Is the restructuring work within the current contract scope, or does it incur additional cost?
- What is the revised migration start date?
See action items below for ownership.
Action Items
- [ ] Isalia Ramirez — Email ClickUp consultant to pause data migration and propose the four-list structure; ask for revised start date and confirm whether restructuring is in scope
- [ ] Melissa Cusumano — Schedule follow-up meeting with ClickUp consultant for Feb 11–12
- [ ] Team — Standardize and clean up the ClickUp tag library before migration resumes
Related
- [2]
- [3]