There are several issues we ran into on the migration and our initial use. We have eventually been able to develop work-arounds for most of the.
1. From an American PM perspective, lots of the Avaza terminology and organization is not intuitive, making it a big search to find the functions we are trying to use.
2. It appears to have been built for small projects, and we had to import over 10K tasks with lots of details - and that was just the currently active projects. there are many cases wher the controls are at the top or bottom of a page, and when you end up with multiple pages, you are constantly scrolling up and down to get to those controls. Even simple things like making a word bold in a note is painful.
3. System Admins do not have the ability to delete things easily. You have to delete every individual task to delete a section and all sections to delete a project, but if any time or expenses are marked as processed, you can't delete them at all. Even archiving something does not allow you to delete it.
4. The support team notes and passes on verified issues and "improvement requests" to the dev team, but there is nothing to give you any feedback on the status of those requests.
5. The documentation is very thorough on what the tool does, but it is written from a marketing perspective. It is very positive and glowing. What is NOT there are all the things you can't do. You have to discover them for yourself, then contact support who says - yes, you can't do that. A good example is the billing and expenses function. We have suppliers who issue us bills that we want to track due dates and payment status using the bill function. But bills are lumped together on the financial reports and don't count to COGS, which is not correct. Bills need to be tracked and bills can be non-billable or billable - so you have to be able to have a bill also be an expense against a project. The documentation is totally silent on this significant limitation.
I'd recommend that Avaza form an advisory group of experienced customers and listen to them on how the customers need to use the system. The organization and functionality of many areas makes no sense to me after 45 years of runnign projects around the world with many different tool sets. Review collected by and hosted on G2.com.