Being wary of software from a company you have not heard of is sensible. Most of the risk in adopting a new tool comes from moving too much, too soon. Here is a way to test one, ours included, that risks nothing.
1. Do not move anything
Leave your current tools exactly as they are. A fair trial runs alongside what you already use. If a vendor's trial requires you to migrate first, treat that as a warning.
2. Test the exit before the entrance
Before putting anything real in, find out how to get it out. Create a few test items, then export them. Open the exported file in a program you already own. If you cannot do that in five minutes, you have learned something important.
In Mechanesmos this is under Workspace and data: tasks export as spreadsheet files, pages as plain text, and the whole workspace as one backup file.
3. Bring in a copy of one real project
Not everything. One board or one spreadsheet that people actually use. Importing a copy leaves the original untouched, so there is nothing to undo.
4. Use both for a week
Do the real work in your existing tool, and mirror it in the new one. At the end of the week ask two questions. Did the new tool save any time? Did anyone on the team reach for it without being asked?
5. Read what the vendor says it cannot do
Every product has limits. A vendor that lists them is easier to trust than one that does not. Ours are on the product page and the security page.
6. Decide, and keep the way back open
If it worked, move one team, not the whole company. Keep exporting a backup now and then. A tool you can leave is a tool you can safely adopt.
What this costs you
A few hours over a week, and nothing else. No card, no installation, and no change to the tools you rely on today.