I’m thinking of migrating my team of 3 into fibery from clickup. Tired of the pricing scheme, bugs, and lag – and feeling like clickup dev team doesn’t care.
Main features we love with ClickUp
- integrated chat, allows you to easily reference things from the workspace
- mobile app to get chat notifications on the go
With my team, I do all the project managing and use tasks and different views, while the other 2 mainly just use chat, and open docs and tasks I link there.
I see there isn’t either of those features listed in fibery. Is it known if that is planned? How do people currently work around that?
1 Like
In Fibery, you can set it so that an entity has a comments field. Comments works quite similarly to the chat feature within a task in Clickup. Also, in a rich text field, you can use inline comments. These will send notifications as long as the person is set as a watcher to that entity and has their notification setting set proper. There is also an experimental “thread” feature which shows the comment field of an entity in its own view. I like to use this to have a “general” channel according to the space.
Ya, there’s currently no app, but they’ve said they are developing one this year.
We moved from clickup to fibery about 18months ago and so glad we did!
2 Likes
I’m curious about the migration process 
What is the industry you are at? What about the Team size? How was the process of convincing the decision makers? Migration and educating the team about Fibery?
We just did migration by hand as we wanted to rebuild our processes using the features of fibery that could make them so much better. We run events so having a system flexible enough to handle everything from operations to marketing as our centrepoint is so useful. Team size 10. Im the founder so decided myself. Learning curve for building things in fibery is steep but worth it and the support team have been incredible at guiding us. For team members that just need to sign in and follow a process its pretty easy to make it self explanatory with the features on offer.
3 Likes
I find the importer is great for ClickUp lists that were like databases and used to store static information.
When moving tasks into Fibery, the layout isn’t as attune to tasks as a use case (IMO) so I didn’t want as many fields as I had in clickup. Regardless of my preferences @Lee_Denny definitely has the best approach I’ve seen. Moving tools is a good time to evaluate information, processes, and how they best work together. Since Fibery is better at tracking distinct databases of different data types, a refactor is necessary.
1 Like