The solution has a very complex pricing model. We don't get involved with pricing or licensing but note the complexity when comparing to other vendors or when hearing things from customers. Pricing is rated a six out of ten.
OpenText 360's price varies depending on how long you've been a customer, how many licenses you have, and which products you use. Professional services are available at additional cost.
Learn what your peers think about OpenText 360 for SharePoint. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
Principal Technical Support Engineer at Veritas Technologies LLC
Real User
2022-07-18T07:40:58Z
Jul 18, 2022
I know the licensing costs involved as I'm doing the budgeting part. I cannot really talk about the licensing things that have been agreed upon between Microsoft and us. Our procurement and finance team have taken care of the cost and everything. That's about their guidelines and things that they have between our organization and Microsoft.
Enterprise Architect at a financial services firm with 5,001-10,000 employees
Real User
2021-12-21T13:08:00Z
Dec 21, 2021
If you are using the on-premises version, this product tends to be very expensive, whereas the SaaS product uses floating licenses, so it's usually cheaper. Additional costs may also apply, for instance, if you want to backup and restore your files, you would need to spend money on a third-party solution.
Its price is reasonable, but its licensing is very complex. This platform contains a number of pieces, and you have to be an expert in reading all the conditions in the license. They should simplify its licensing.
OpenText Process 360 is costly compared to SharePoint. There is a very costly investment required to license the product. I don't want to spend a lot on user licenses. The integration with OpenText Process was very complicated on licensing. This product supports the definition of roles and responsibilities. We are making a lot of investment in infrastructure and hardware with all this support.
With Process360, businesses can take advantage of enterprise process applications delivered on top of SharePoint that also leverage other Microsoft technologies for content management, collaboration, user interface design, and integrated communications.
The price is not cheap but entirely reasonable.
OpenText 360 for SharePoint offers subscription-based licensing. It has a reasonable price. I rate the pricing a seven out of ten.
Pricing is a part of the enterprise agreement that we have.
The solution has a very complex pricing model. We don't get involved with pricing or licensing but note the complexity when comparing to other vendors or when hearing things from customers. Pricing is rated a six out of ten.
OpenText 360's price varies depending on how long you've been a customer, how many licenses you have, and which products you use. Professional services are available at additional cost.
There is a license needed to use OpenText 360 for SharePoint and we pay annually. The price of the solution could be less expensive.
I know the licensing costs involved as I'm doing the budgeting part. I cannot really talk about the licensing things that have been agreed upon between Microsoft and us. Our procurement and finance team have taken care of the cost and everything. That's about their guidelines and things that they have between our organization and Microsoft.
SharePoint uses a subscription model.
If you are using the on-premises version, this product tends to be very expensive, whereas the SaaS product uses floating licenses, so it's usually cheaper. Additional costs may also apply, for instance, if you want to backup and restore your files, you would need to spend money on a third-party solution.
Its price is reasonable, but its licensing is very complex. This platform contains a number of pieces, and you have to be an expert in reading all the conditions in the license. They should simplify its licensing.
OpenText Process 360 is costly compared to SharePoint. There is a very costly investment required to license the product. I don't want to spend a lot on user licenses. The integration with OpenText Process was very complicated on licensing. This product supports the definition of roles and responsibilities. We are making a lot of investment in infrastructure and hardware with all this support.