Seeking advice: migrating from ClickUp to Fibery

Get Help
1

I already use Fibery for my Business and know how great it is in several aspects. And I’m helping another business to organize their digital infrastructure. I’m considering and already exploring migrating them to Fibery.

Their current toolset

This company currently uses:

  • ClickUp for project management
  • Discord for communication
  • Notion, Miro, and Mindmeister scattered across different teams
  • They dont have a single source of truth for documentation

Seeking migration experiences and advice

We’re considering consolidating these tools into Fibery, and I’d like to hear from community members who have made similar migrations, especially from ClickUp.

If you’ve made this transition, I’d appreciate your insights on:

  1. Your migration approach - How did you structure the migration? All at once or phased by team/function?
  2. Data migration strategies - What worked well when moving projects, tasks, and documents?
  3. Team adoption challenges - What resistance did you encounter and how did you address it?
  4. Most valuable gains - What improvements have you seen since consolidating in Fibery?
  5. Unexpected challenges - What would you do differently if starting over?
  6. Time investment - How long did your migration take from planning to completion?
  7. ClickUp vs Fibery - Which specific limitations in ClickUp did Fibery solve for your team?
  8. Documentation/Wiki/SOP integration - How did you structure your knowledge base in Fibery compared to previous tools?

I’m particularly interested in practical experiences rather than theoretical comparisons. Any concrete examples, screenshots of your workspace structure, or migration timelines would be extremely helpful.

Thanks in advance for sharing your experiences! :nerd_face:

2

I just found this, very good:

3

Hey Renato

Unfortunately I don’t have solutions but wanted to chime in as I’m facing a similar challenge and wanted to share some observations.

Context

I work on 2 teams that went from Trello → Hive → Notion (only 1 team)

I’m in a similar position where I personally was using Notion and started using Fibery on my own and I’m loving it.

Observations

Views and databases are still foreign to people

I thought by now that the popularity of tools like Notion would have led to wider adoption and understanding of working with database items and views. But this continues to be a hurdle and I think until users understand that style of working they miss out on a lot of the benefits of these apps.

This is unfortunate because I think even if you don’t have your system figured out and don’t know your structure, people can still benefit from the power of search within these tools and the power of links/relationships.

Wholesale switching an entire team is challenging

I would look for teams/members that are most receptive to change or who feel unhappy with the current tools/workflows. Someone like yourself might be farther on spectrum of open/receptive to change and there are probably people that are the exact opposite Don’t change anything, I have my process and it works.

Waiting to switch until you’ve “figured out the system”

This killed me. You need people using the tool and system and you figure it out as you go. What’s working, what’s not working? The team I mentioned earlier kept delaying moving to Hive until everything was “figured out”. By the time the switch was made people still had to figure things out, that process could have started months ago.

Don’t migrate everything

This comes from Tiago Forte and his concept of second brain. He thinks it’s a mistake to try and migrate everything from previous tools, it can make a mess of the new space. I was skeptical of this advice at first but after migrating from a few different tools I’ve found that it’s easier to start fresh and if necessary just refer back to the old tools.

So what should you migrate? I’d migrate current projects (if they’re still in earlier stages). I’d also migrate current/useful documentation (think 80/20, what documentation is getting used/referred to the most)

Documentation

Create a documents database and don’t use the “Documents” field type from Fibery (elsewhere in the community this has been suggested). This will let you add relevant fields to the document database, the Fibery document type doesn’t let you add fields.

You can create a self relation which would let you nest documents to create Wikis.

4 Likes