The loan origination software market hit $6.58 billion in 2025 and is projected to reach $7.35 billion in 2026. That growth is driven by one thing: lenders connecting their systems instead of running them in silos. Connecting Encompass with Microsoft Dynamics is one of the highest-impact integrations a mortgage operation can make.
Encompass handles loan origination, compliance, and processing. Microsoft Dynamics manages your sales pipeline, borrower relationships, and team workflows. When they run separately, loan officers toggle between systems, re-key data, and miss updates. When they connect, loan status changes flow to your CRM in real time. Follow-ups trigger automatically. Data entry happens once.
This guide covers what the integration looks like, how to set it up, and how to avoid the problems that derail most CRM-to-LOS projects.
Why Connect Encompass with Microsoft Dynamics
Most mortgage companies run Encompass for loan production and a CRM for sales management. The problem starts when those systems don't share data.
A loan officer closes a milestone in Encompass. The sales manager doesn't see it in Dynamics until someone updates a spreadsheet. A processor flags a missing document. The originator finds out hours later through email. These gaps cost time on every loan.
Integration solves specific problems:
- Real-time loan status in your CRM: When a loan moves from processing to underwriting in Encompass, Dynamics reflects that change without manual updates.
- Automated lead routing: New loan applications in Encompass create or update Dynamics contacts with the right assignment rules applied.
- Single data entry: Borrower information entered in Encompass syncs to Dynamics. No re-keying. No conflicting records.
- Pipeline visibility: Sales managers see real loan progress alongside CRM metrics in one dashboard.
Prerequisites for a Successful Integration
Rushing into integration without preparation causes most project failures. Confirm these items before writing any code or configuring middleware.
- Admin access to both systems: You need Encompass admin credentials with API permissions and Dynamics 365 system administrator rights.
- Defined field mapping: Decide which Encompass fields map to which Dynamics fields before starting. Loan number, borrower name, loan amount, milestone status, and assigned loan officer are the minimum.
- API credentials: Generate an Encompass Developer Connect API key and configure OAuth 2.0 authentication. Set up a Dynamics application registration in Azure AD for API access.
- Test environment: Build and validate the integration in a sandbox before touching production data. Both Encompass and Dynamics offer test environments.
- Middleware selection: Choose your integration method. Azure Logic Apps works natively with Dynamics. KingswaySoft provides pre-built Encompass connectors. Custom Azure Functions handle complex transformation logic.
Integration Architecture and Data Flow
The integration connects two REST API endpoints through middleware. Here is how data moves.
Encompass to Dynamics (Loan Data Push)
Encompass webhook fires when a loan milestone changes. The middleware receives the event, transforms the data into Dynamics format, and updates the corresponding Dynamics record. This covers loan status updates, document completion events, and closing milestones.
Dynamics to Encompass (Lead and Contact Sync)
When a new lead enters Dynamics through your website, marketing campaigns, or manual entry, the middleware creates or updates the corresponding Encompass contact. This prevents duplicate records and keeps both systems aligned from first touch to closing.
Bidirectional Sync Rules
Decide which system is the source of truth for each data field. Encompass owns loan data. Dynamics owns sales activity and lead scoring. Trying to sync the same field both directions without clear ownership causes data conflicts.
Step-by-Step Implementation
Step 1: Configure Encompass API Access
Log into Encompass as an administrator. Navigate to the developer portal and create an API client. Generate your Client ID and Client Secret. Create a dedicated API user with permissions limited to the data fields your integration needs. Test authentication with a simple loan query before building anything else.
Step 2: Register Dynamics API Application
In Azure Active Directory, register a new application for the integration. Grant it Dynamics 365 API permissions. Generate a client secret. Note the tenant ID, client ID, and secret for your middleware configuration.
Step 3: Build the Field Mapping
Create a document that maps every Encompass field to its Dynamics equivalent. Account for data type differences. Encompass stores loan amounts as decimals. Dynamics may use currency fields with different precision. Date formats, phone number formats, and address structures all need explicit mapping rules.
Step 4: Configure Middleware
Set up your chosen middleware platform. For Azure Logic Apps, create a flow triggered by Encompass webhooks. For KingswaySoft, configure the Encompass connector with your API credentials. For custom code, deploy an Azure Function that listens for webhook events and calls the Dynamics API.
Step 5: Test with Sample Data
Run 10 to 20 test loans through the integration. Verify that every mapped field transfers correctly. Check that milestone updates appear in Dynamics within seconds of the Encompass change. Test error conditions: what happens when Dynamics is temporarily unavailable? Does the middleware retry?
Step 6: Deploy to Production
After successful testing, enable the integration on your production instances. Monitor the first 48 hours closely. Check sync logs for errors. Verify that real loan data appears correctly in Dynamics. Train your team on what changes in their workflow.
Troubleshooting Common Integration Issues
- Field mapping mismatches: The most common issue. Verify data types match between systems. A text field in Encompass mapped to a number field in Dynamics will fail silently.
- Authentication token expiration: OAuth tokens expire. Your middleware must refresh tokens automatically. If syncs stop working after hours of success, expired tokens are the likely cause.
- Rate limiting: Both Encompass and Dynamics APIs enforce rate limits. High-volume operations need queuing and retry logic. Batch updates during off-peak hours when possible.
- Duplicate records: Without a clear matching rule (usually loan number or borrower email), the integration may create duplicate Dynamics records. Define your deduplication logic before going live.
Related Articles
- Microsoft 365 for Mortgage Industry: The Complete Guide
- Microsoft Copilot for Mortgage Operations: The Deployment Guide
- Microsoft Secure Score for Financial Executives: Your Guide to Risk Reduction
Frequently Asked Questions
What middleware works best for connecting Encompass to Microsoft Dynamics?
Azure Logic Apps offers native Dynamics 365 connectors and handles webhook triggers from Encompass without custom code. KingswaySoft provides pre-built Encompass connectors for SSIS-based data flows. Custom Azure Functions give full control for complex transformation logic. The right choice depends on your team's technical depth and the complexity of your field mapping requirements.
How does the Encompass-Dynamics integration handle GLBA compliance for borrower data?
Data transfers between Encompass and Dynamics use encrypted HTTPS connections with OAuth 2.0 authentication. Both systems enforce role-based access controls on borrower records. The integration inherits Encompass's compliance engine rules, meaning only authorized users see protected data in Dynamics. Audit logs track every data transfer for regulatory review under GLBA and state privacy laws.
Can the integration sync loan data in real time between Encompass and Dynamics?
Yes. Encompass webhooks push loan milestone events to your middleware within seconds. The middleware transforms and forwards that data to Dynamics through its API. Real-time sync requires properly configured webhook subscriptions in Encompass and a middleware layer with retry logic for handling temporary API failures on either side.
What is the typical implementation timeline for an Encompass-Dynamics integration?
A standard integration takes four to eight weeks from planning to production deployment. Simple field mapping with pre-built connectors lands on the shorter end. Complex transformations, custom business logic, and multi-environment testing push toward eight weeks. The field mapping and testing phases consume the most time. Rushing either phase leads to production data issues.
Build Your Encompass-Dynamics Integration Right
Integration projects fail when teams treat them as IT tasks instead of business process redesign. The technology is straightforward. The hard part is mapping your actual workflows, defining clear data ownership rules, and testing against real loan scenarios.
Mortgage Workspace supports 750+ financial institutions with managed IT services that include LOS-to-CRM integration planning, implementation, and ongoing monitoring. Our team works with both Encompass and Microsoft Dynamics daily.
Talk to a mortgage IT specialist about connecting your systems.
