This is where AvePoint shines. They are forward-leaning in their development. We had a conversation with one of their developers about an idea, and a few months later, it was implemented. Their innovation and responsiveness to client needs make them a leader in the market. I don't see any room for improvement compared to other vendors. We're truly satisfied with them.

The great thing is when we communicate these needs to AvePoint, they swiftly incorporate them in upcoming releases. 

However, in future releases, it would be beneficial to have a more optimal Google Backup for larger environments.

The product's sales process needs improvement. It takes a lot of work to acquire it. AvePoint doesn't sell products directly to the customers. They take the help of IT system distributors. It is challenging for small or medium-sized businesses to purchase it. This particular area needs improvement compared to other companies.

The component in the product that can be improved revolves around the area where the tool should focus on providing more of a custom touch to the policies. As far as I checked, you can use the backup data option four times per day at customized time intervals, and it would be great if the limit could be increased. Customers would love to have a bit more regular backup to deal with use cases involving an exchange of data.

As of now, AvePoint doesn't provide instructions about the licensing details or how the backups work. For improvement, AvePoint can provide details on how the tool's backup scope works. You can create a backup scope by following some rules provided by AvePoint. Based on the backup scope, you can create the container which will take the backup, but there are no clear details on the total licenses required for it and which mailboxes won't be covered under the backup because of the missing licenses. If AvePoint provides licensing details, it would be easy for an administrator to see the main sources or scope in terms of the license. The administrators can know the mailboxes considered under the backup.

I would like to see improvements in the tool's initial seed. The initial seed of around 10 TB of SharePoint data took 45 days to complete. 

Its price is a problem in some cases, and they want us to find a cheaper solution. 

Some customers choose other backup solutions because AvePoint is Office 365 and CRM backup system, but they have other backup needs for Azure and so on. Such customers often choose another backup solution instead of AvePoint. 

The performance could be better. It takes a couple of hours to back up a whole environment. The restoration could be faster. I rate the performance a six out of ten.

It is not a traditional restore process and it is somewhat limited in what we can do. We need to know specifically what data we need to restore, or a timestamp. If someone comes up to us and asks for the last six months of somebody's email then we can't do that.

With respect to the reports, I would like to enhance the reports on what was backed up and added. To have it show you the amount of growth in the ecosystem, of the sectors of Exchange, SharePoint, and OneDrive would be useful.