4

I am in the same situation as the questioner two years ago, however I don't have a body of people using Confluence they see it as being promising and should be considered. Has the landscape changed with SP 2013? or are the conclusions the same...

Previous Question I have been using SharePoint now for 3 years and I really like it and would really like all employees in our company to move over to SharePoint from our Confluence Wiki.

I want them to have their Team Site and for them to save all their documents there and make use of all the collaboration features such as calendars, announcements, etc.

The problem that I have is getting them over to SharePoint but I cant tell them why they should rather use SharePoint since I know nothing about how the Confluence Wiki work.

What are the main differences between the 2 and how can I try and convince them to rather use SharePoint? asked by Etienne on May 31 '11 SharePoint vs Confluence Wiki

1
  • Hi James, firstly welcome to SharePoint StackExchange, your question has been flagged as being too broad to answer directly. In order to get a question answered it needs to be precise so for this you could ask: What are the key features you are looking for? What and how do the users want to user their wiki. Perhaps a feature grid of the current system posted and asking if this can all be covered off in SharePoint and look at what is actually better for your users instead of being so general. We aren't Confluence Wiki experts but we are SP experts :)
    – Hugh Wood
    Nov 1 '13 at 12:01
4

SharePoint and Confluence are two separate platforms for different purposes which do share similar functionality, are based on completely different technology, and for which can be difficult to move users either way.

Nothing has really changed. SharePoint 2013 does bring more to the wiki world and is making strides towards offering what Confluence has but it has not caught up in my opinion as administrator of both. The best option, still, is to use both and let the users choose which platform is best for them. Get the SharePoint Connector for Confluence and make everyone happy.

The main difference is that Confluence is an enterprise wiki compared to SharePoint which is a Microsoft application platform which includes document management, a wiki, web application hosting, social media functionality and more. SharePoint is working its way towards offering the same functionality as Confluence, in a Microsoft way.

SharePoint still can't compete with Confluence as an Enterprise Wiki. It is possible to get results from SharePoint if you are willing to throw enough resources at it. SharePoint will do as a basic wiki for an organisation that doesn't have Confluence or another wiki specific solution.

Confluence is still superior for information input and management of wiki pages. YMMV. The Confluence page hierarchy, plugins, security, user macros, page alias, metadata macros, scaffolding and user interface offer a superior wiki platform over SharePoint.

SharePoint is a superior DMS. Confluence is a better wiki. Both have online Office document editing capabilities, although SharePoint may be better. Both have search. SharePoint's Site Collection / Sites / Subsites structure may be more suitable than Confluence's site structure for organisations who need a deep site hierarchy.

Moving dedicated Confluence users to SharePoint is difficult, especially for users of Confluence plugins. Migrating data from Confluence to SharePoint can also be difficult even with migration tools.

SharePoint still takes a lot more resources - servers and administrators - than Confluence. SharePoint requires more planning, configuration, technical expertise, and time to implement. SharePoint requires much more system knowledge to administrate. Both could do with improvements for data export and data import.

When considering performance, SharePoint is still slow compared to Confluence. Waiting for pages to load is just painful.

User training and education about SharePoint is a serious issue. As a general rule you can grant a user access to Confluence and let them just go for it. For SharePoint basic training is needed to avoid problems later on.

Some users will try SharePoint and like it. Most won't. The only way I've seen to get people to move is to turn Confluence off. Most sites will run both. Considering that Confluence is quite cheap to licence and maintain the benefits outweigh the costs.

Your question has been asked here repeatedly for years now especially from people who think that SharePoint and Confluence are the same because you can create and edit web pages in both. Higher up in the chain managers ask why we are paying for two products which do the same thing: no one understands why users will not voluntarily move to SharePoint from that perspective.

The only answer I have so far, barring turning off Confluence, is:

  1. Create a SharePoint site for each Confluence Space using the same space name as the site name
  2. Create the security groups in SharePoint as the same names as in Confluence
  3. Give users an introduction to SharePoint showing the basic functions including wiki pages, document management, web parts, apps, etc
  4. In Confluence edit the home page or sidebar to create links to the SharePoint site. In SharePoint create links in the sidebar or menu to the existing Confluence spaces
  5. Reduce the barriers to entry for users to use SharePoint as much as possible
  6. Wait and see who gives SharePoint a try

Good luck convincing people to use SharePoint over Confluence. Carrot, stick, or both? In your position I would find teams in the organisation who are not using Confluence to start using SharePoint. I would then find Confluence loving teams willing to give SharePoint a go, offering them extended support to bridge into the SharePoint world. With users started, I would build the community, documentation and support for SharePoint over time to give the Confluence stalwarts good examples of what SharePoint can do for them.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.