Try our new research platform with insights from 80,000+ expert users
Cesar Danecke - PeerSpot reviewer
IT Supervisor at HORSCH BRASIL
Real User
Top 20
Enables us to share information more securely
Pros and Cons
  • "The online editing capabilities, file sharing, auditing, information security, ease of solution management, and the easy user adaptation to the platform are the most valuable features."
  • "The way to change the version of the files in SharePoint should be improved. The method of synchronizing files from local to the cloud can also use improvement."

What is our primary use case?

Our primary use case is for file sharing. SharePoint is implemented in our environment for files and user sharing. We also use it for simultaneous editions.

How has it helped my organization?

We had all the group files registered in SharePoint, including all local files. It was possible to share the information more securely. 

What is most valuable?

The online editing capabilities, file sharing, auditing, information security, ease of solution management, and the easy user adaptation to the platform are the most valuable features. 

What needs improvement?

The way to change the version of the files in SharePoint should be improved. The method of synchronizing files from local to the cloud can also use improvement. 

I would also like to see improvements in the interface, speed to load the page, mark favorite directories, synchronize the most recent, and the least accessed files automatically do the archiving. I would like to have an option at the first sync to choose more locations on your computer.

Buyer's Guide
SharePoint
March 2025
Learn what your peers think about SharePoint. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,767 professionals have used our research since 2012.

For how long have I used the solution?

We have been using this solution for more than five years.

What do I think about the stability of the solution?

The stability of SharePoint is very good, amazing.

What do I think about the scalability of the solution?

SharePoint is easy and has new features now. Scalability with SharePoint is good and easy for us at work. To maintain the product, we do not need a large amount of professionals, we currently have three professionals to administer the platform.

How are customer service and support?

Technical support with SharePoint is very good, very easy and includes support for multiple languages. It can be opened by several channels.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

What motivated us to switch solutions was the easy solution management, space scalability, additional features, easy synchronization, data security, and sharing control.

How was the initial setup?

The initial configuration of SharePoint was very easy. The configuration, training, and communication with the users took less than two months.

What about the implementation team?

Internal deployment of the system was conducted through a Microsoft partner and was very easy. We had our internal professionals deploy the system together.

What's my experience with pricing, setup cost, and licensing?

With regards to licensing, it depends a lot on what you need to do, there are many plans, and options to choose from, you need to plan and enjoy 100% of what the product offers, so you can decide if the value is right.

Which other solutions did I evaluate?

I used several products, but sharepoint brought them all together. I used windows file server, linux, file versioners, website to share documents.

What other advice do I have?

Compared with other products, SharePoint is very good. We do not have other products that are as good as SharePoint.

SharePoint is definitely richer in features with functionality which helps us to get our work done. I would rate SharePoint a 10 out of 10.

The solution is integrated with the entire Microsoft platform, from e-mail to Azure computing, so the solution as a whole is easy to manage and has a central administration that facilitates the view of the entire environment.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
CEO l Founder at a manufacturing company with 11-50 employees
Real User
Content and knowledge management system that's good for small-scale implementation, but needs improvement in stability, SSO integration, and document management
Pros and Cons
  • "What I like about SharePoint is that they keep up with a lot of updates, and they bring out new features. I also like that the system is integrated with the Microsoft 365 suite of apps."
  • "Document management and the ability to easily integrate single sign-on (SSO) are areas for improvement in SharePoint."

What is our primary use case?

SharePoint allows us to access and to search for what we have in our repositories.

What is most valuable?

What I like about SharePoint is that they keep up with a lot of updates, and they bring out new features. I also like that the system is integrated with the Microsoft 365 suite of apps.

What needs improvement?

Document management and the ability to easily integrate single sign-on (SSO) are areas for improvement in SharePoint.

Integrating SharePoint with other software is what I'd like to see in its next release.

For how long have I used the solution?

I've used SharePoint in the last 12 months. We use it internally in our organization.

What do I think about the stability of the solution?

The stability of SharePoint needs improvement, because once you start to get a large amount of data, it becomes very unwieldy, and it takes a long time to index. There are much better products for content management and knowledge management, when compared to SharePoint.

What do I think about the scalability of the solution?

SharePoint is not as scalable, particularly when implementing larger projects. It's good for small-scale implementation.

How are customer service and support?

I haven't personally contacted the technical support for SharePoint. It's our support team who contacts them.

Which solution did I use previously and why did I switch?

I used HPE Content Manager, formerly TRIM software, which used to be owned by TRIM here in Australia. We used TRIM a lot, then it was bought out by HPE, HPE has now been bought out by Microsoft.

Our organization chose SharePoint because they wanted to become accredited with Microsoft. They saw that Microsoft was the industry leader, so everyone wanted Microsoft. They saw Microsoft as the way forward, at the time.

How was the initial setup?

The initial setup for SharePoint was complex. Anything from Microsoft is complex.

What about the implementation team?

We implemented SharePoint in-house. We had a team that had experience with SharePoint when we decided to use it as our content management system. We had the skills from implementation and from attending numerous Microsoft training courses.

What was our ROI?

SharePoint is probably cheaper than dedicated, larger, and more useful content management systems, so you could get a return on investment from it, as long as you keep your infrastructure and everything up to date, and move to the new version when you have to.

What's my experience with pricing, setup cost, and licensing?

You have to pay for a license to use SharePoint, and any extended support from Microsoft is expensive. For example: if you have SharePoint 2013 and it reaches its end of life and goes out of support, you can migrate to SharePoint online, and that's a benefit, but you'll have to pay for extended support.

Which other solutions did I evaluate?

I evaluated Lotus Notes and HPE Content Manager.

What other advice do I have?

In terms of what features I found valuable in SharePoint, I haven't found many. I had come from IBM and was very entrenched with Lotus Notes and the Lotus Notes environment. I love Lotus Notes. When IBM sold Lotus, we started to move away from Notes, and I didn't like it, and then I was made redundant. Now I've been outside of IBM, having to use Microsoft, and I hate it.

My advice to people looking into using SharePoint for the first time is for them to 
look at how much data they have, and also look at the volume their data and data holdings are going to grow to. They should look at how long it would take to get to that point, then look at their ROI, and whether they would need to upgrade to another product in the near future. I'd say "Yes. Go for it.", but they should also look at the future, and how it would be long term.

I'm rating SharePoint a seven. Yes, it's good for organizations to start on knowledge management, but you'd have to look at how quickly you think your data will grow, and how soon it would take to get to that point, because it can become unwieldy.

Our company is a consulting partner of Microsoft. We're a service integrator that works in both the private and Australian Federal Government sectors.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
PeerSpot user
Buyer's Guide
SharePoint
March 2025
Learn what your peers think about SharePoint. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,767 professionals have used our research since 2012.
PeerSpot user
Lead Enterprise Architect at a tech services company with 1,001-5,000 employees
Consultant
I like the eServices Platform for developing applications on top off it.

What is most valuable?

  • Enterprise Content Management.
  • eServices Platform for developing applications on top off it.
  • Organization Portals.
  • Collaboration, Team working and sharing.
  • Document Management.
  • Simple workflows.
  • Enterprise Search.

How has it helped my organization?

  • Team sites and collaboration.
  • Main entry point for all applications.
  • Utilizing as a sign-on.

What needs improvement?

  • Workflows.
  • Performance.
  • Content Migration and sharing.
  • Reporting.
  • User experience and design response.

For how long have I used the solution?

I’ve used and implemented this software since the 2007 version until now (almost 9 years). My last implementation was in 2014, but I’m still using this as an end user.

What do I think about the stability of the solution?

We did have stability issues in the old versions and there were too many hotfixes, in the 2013 version. It’s more stable now, but it can still be better.

What do I think about the scalability of the solution?

I've never encountered any scalability issues. In the past, I’ve implemented it in with 3TB of information, without any problems.

How are customer service and technical support?

Technical support was very good, very responsive and professional.

Which solution did I use previously and why did I switch?

We used to employ Oracle UCM, but we replaced it because of the features provided in SharePoint along with the customizations, flexibility and ease of creating websites, workflows, pages and applications.

How was the initial setup?

Initial setup was straightforward, easy and successful.

What's my experience with pricing, setup cost, and licensing?

SharePoint is a suite of features and products within one product. Purchasing and implementing it needs optimal usage planning. I would recommend that you select the pricing or license type based on your usage. (In general, the internet license is the best).

Which other solutions did I evaluate?

We evaluated multiple alternatives including:

  • Oracle UCM
  • EMC Documentum
  • FileNet IBM
  • Alfresco
  • Liferay

Based on two selection exercises in two organizations; SharePoint was the best fit solution. The 2nd was EMC Documentum, then Oracle followed by FileNet and Alfresco, with Liveray last.

What other advice do I have?

Plan, Plan and Plan again! Usage planning is needed with up to 70% of your efforts being expended in information gathering and implementation and usage planning.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Technical Manager at Rigor Systems Limited
Real User
A reasonably priced product that provides excellent security features and enables users to have multiple versions of documents
Pros and Cons
  • "The security feature is valuable."
  • "The product must provide more automation."

What is our primary use case?

It is an eDMS. We use it for electronic document management.

What is most valuable?

The security feature is valuable. We have control over who has access to what and when. We also have the audit trails to review who accessed what at what time. The document versioning is also a valuable feature. We can have multiple versions of the same document. If there is an issue or if there's something that we missed on a document, we can easily roll back to the previous version and get our data the way it was.

What needs improvement?

The product must provide more automation. We must be able to automate tasks instead of doing them manually. The product must enable customization of features. It must allow integration with other systems. Integrating the tool into databases like Oracle or Microsoft SQL and pulling data from SharePoint would be helpful.

For how long have I used the solution?

I have been using the solution for close to five years.

What do I think about the stability of the solution?

I am satisfied with the tool’s stability. I rate the stability a ten out of ten.

What do I think about the scalability of the solution?

The tool is scalable. I rate the scalability a ten out of ten. We have eight users in our organization.

How was the initial setup?

The initial setup is easy. I rate the ease of setup an eight out of ten. It is a cloud solution. A person with some knowledge about the solution can deploy it in four to five hours. One person can do the deployment.

What's my experience with pricing, setup cost, and licensing?

The product is reasonably priced.

What other advice do I have?

I will recommend the solution to others because of its security features. Security is key for any organization. The tool is very scalable and stable. Overall, I rate the product a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Senior Consultant | Architect at DHL
Consultant
Applies to a wide range of company scenarios. You can integrate systems using workflow management middleware.

What is most valuable?

What makes SharePoint special is that it applies to a wide range of company scenarios; document management, knowledge management, project management, and records management.

When you want to save information, collaborate, or discover information, SharePoint is the first point-of-contact. You can search, use metadata, or access content via business intelligence created as Excel reports or dashboards. You can also access data from PowerPoint presentations, PowerBI, JavaScript. or jQuery.

Since the core structure is based on ASP.NET technology, you can manage simple development projects using standard .NET developers who have no specialization. You are also able to brand the product using HTML, CSS and JavaScript.

How has it helped my organization?

SharePoint has benefitted us a lot regarding optimization. We can automate document management, project management, and basic service desk functions.

The biggest value is that you are able to integrate systems using workflow management middleware. You can also use business intelligence to integrate data and display output on a SharePoint page with predefined restrictions applied for separate security groups.

There is occasionally a problem when an organization has several in-house developed systems without any integration connectors, etc. But this is only an issue in some really specific cases.

What needs improvement?

The allowed size of document libraries and lists, i.e., the number of items allowed, needs to be increased. This was already improved in the latest 2016 version of SharePoint.

Also, there need to be more options to brand solutions without needing developers. This would be good for end users.

For how long have I used the solution?

I specialized in the implementation, configuration, and branding of SharePoint for about 7+years. I’ve implemented solutions for many customers, large and small, in many architecture scenarios.

What do I think about the stability of the solution?

Stability is always a big issue, but not from the view of SharePoint itself. It’s more of an issue from the architecture and infrastructure point of view. Many customers implement SharePoint on virtual machines with dynamic memory allocation. VMs have slow disk access speeds that are below recommended specifications.

In these situations, there are always issues with stability, especially regarding search services, etc. For example, if you installed SharePoint on a virtual machine with dynamic memory, it could destroy the farm without any possibility of repairing it. You will then have to reinstall the whole farm. This would really be a big problem in the case of a farm with 10 virtual servers.

What do I think about the scalability of the solution?

Scalability issue are related to the previous question regarding stability.

How are customer service and technical support?

The main burden of technical support is on Microsoft partners, who implemented the particular solution. If customers want extra support from Microsoft, it is possible I think, but only if they have Software Assurance or an Enterprise Agreement. Even if a customer has one of these, they still mostly use Microsoft Partners for consulting, maintenance, or new projects.

Which solution did I use previously and why did I switch?

I previously used SharePoint Services 3, SharePoint Server 2007/2010/2013. Now, I am using SharePoint Online 2016 in a hybrid model that has new features and some new innovations. There are many reasons to switch.

How was the initial setup?

The initial setup was really difficult, because we had no experience. But, together with my colleagues, we managed to solve the initial issues. Then, we used specialized consultants to help us. All subsequent implementations, even in our own environment, were successful. There is always some troubleshooting to do, but this is normal.

What's my experience with pricing, setup cost, and licensing?

I advise to really plan carefully before implementing a solution. You need to allocate the correct number of licenses of various types (standard versus enterprise), including the required SQL licenses. Be careful with SQL licensing as many companies get this wrong. Licenses for other systems, for example, AD CALs or terminal server CALs, also need to be considered.

One of the most common mistakes is that a project plan will not take into account the use of features that require an enterprise license to run. For example, if the planners allocate only 50 enterprise licenses and the rest are standard licenses, there may not be enough enterprise licenses for all the components that need them.

What other advice do I have?

My advice is to look around the Internet and find some justification to negotiate with your boss to buy this product. Alternatively, you could go to the cloud as well and create a hybrid model to reduce the cost of infrastructure (using Azure/Office 365).

Also, optimize your business using automation, forms, document management, etc.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1142955 - PeerSpot reviewer
Senior Analyst at a consultancy with 1,001-5,000 employees
Real User
Top 20
Used for the creation and sharing of documents
Pros and Cons
  • "SharePoint is easy to collaborate with."
  • "The solution's support services and GenAI could be improved and made faster and more knowledgeable."

What is our primary use case?

I mostly use the solution for the creation and sharing of documents.

What is most valuable?

SharePoint is easy to collaborate with.

What needs improvement?

The solution's support services and GenAI could be improved and made faster and more knowledgeable.

For how long have I used the solution?

I have been using SharePoint for more than two years.

What do I think about the stability of the solution?

I rate the solution’s stability eight and a half out of ten.

What do I think about the scalability of the solution?

SharePoint is a scalable solution.

I rate the solution a seven or eight out of ten for scalability.

How was the initial setup?

The solution’s initial setup is straightforward and doesn't take much time.

What about the implementation team?

Our IT team deploys the solution.

What other advice do I have?

The solution has good integration capabilities. SharePoint supports remote work and team collaboration within our company. The solution's workflow data analysis and AI-driven content organization are good. I would recommend the solution to other users because of its reliability and AI features. SharePoint has helped our organization save time and money.

Overall, I rate the solution an eight to nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1451235 - PeerSpot reviewer
IT business analysis, development and governance at a tech services company with 51-200 employees
Real User
Stable and scalable collaboration system; good for document and file sharing, and offers fast issue resolution from its support team
Pros and Cons
  • "No code and low code, scalable, and stable collaboration platform. Straightforward to set up. Its support system is good and offers fast issue resolution."
  • "Integration needs to be more straightforward, particularly with Azure. SharePoint also needs a more comprehensive introductory course for users."

What is our primary use case?

Our primary use case for SharePoint is for document sharing and file sharing in projects where participants are from different organizations. It is a very good tool for users or participants of teams from different tenants inside the organization.

What is most valuable?

What I like most about SharePoint would depend on what the task is, e.g. if it's just simple document sharing then the document library is fine. The most exciting feature of the platform is that it's a no code or low code development platform. There's also Power Apps and Power Automate.

What needs improvement?

Despite the enthusiasm and very good promises offered by SharePoint, the usage of the power platform is limited, so that's an area for improvement, but I would suggest this just as a team feature.

It's hard to highlight other areas for improvement, but a better approach towards licensing power platform components for guest users would be great. SharePoint licensing costs could be lowered to introduce it to the outside guests of a tenant, then to supply them with power apps and power automate features.

A more straightforward integration with Azure, including better licensing in terms of using Azure components and functions, is also another area for improvement in SharePoint.

My advice for Microsoft, and this is something I'd like to see in the next release of  SharePoint, is for them to constantly improve training material. Currently, the training material is organized in a way where a new feature appears and is enforced, then they develop the training material for that new feature. What happens is that the total product or solution, e.g. SharePoint, then lacks overall introduction in terms of training. There should be a balance between the introduction of the tool and the introduction of the new feature. They should have comprehensive introductory courses for both Office 365 and SharePoint, instead of needing to Google for particular situations. I'm trying to get the knowledge bit by bit, so I'm losing the idea of the whole product, e.g. SharePoint is losing its essence. To get onboarded to any new product, it's important to get a good introduction into that product.

For how long have I used the solution?

I've been using SharePoint since 2006, so I've seen its "many flavors".

What do I think about the stability of the solution?

I find SharePoint to be stable. No complaints there.

What do I think about the scalability of the solution?

I have no complaints about the scalability of SharePoint.

How are customer service and support?

The support system for SharePoint works pretty well. We had a complicated situation about the reasoning why tenants and users are limited in terms of functionality, and the escalation and resolving of that issue, of that situation, went pretty fast, even for experimental features. It was quite straightforward to get access to experimental features, or find out why this access is limited, then fix it. I'm happy with the technical support for SharePoint.

How was the initial setup?

The initial setup of SharePoint is very straightforward. Microsoft did a very good job with onboarding new users of their platform, e.g. the Office 365 platform. There were a lot of good improvements for administrators of tenants of different parts of Office 365, including SharePoint.

What about the implementation team?

We implemented SharePoint through our in-house team, because we are a technology company, so we didn't need to use external experts or specialists for the deployment of the platform.

What other advice do I have?

I'm using SharePoint as part of Office 365, using it as a part of Teams and under the hood of Teams, so yes, I'm still using SharePoint.

SharePoint is deployed on public cloud. We have some projects where SharePoint 2019 is deployed as a server, but those are based on an integrations app, but mostly it's on Office 365, e.g. SharePoint Online. Microsoft is the cloud provider we're using for the platform.

I want to highlight that some organic growth was missed with Teams, because there's still complicated switching between tenants, e.g. Teams and SharePoint users. In this case, Teams users may work in different organizations, or are guests of different tenants and different organizations. Switching between tenants, or the ability to streamline and organize identity management logging into the system, e.g. to the cloud, to Office 365 with one ID or organization ID should provide options to do work with many organizations at the same time.

Currently, there is still the need to switch from one organization to another, to get the full toolsets of a particular tenant, so for users, that's quite annoying. For one organization that fits, and that works fine for an organization with guest users, but when we have multi-tenant situations, when people are collaborating on different projects, and when initiated or hosted by different organizations, switching from one organization to another should be improved.

We have 40 to 50 users of SharePoint, and they are involved in various projects run by customers. We also add users from other organizations, so the total collaboration space may include 200 to 300 users.

My advice to people thinking about using SharePoint, the very important lessons I learned during years of using the tool, is for them not to fight with it, e.g. they should not start to use it based on what they initially wished to use it for. It's best to first spend more time in getting a better understanding of the tool and its relevant capabilities. Learn SharePoint first. Spend time learning it.

I would give SharePoint a rating of nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Data Research Analyst at a tech services company with 501-1,000 employees
Consultant
It integrates collaboration, e-mail, document management, workflow, and content management.

What is most valuable?

When an organization is using Microsoft products already, the integration with the Microsoft Office products and the ability to leverage web-based Office products can transform business processes. I think there is a great benefit in integrating collaboration, e-mail, document management, workflow, and content management in one product. When I have been in the role of Information Architect, I took advantage of site content, metadata, advanced searches (FAST), web parts and the free applications.

There are a large number of solid third-party vendors that develop web apps that are easy to integrate and configure.

In smaller organizations or organizations with limited budgets, I was able to leverage SharePoint to provide a lot of functionality around workflows, content and document management with very limited customized development.

How has it helped my organization?

When implemented correctly, SharePoint and Office 365 can provide knowledge workers with the information they need quickly and it can provide for team collaboration. I have used it to transform relationships between business units and to break down silos.

What needs improvement?

I would focus on improving:

  • Integration with other enterprise products.
  • Simpler API.
  • Enhanced ability to report against structured and unstructured data in the environment.
  • More flexible security or training: I have noticed in organizations I joined that they lock down SharePoint so much, there is very limited functionality. As a result, teams in the same organization move to other collaboration tools when they would not need to.
  • Enhanced ability for users to back up and restore at various levels of the architecture.
  • Have SharePoint and Office 365 expand so that additional third-party products for document management are not necessary.

For how long have I used the solution?

I have used it for over 10 years.

What do I think about the stability of the solution?

Any issues regarding stability are generally caused by a lack of governance from planning of the underlying infrastructure through ongoing operations. With best practices in rolling out any application from an infrastructure planning and operations perspective, stability is not a significant issue.

What do I think about the scalability of the solution?

Frankly, I would make a case for many organizations to go with the SaaS-based option. I investigated the security around Office 365 in the past and it was HIPAA and PSI compliant. When organizations host these types of solutions instead of leveraging commodity hardware and expertise in a SAAS environment, that is where the issues of stability and scalability come up.

How are customer service and technical support?

Technical support is excellent.

Which solution did I use previously and why did I switch?

I have used Google and still do today. It is less expensive as a personal solution to document management, archiving and collaboration. It also integrates with my personal Google e-mail solution.

How was the initial setup?

Rolling out the enterprise version and ensuring integration with other products, budgeting for the hardware, and ensuring governance was not easy for SharePoint. However, I did leverage all of the plans and checklists that Microsoft provided, which made the process much simpler.

Office 365 was very simple to setup and I liked the ease of expanding storage when needed.

What's my experience with pricing, setup cost, and licensing?

It really depends on the size of the organization. For small organizations, I would advise them on just purchasing Office 365 for what they need in the next year or two. They can always scale up. In larger organizations, I would love to have the enterprise version. However, not every organization can afford the cost.

Which other solutions did I evaluate?

I compared it against Google's solution.

What other advice do I have?

I would advise others looking into implementing this product to consider Office 365 as a SaaS solution. I would also provide a governance plan and some common templates and training to get them started.

I would advise them to start with the teams that will leverage the product.

I would recommend finding ways to combine business process re-engineering with rolling out sites. This would be an easy win: combining process improvement with content management, document management, workflow and collaboration.

I would tell them to expect some amount of customization depending on what they wanted to leverage the product for.

As a portal, EDM platform for organizations, I think it is an excellent product. The limitations I have seen are the implementation and expectations of the technology, not the technology itself.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Anthony Q. DeLoach - PeerSpot reviewer
Anthony Q. DeLoachProgram Manager at a government with 10,001+ employees
Real User

Thanks for your write up, I am wondering if you have done workflows from a use of a form created in SharePoint Designer? I am finding that the workflows are not compact ( or least I have not figured out how do so yet) and the user(s) in line may not understand what they are supposed to do without some cerebral damage. Any example you could provide would be most appreciated.

See all 6 comments
Buyer's Guide
Download our free SharePoint Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Buyer's Guide
Download our free SharePoint Report and get advice and tips from experienced pros sharing their opinions.