SharePoint integration with Salesforce – all you need to know

Ana Neto Company news, Technical 8 Comments

You heard about companies that use both Salesforce and SharePoint. It made you wonder if there is any synergy in using both applications. Can there be advantages to a Salesforce SharePoint integration, or does it simply not make sense? In this article we will have a look at the advantages and pitfalls and let you decide.

Why should you consider doing a Salesforce and SharePoint integration?

The fact is that Salesforce is one of the most expensive tools in the CRM world. Which does not mean customers are not happy. As Rebecca Wettemann, vice president at Nucleus Research, put it when speaking at the CRM Market Leader Awards 2018 “Despite high cost, we continue to see satisfied customers and high ROI across the board from Salesforce”.

Still, even a happy customer will be happier if there is a way to cut costs. That's where the SharePoint Salesforce integration comes in. The standard SharePoint storage is 10 GB. If that is not enough, you can buy extra storage at the very reasonable price of $0.20/month per GB extra. This is the first reason to integrate Salesforce and SharePoint.

The second reason is that SharePoint is better at storing loads of files than Salesforce. Yes, Salesforce has the functionality of attaching documents and notes to accounts – as an option. But all the invoices, contracts, statements of work and such can really pile up. They end up stealing valuable operating capacity, making Salesforce run slower.

It is just smarter to move the files to a document management system. A system designed for that and that provides you with more features, such as: you can work on documents together with your colleagues, you can share files to external users, you can see the complete version history.

What are the pitfalls of the Salesforce integration with SharePoint?

If you try to integrate Salesforce with SharePoint using only the tools you get with Salesforce, you normally use Salesforce's Files Connect.

The first thing to notice is that this will only allow for connecting to SharePoint Online. It used to work for SharePoint 2013 / 2010 on-premises versions, but the most current documentation no longer mentions any of this and the licensing options for it (the paid licence "Files Connect for on-premises external data sources") no longer seems to be available.

Then note that with this integration users will be able to access and share SharePoint files via the Files tab and feed, and search for them the same way they search their Salesforce content. But the file needs to be already in SharePoint to begin with. That might not be very intuitive to users, especially if they are already used to Salesforce but not so much so to SharePoint.

Next, you may not want to store financial and client-related files in the cloud. If you are trying to comply to data protection regulations like GDPR, it might be necessary to store this type of documents on premises.

And then there is the problem of getting the Files Connect integration to work. Just for starters, you have to work your way through the 137 pages of official documentation: the Salesforce Files Connect Implementation Guide, the Files Connect Setup Guide and the Files Connect User Guide.

And then you'll realise the real problem is that this documentation is outdated… it was written when Files Connect was launched back in 2015 and the updates to it have been scarce (most of them were last updated in 2016). As SharePoint online was significantly overhauled in 2018, some terms are not the same and some actions need to be performed in a different order.

Salesforce even launched a Common errors with Files Connect Office 365 page to try and help users. Still, many users follow the integration instructions only to end with an ugly error "Can't access external source - External data source is unavailable because of an error" or even more appalling "An unknown error occurred while accessing Files Connect". If you are trying to get an integration to work, it does not get any worse that getting an unknown error!... When you see this, you know it is time to look for an alternative.

Related posts

Is there a better way to integrate Salesforce with SharePoint?

The alternative to the Files Connect integration is to use a third-party integration tool. Document Extractor Built for Salesforce platform™ is such an integration tool. It transfers documents saved in Salesforce to SharePoint and replaces the original documents with links pointing to them at the SharePoint document location where those documents are saved.

Document Extractor built for Salesforce platform

The general idea is that the users still reach the files where they originally saved them – in Salesforce under the respective accounts. Running at the background, Document Extractor detects files, moves them to corresponding libraries in SharePoint and leaves a link in Salesforce instead. The user sees a link in the exact same place in Salesforce, so the user experience does not change.

the document is replaced by a link on salesforce that points to the document in sharepoint

Document Extractor also transfers the information about the Salesforce document creator, editor and owner to SharePoint for easier tracking of the documents. The name and extension of the original files are also transferred. The version history is also kept.

Document version history is kept intact on Salesforce allowing you to access each version of the document

Moreover, when the service finds two documents with the same name at the same location on Salesforce, it creates 2 documents on SharePoint, and it adds a suffix that allows both files to exist on SharePoint. The suffix is always based on a number, but the exact location of this number within the file name can be configured.

To sum up, Document Extractor brings you only benefits and helps to reduce storage costs dramatically.

What else can I integrate with Salesforce?

It is actually possible to integrate any kind of existing dataset with Salesforce as well. You can connect to Salesforce from any local database management system (DBMS) such as ORACLE, SAP HANA, MySQL, MariaDB or Microsoft SQL server. You get data from Salesforce into the local database or put data that is coming from the database into Salesforce.

This means all kind of flexible solutions can be created, perfectly adjusted to your data integration needs, as you can connect to any kind of already existing database. It is a great way of maximizing what you can take out of a Salesforce integration.

This is done with the CB On-prem Database to Salesforce Sync solution. This solution is based on the Connect Bridge platform. This is why you get all this flexibility in an out-of-the-box and tested solution.


Document Extractor is the trustworthy third-party tool that can better handle the integration of SharePoint and Salesforce.

Cheaper storage, GDPR compliant, Increase usability

This tool is available in AppExchange. You can study the product description and features, try it for free or buy the SaaS version.

Another option for SaaS deployment is ordering the product on Connecting software's website. Yet another option, in case you run a larger organization and prefer to be in full control of the product, on the website you can opt–in for the self-hosted version. Go for a SaaS free trial or a self-hosted free trial today!

Share this Post

Comments 8

  1. Hi Cesar, yes we support custom objects. Best would be to contact us and we can show and answer you all.

  2. We have thousands of documents in Sharepoint in an elaborate (traditional subfolder) structure, none in Salesforce. Would it be possible to get links from Sf records to the corresponding Sharepoint “folders” with all the documents teherein that already exists?

  3. Post

    Hello Mark,

    What we do with Document Extractor is more or less the opposite of what you need: we get the documents from SF to SharePoint. For your needs, I think our Connect Bridge platform is the best fit. This was the platform we used to build Document Extractor, so you could easily build your own custom software that does what you need. We will get in touch with through the e-mail you indicated to explore this option with you.

    Ana Neto

  4. Hi,
    All our files are uploaded in Sharepoint today. We want the users to be able to search Sharepoint from Salesforce custom object records and be able to link to records. Also if a user is uploading new files it should be uploaded to Sharepoint. Does your solution offer both ways?

  5. Post

    Our solution transfer files from Salesforce to SharePoint once they are uploaded to Salesforce of course. The solution then replaces the original files in Salesforce with URLs.

    Users can still search for those files in Salesforce as we maintain the document names and extensions in Salesforce.

    Initially if all your files are in SharePoint, then we could use our Connect Bridge platform to create URLs in Salesforce pointing to those documents in SharePoint. Those URLs could be created under all default and/or custom objects in Salesforce.

  6. Hi,

    It looks like this package would do some of what we wanted. But we also would like an integration whereby when a new custom object (i.e an opportunity) is created in Salesforce a folder is created within Sharepoint, and this is where all documents relating to this opportunity are stored. When the opportunity is then won our Salesforce system creates a project. We’d then want all project documents saved back in this one opportunity folder also. Is this something that is easily possible? Thanks

  7. Post

    Yes, whenever you add a new object, the product will automatically add a new folder on SharePoint. Furthermore, it’ll keep the same structure as well and all documents related to that new object.

Leave a Reply