To Top
API limits must be taken into account


Publish date:


Rajesh Verma runs a large pharmacy in South Delhi with certain tech tools, but he had heard about salesforce and the difference it could make to his business. However, he was vary of issues pertaining to integrating salesforce with his current apps. This article is for those who like Mr. Verma are seeking to integrate salesforce with their current applications and external cloud services. A secure, reliable, seamless, and scalable integration is what we all should aim for.  Salesforce integration and migration can prove to be a headache if you are not aware of the processes involved. Without a thorough understanding and planning, it can lead to unwanted situations and failures which are best avoided.  

3 things to consider before integration project: 

  1. Finalise the quantity and type of information / data that needs to flow or be shared between the systems. After this has been achieved, next is to determine the direction in which the information flow and what intervals should this flow happen (duration). 

  2. API limits need to be given due consideration. As with Salesforce, many other systems have an API that restricts the quantity of information it can transfer in a 24-hour cycle. 

  3. Integration schedule. Real-time and two-way integration is the ideal result of the integration process. Some issues may prevent this such as lack of finances or the company has multiple SIS systems, so some data is available only once a day. Therefore, most companies start with a daily batch process.

These are some of the commonly faced problems when integrating Salesforce with other systems: 

  • Mapping the data - The most commonly faced issue in this context is the mismatch of data and field types. The filed types vary from app to app.  

  • Duplicate data – A business must ensure that only clean data that is up to date and relevant goes in during integration.  

  • Auto-ID creation - Salesforce automatically generates its ID for each entity created or imported into it. The problem arises when records imported from external apps have pre-existing IDs and they already linked to other data/records via those IDs.   

  • Data migration - To avoid the issue of duplicate records, a business can use the Salesforce out-of-the-box features (Duplicate Management) or create a custom code.  

  • Defining the scope – Success must know/understand the scope of integration (whether to expose a service in Salesforce or consume external service.). 

  • Select best apps – Choose the best apps from AppExchange (Free/Licensed)  that serves your needs and requirements. 

  • Data validation – Validation of data is a key aspect while keying in data from an external source to Salesforce. Note some data fields are mandatory in Salesforce while they may not be in other apps.  

  • Information review – The team needs to meet to review all critical aspects of the integration process. Review all information so everyone is clear ad doubts are put at bay. 

  • Begin with clear integration scope - Salesforce strictly enforces governor limit, therefore, be ready with documentation, business processes, and have an understanding of the external systems. 

  • Real-time integration - It is a myth that importing or exporting data from Salesforce is the same as real-time integration.  Import/export of records run as batches and data may not be synced as expect to real-time integration.

Need help in Salesforce Integration Services? Contact the best Salesforce Integration Partner today!

About the Author

Mohit Sharma

Mohit is Practice Lead, 4x Certified Salesforce Consultant, Salesforce trainer, blogger, writer, and full-time husband. With over 8 years of experience implementing Salesforce, and an obsession for innovation, ready to tackle any new project that comes his way.

Leave a Comment