How to Integrate Encompass with Salesforce CRM? (Full Guide)

The Problem Nobody Talks About Loudly Enough

The two systems are functioning perfectly on their own but your staff is drowning in work. The loan officer accesses Encompass to get an update on a loan milestone, but has to switch to Salesforce to access that same borrower’s record. The follow-up email is sent late because no one heard that the loan has already reached the underwriting phase. The sales manager recovers a pipeline report that is already two days old. This isn’t an issue with people, it’s a systems issue. 

Encompass by ICE Mortgage Technology is one of the most successful Loan Origination Systems in the entire U.S. mortgage industry. Whereas, Salesforce is the most reputable CRM. Both are extremely good at what they do on their own. However, when they are in separate silos, they create time inefficiencies, errors and ongoing frustration for all employees including your borrowers. 

This guide provides a complete step by step program for Encompass Salesforce integration. It will benefit mortgage lenders, brokers, or other technology professionals working in the mortgage sector. It further explains how to improve data connection between Encompass and Salesforce through streamlined workflows. 

What is Encompass and Why Does It Matter?

Encompass is developed by ICE Mortgage Technology. It’s a comprehensive LOS that supports the full mortgage lifecycle from application intake to final loan closing. It handles automation, compliance workflows, document management, and milestone tracking. 

Encompass is often utilized by mortgage businesses in their daily operations. They make use of Encompass in a number of ways including:

• To manage loan files and their respective pipeline stages
• To produce necessary disclosures and compliance documents
• To coordinate with the Underwriting department, Title department, and Appraisal department
• To run Audit Trails and Regulatory Reporting, and 
• To automate any repetitive tasks within the loan process. 

However, Encompass does not help mortgage businesses manage their front-end operations. Front-end operations include lead generation, borrower communication, marketing automation and relationship management. This is where Salesforce fits into the equation.

What is the Link of Salesforce with a Mortgage Workflow?

Salesforce allows lenders to track:

• New prospective borrowers and referral partners’ relationships
• Communication flow with prospective borrowers (calls, emails, text messages)
• Automated marketing campaigns
• Tracking of loan officer performance
• Business development and retention efforts

Why Does Integration Matters More Than You Think?

Here’s what happens on the business side when the two systems do not have a clear and concise point of contact.

• Duplicate data entry: When the file moves to Encompass, someone has to enter the same information again (SAME borrower name, address, income, employment, and SSN). This creates duplicative work; it takes between 20 and 30 minutes (or more) depending upon the complexity of the loan. Now multiply that work time over hundreds of loans in a given month.
• Stale pipeline visibility: Your Sales Manager is reviewing a report in Salesforce. The loan has moved to “Conditionally Approved” in Encompass. However it still shows as “In Underwriting” in Salesforce. So, decisions will ultimately depend on old data sets. 
• Missed borrower touchpoints: Once a loan reaches the main event, e.g., “Clear-to-Close” in Encompass, the borrower will receive some form of acknowledgment (a congratulatory e-mail, or an e-mail outlining additional steps). Without the connection between systems, that trigger doesn’t fire automatically, and somebody has to send out this communication: either they forget, or they send it manually. 
• Compliance exposure: You have 2 platforms, giving you two views of the truth. When an auditor asks you for a timeline of borrower interactions, you are retrieving information from both platforms and trying to collate them to formulate a complete timeline, resulting in a compliance gap. 

To describe the value of a successful integration of Encompass with Salesforce, let’s take a look at what happens when those integrations are correctly performed:

• When a lead is entered into Salesforce, the lead’s data automatically populates a new Encompass loan file.
• Any milestone updates within Encompass are instantly updated in the Opportunity record of the Salesforce instance.
• Encompass hitting critical loan stages automatically triggers emails to be sent from Salesforce.
• Loan officers can view live loan status directly in Salesforce without having to switch browser tabs.
• Leadership can see consolidated dashboards that blend CRM engagement with LOS loan data.

Can You Integrate Encompass with Salesforce Directly?

Many companies build integrated systems using Encompass Developer Connect APIs. However, the ICE Mortgage Technology also provides a standard way to connect systems through the Encompass Connector for Salesforce. 

By knowing this information upfront, you can create realistic expectations regarding the integration process, such as how to build or purchase an operational data pipeline after clicking the “Connect” button in an app store. 

There are three primary ways to obtain this: 

The 3 Integration Methods: Which One Is Right for You?

Method 1: Custom API Integration (Developer-Built)

A developer can use both the Encompass Developer Connect RESTful API endpoints and the Salesforce APIs to create a direct custom integration layer for the two platforms. 

How it works technically:

1. The first step is registering an application with Encompass Developer Connect. After registering the application, you will be able to generate API credentials. 
2. The integration will use OAuth 2.0 to authenticate, and use a token tied to your Encompass Client ID. Your token will expire on a schedule and will require your application to refresh it. 
3. Your integration layer will send requests to the Encompass Developer Connect endpoints to either read or write loan data in JSON format. 
4. There are several ways you can handle this on the Salesforce side, including Apex code, Platform Events, or REST callouts. However, in general you will be pushing/pulling the loan data into/from standard or custom objects. 

What can be synced:

• Borrower’s name, phone number, email address, income, and employment 
• Loan number, loan amount, loan type and interest rate 
• Milestone status (Application, Processing, Underwriting, Approved, Clear to Close, Funded) 
• Documents, conditions, tasks 
• The Loan Officer and Team information assigned to the loan. 

Field mapping example:

More and more developers are saying this. Mapping fields ends up a lot more complex when you actually work with them. Encompass has many different fields with corresponding IDs. Using real LOS knowledge rather than just the API Experience to determine which mapped field within your software solution to which field in Salesforce is necessary for your workflow.

One Developer, who builds these integrations for their living, states it like this: “Anyone could write the API calls, the difficulty comes from knowing the Encompass data model well enough to know which 40 out of 3000 fields within Encompass are relevant to your business rules.”

It is the best for any lender that has internal developer resources, or a trusted technology partner that they can rely on. Teams that require precise control over when data is moved, what transformation logic will be applied, as well as how the data will be transformed. 

Timeline: Typically 4–12 weeks depending on complexity.

Method 2: Middleware Platform (No-Code / Low-Code)

Middleware technology integrates Encompass and Salesforce so that there is no need to create custom code for translation. The most commonly used middleware platforms include: MuleSoft, Workato, Zapier and Make. 

1. MuleSoft Anypoint Platform is the enterprise-level option owned by Salesforce. It has excellent native connections to other Salesforce products. MuleSoft Anypoint is the best in carrying out complex/multi-system workflows with transformation logic, error handling and audit logging. On the other hand, there are trade-offs involved, such as price and required level of expertise to implement properly. 
2. Workato represents a happy medium. It has more capabilities than Zapier but is less complex than MuleSoft. Mid-size mortgage companies that require automation without having a full team of engineers, often execute Workato as their best solution. 
3. Zapier represents the light-duty solution where simple trigger-action automations can be created quickly and easily. According to MuleSoft’s report dated 2026, 71% of all businesses use some form of integration tools to increase the accuracy and consistency of their data. Zapier is typically more suitable for low-volume integration type uses, and for intermediate-type types. 
4. Make.com (previously known as Integromat) provides more visual control via Conditional Routing. It is particularly useful if you require branching logic without the need to code your automation solutions. 

The core trade-off with middleware:

Method 3: Integration Specialist / Managed Service

There are also companies that focus only on completing the integration of Encompass and Salesforce for you and providing a complete, ready-to-use integration solution. Most will manage everything from architectural design, field mapping, and developing, through testing and providing support after launch.

When does this option make sense?

• You don’t have development resources internally
• You have attempted DIY methods to integrate and have had failures or unreliable integrations.
• You want the integration to go live in a very short period of time, with the least amount of risk.
• You have compliance and data security concerns.

A reputable specialist will follow the following process for the integration:

1. Discovery – Your current Encompass setup, Salesforce org, and business workflows will be evaluated.
2. Architecture Design – Field mappings and the direction of data are set up along with some business needs for how the integration will trigger. 
3. Build – The integration is typically built using Salesforce Apex, REST APIs, middleware platforms, and Encompass Developer Connect APIs. 
4. Testing – The integration is deeply tested and all edge cases, errors, and success criteria as well.
5. Go live – The integration will be rolled out with zero downtime to the production environment.
6. Ongoing Support – The vendor will continue to provide proactive monitoring, will acknowledge performance issues and suggest improvements, as well as develop improvements to the integration after it goes live. 

Step-by-Step: Setting Up the Integration (Technical Walkthrough)

The following describes the actual steps to complete a custom API integration: 

Step 1: Access Encompass Developer Connect

Visit the ICE Mortgage Technology Developer Portal at developer.icemortgagetechnology.com. Here you will register your application, retrieve a Client ID and generate your API key(s). Additionally, you will create an API User in Encompass that has been granted the appropriate Role Based Permissions. This API User Account will be used by your Integration to authenticate itself. 

Important Note: The transition period for organizations to change from using SDK to using APIs has been extended by ICE until December 31st of 2026. While continuing to use SDKs is fine during this time, ICE highly encourages organizations to migrate to Encompass Developer Connect APIs for long-term support and more future improvements. 

Step 2: Configure OAuth 2.0 Authentication

To call Encompass APIs you will always need a valid Bearer Token to include in every API request. Below is the basic flow of how to get a Bearer Token:

• Register your app and get OAuth credentials. 
• Send an auth request to the designated OAuth token endpoint. 
• You will receive an access token for a specific time. 
• Use the bearer token in future API requests. 
• As needed, implement logic to refresh tokens. 

Step 3: Plan Your Field Mapping

Before you begin writing your sync logic, it’s a good idea to first map out your Field structure to figure out:

• The source of truth for each data point in Encompass, which will help you track these items down later.
• Which Salesforce Objects correspond with each data point either Lead, Contact, Opportunity, or Custom Object(s).
• What data types exist and if any transformation will take place (for example: different date formats from Encompass compared to Salesforce).
• The flow of data: does it happen from Salesforce to Encompass (lead creation), Encompass to Salesforce (status changes) or does both ways occur (bi-directional)?

The minimal field sets that most teams will synchronize between both systems are Loan Number, Borrower Name and Contact, Loan Amount, Milestone Status, Loan Officer and Estimated Closing Date. 

Step 4: Set Up Webhooks for Real-Time Triggers

Encompass Developer Connect has webhooks available for just about every major loan event throughout the life of the loan. For example, once a milestone changes, a document is uploaded or a condition is added. You subscribe to the appropriate webhook in the Encompass Developer Connect system and then you configure your integration layer’s endpoint to listen for the relevant event(s) that are sent and trigger an update to Salesforce. Webhooks help your integration appear to be “live” instead of done in batches. Without webhooks, you would have to occasionally poll the Encompass API to get the information you need. 

Step 5: Build Salesforce-Side Logic

You can use one or several of the following methods on Salesforce depending on the level of detail in the integration:

1. Platform Events – Publish events in your integration layer, subscribe to them within Salesforce flows or through an apex trigger
2. REST API Callout – Your integration pushes directly into the Salesforce object endpoints.
3. Apex Triggers – As new records come into Salesforce, this method applies data conversions and business rules.
4. Salesforce Flows – When a loan milestone is synced, trigger additional actions such as sending an email, creating a task, or updating the stage of the loan. 

Step 6: Test in Sandbox Before Production

Before executing any final plans, STNT developers should ensure they do all development and testing of their integrated solution in a test environment prior to implementing it in their production environment. 

Below are some specific tests to perform while in the sandbox environment: 

• Bidirectional Synchronization Accuracy – Verify whether a change that is made in Encompass reflects correctly in Salesforce and vice-versa. 
• Error Handling – Verify what happens when there is a failure in Synchronization. Does the system do a Retry? Is someone notified when there is a failure? 
• Prevention of Duplicates – When a loan is created from a Salesforce lead, does this also create a duplicate Contact Record. 
• Edge Cases – What happens with a refinance loan where the Borrower already exists as a Contact in Salesforce? 

Step 7: Go Live with Monitoring

Deploy to production and monitor the first few weeks closely with logging turned on. Track sync latency, error rates, and any data inconsistencies. A well functioning integration will be nearly unnoticeable to the end user. It means data will show up when it’s expected, where it’s expected. 

Security and Compliance: The Non-Negotiable Part

The Encompass side: All API calls authenticate using OAuth 2.0 access tokens. Access to data is controlled through role-based permissions and user authorization settings. 

The Salesforce side: Enterprise-grade security through field level security, profile controls and audit logging.

The Integration itself:

• All data in transit must be secured (TLS encryption using HTTPS)
• No PII data should be logged in plain text in your middleware or integration logs.
• Access tokens should NOT be hard coded in scripts, rather use a secure vault mechanism.
• Audit trails must track each data transfer for regulatory compliance under GLBA and CFPB regulations.

If you’re working with an integration specialist, ask particularly how they are compliant with GLBA regulations and the architecture of their audit logs. This is a key inquiry to differentiate a vendor with mortgage knowledge from one that is guessing.

Common Mistakes That Break Encompass-Salesforce Integrations

1. Field Mapping Phase is Skipped:

When you go to code without doing enough field mapping upfront you are likely to end up with wrong data types and broken sync logic. So hours of debugging will be needed to correct this.

2. Duplicates Have Not Been Planned For:

If you have 5 years worth of contact records in Salesforce and want to start syncing with Encompass borrowers without a duplicate strategy, you’re going to end up with double records.

3. Unit Directional Sync When Full Sync is Required:

Many teams will put together a unit directional sync (Encompass to Salesforce) only to find out later that the Loan Officer needed to update something from Salesforce that also needed to flow back to Encompass. Make sure your building for the full data flow your team actually needs. 

4. Failing to handle error conditions: 

Giving feedback that sync failed silently is worse than no feedback at all. Add retry logic, fail alerts, and a monitoring dashboard. 

5. Overlooking the discontinuation of the Encompass SDK: 

Companies using SDK-based systems must develop plans for migrating to the next generation of API technology from ICE’s Developer Connect APIs. As part of this, ICE is directing customers to implement Encompass Developer Connect APIs as the preferred long-term support option. 

6. Reckless Configuration of Zapier to Handle Enterprise Workloads: 

Zapier works wonders for simple automation in smaller-scale jobs. It’s not built for high-volume bidirectional communication and the sync of mortgage data. Use the right tool for the job. 

Integration Comparison: Tools at a Glance

Wrapping Up

Integrating Salesforce and Encompass is not a simple task. There are many different options available for building an integrated system. However, the majority of teams that have completed the integration can do less manual work, reduce the number of errors, complete loans much more quickly, and create the type of borrower experience that borrowers look for. 

If you are just beginning to think about integrating Salesforce and Encompass, start by conducting a discovery session. Document your current workflow so you can identify areas that will receive information from one of the two systems and where you have no movement of information between the two. In addition, this will be the best starting point for determining the resources that you will require to successfully complete the integration. 

Ready to streamline your mortgage operations and create a seamless borrower journey? Contact us today to learn more about our Encompass API Integration services and discover how we can help you build a fully connected lending ecosystem. 

Frequently Asked Questions

Q1: How do I connect Encompass to Salesforce?

You can connect Encompass to Salesforce using one of three methods:

• An Encompass Connector for Salesforce
• MortgageExchange®, as well as several connectors from Mphasis Silverline and EMS Consulting.
• Custom Solutions may be developed using the Encompass Developer Connect APIs in along with Salesforce APIs. 

Q2: Can Encompass integrate with Salesforce CRM?

Yes. Encompass can integrate with Salesforce through the official Encompass Connector for Salesforce, third-party integration platforms, or custom API-based integrations. 

Q3: What is Encompass Salesforce integration?

Through the integration of Encompass-Salesforce, you can send loan applications data directly to and from Encompass to Salesforce. This also allows for the smooth transfer of data into and out of both systems. 

Q4: What are the benefits of Encompass Salesforce integration?

Some of the benefits of integrating Encompass and Salesforce include:

• Manage leads to funding through use of Salesforce. 
• Hold borrower and loan data without needing to double input or rekey borrower information. 
• Leverage borrower/loan data to develop project workflows and establish marketing strategies in Salesforce. 
• Get a complete “360-degree” view of your clients including the loan status and all other pertinent information. 
• Manage the lending pipeline with greater accuracy. 
• Provide timely customer service by giving staff real-time access to every borrower’s, loan’s, and pipeline’s current status. 
• Provide a more secure environment for users through the use of advanced integrated security protocols. 

Q5: How to automate mortgage workflow with Salesforce and Encompass?

With automated mortgage processing, it is possible to automatically sync mortgage workflow tasks, loans, and key milestone data between Salesforce and Encompass. By doing this, loan officers and sales team members can minimize manual labor and facilitate the management of their customer relationships from within Salesforce. 

Q6: What is the cost of Encompass Salesforce integration?

There is no set price to connect the two systems by any specific methodology.  A couple of ways to connect include: 

Encompass Connector (Managed Package): 

You can ask ICE Mortgage Tech what their price is for the connector.  

Custom (Third Party) Integrations: 

Custom integration costs can range from several thousand dollars for basic workflows to six-figure projects for enterprise-grade implementations. So contact a certified salesforce partner for more information. Ongoing support costs may be incurred once the integration is live if the integration is complex.