Skip to content
Notifications
Clear all

ClickUp or Monday.com for a 200-user retail ops team - our migration story

3 Posts
3 Users
0 Reactions
0 Views
(@devops_barbarian)
Reputable Member
Joined: 4 months ago
Posts: 250
Topic starter   [#24812]

We were on ClickUp. Everyone said to move to Monday for "better workflows." So we migrated. It was a disaster that cost us six months of productivity.

The sales pitch ignored the actual work. ClickUp's hierarchy is rigid but that's a feature. It maps to retail ops: Portfolio > Project > List > Task. Monday's "boards and groups" model forced a complete reconception of every process. The migration script they provided failed on custom fields. We had to write our own scraper for the ClickUp API and a loader for Monday's, handling rate limits and field mapping manually.

```python
# Example of the field mapping hell we had to script
clickup_custom_fields = {
'store_number': 'number',
'priority_rating': 'dropdown',
'asset_tag': 'text'
}
monday_mapping = {
'number': 'numbers',
'dropdown': 'color',
'text': 'text'
}
# Then transform every single task's custom field value type
```

The real failure was assuming any tool survives contact with 200 users. We lost historical comments, attachments had broken links, and automations all needed rebuilding from zero. Monday's pricing model bit us when we needed more "boards" for seasonal campaigns.

We're back on ClickUp now. The lesson wasn't about which tool. It was that a forced migration of a live ops system without a parallel run phase is just chaos engineering on your own payroll.


Don't panic, have a rollback plan.


   
Quote
(@davidn)
Estimable Member
Joined: 3 weeks ago
Posts: 148
 

That field mapping example hits home. We evaluated Monday for a warehouse management rollout last year and the custom field translation was a major blocker. Their "color" column type for what should be a simple dropdown added a layer of complexity we didn't anticipate.

Your point about the hierarchy is crucial. Monday's flat board structure demands you build a process model from scratch, while ClickUp's enforced nesting, while sometimes inflexible, provides a ready-made operational skeleton. For a 200-person team, that skeleton is what keeps everyone aligned without constant configuration.

Did you find any lasting damage from the broken historical data, like audit trail gaps, or was it mostly a productivity hit during the transition?


Measure twice, buy once.


   
ReplyQuote
(@benjislack)
Estimable Member
Joined: 3 weeks ago
Posts: 94
 

Audit trails were completely broken. The migration timestamp became the creation date for everything. Any historical analysis of how long tasks sat in "pending vendor" is gone.

That skeleton you mentioned is exactly why people get trapped. It works until you need to do something slightly outside the frame, then you're stuck buying another add-on or building a workaround. ClickUp's nesting is a straitjacket disguised as a scaffold.

The real cost wasn't the six months. It was the institutional knowledge we lost because the new system couldn't reflect how the work actually got done.


your mileage will vary


   
ReplyQuote