Only the deadlines. All transition plans remain the same.
Encompass SDK transition
At ICE, our mission is to drive innovation and equip mortgage professionals with the ability to enhance the borrower experience, maximize ROI, and improve efficiency with advanced technology. To achieve this, we're continuing to invest in modern solutions and transitioning from legacy technologies, including the Encompass SDK (Software Development Kit).
To best support our customers, we are extending the SDK transition deadline to December 31, 2026. This additional time period provides an opportunity for our clients to confidently adopt and implement a robust, enhanced modern technology stack as you retire legacy integrations and applications.
Thanks to our collaborative efforts, significant progress has already been made:
- A majority of Encompass lenders have started to adopt APIs and Encompass native functionality which drive automation and innovation
- Partners have made more API-based apps available to lenders for improved user experience, speed and automation
- Lenders have saved costs related to custom applications and plugins by leveraging built-in Encompass features and workflow automation
We encourage you to continue building on this momentum, using this additional time to confidently complete the transition. Together, we can ensure a seamless shift to innovative, future-forward technology.
Key highlights:
- The SDK transition date has been extended to December 31, 2026
- The SDK will continue to be maintained but no new features will be added to the Encompass SDK as of November 1, 2025
- ICE customers and partners will be required to transition off the Encompass SDK by December 31, 2026
- Shared Lock and Plugins 2.0 will be available for General Availability in mid 2026
- For those needing transitional SDK access after December 2026, special access will be required and monthly fees applied
Mark your calendars for December 31, 2026
remaining to transition off SDK
Frequently asked questions
Stay up-to-date with answers that will help you reach this important milestone. Below are a few common questions we have received, and the full FAQ list is available on the Encompass Resource Center here.
What’s changed?
What’s the SDK transition?
The replacement of SDK technology with API and/or native Encompass functionality, now due by December 31, 2026.
What’s the EPC transition?
Moving from legacy systems (e.g., EMN, PSDK, TQL, EPASS) including ordering appraisal, closing fees, documents, flood, fraud, mortgage insurance, pricing, tax service, title and verifications to EPC by December 31, 2026. More information can be found here.
Why is the transition being extended?
To provide lenders and partners with sufficient time to transition with success.
What if we have already subscribed to Transitional SDK access?
If Encompass Transitional SDK Usage was added to your contract, there’s nothing for you to do. The contract will be updated in the coming months to reflect new billing details which won’t apply until after December 31, 2026.
With the extra time, should we slow down our progress?
No, please continue to prioritize your transition off the SDK.
What SDK integrations are being transitioned on December 31, 2026?
Encompass SDK (Software Development Kit) applications and plug-ins.
What should you be doing to prepare for the transition?
Please review the following information and resources.
SDK and legacy service ordering transition milestones
Mark your calendar for important SDK transition dates
Now |
|
Mid-2026 |
|
Before December 31, 2026 |
|
Why should you adopt APIs?
- Improved ROI – Using APIs allows you to reduce the time and money spent developing and maintaining multiple integrations and/or legacy technologies
- Speed – APIs enable you to accelerate development and deployment of new features and integrations using standardized technology
- Platform independence – RESTful APIs are not tied to specific platforms or technology, which means you can use the technology stack of your choice
- Scale – APIs are designed to handle high volumes of request which enables you to scale and manage increased traffic
Which SDKs are included in the SDK transition?
- Standalone SDK Modules (transition to Developer Connect APIs)
- SDK Loan Plugins (Migrate to SSF framework and Plugins 2.0 framework)
Are Custom Forms with custom code bases impacted by the SDK transition?
Custom forms are not included in the SDK transition. Custom forms with custom code bases will continue to work in Smart Client post sunset, but if similar functionality is needed for your web users, you should plan to transition them to SSF framework for web users.
Does this mean we have to fully transition to the web version of Encompass?
No, this is not a transition to the web. The web and desktop are different ways of accessing the same files. New features being released continue to be interoperable between desktop and web.
Which Encompass features can replace popular SDK plugins?
Native Encompass features replace the need for many plugins. Below are common plugins and the corresponding features available today in Encompass.
| COMMON PLUGIN FEATURE | NATIVE FUNCTIONALITY | AVAILABLE ENCOMPASS VERSION | ADDITIONAL INFORMATION |
| Address Verification | Address Verification | Desktop and Web | |
| Home Counseling Automation | Home Counseling Automation | Desktop and Web | Requires Encompass Consumer Connect; Roadmap for third party integrations. |
| AUS Automation | Automated Service Ordering | Desktop and Web | |
| Request Documents from Borrower | Automated Request / Send Documents | Desktop and Web | Requires Encompass Consumer Connect; Roadmap for third party integrations. |
| Conditions Management | Workflow Rules / Manage Conditions | Desktop and Web | Requires Enhanced Conditions. |
| Request Access to Loan File | Notify Me | Web Only | |
| Role Assignment | Workflow rule to Assign User to Role | Desktop and Web | |
| Email notifications | Workflow rule to Send Notifications | Desktop and Web | |
| Update a Custom Field | Workflow rule to Update Custom Fields | Desktop and Web | |
| Incomplete Application | Workflow rules + Scheduler to define NOIA process | Desktop and Web | |
| Automated based on Field Change | Workflow rule to respond to changes in loan file and take action Itask, role assignment, service orders, conditions, notifications, notifications, request documents, send documents) | Desktop and Web |
What are partners with SDK-based solutions doing to prepare for the transition?
Visit the SDK Partner Plan resource page for webinars and information about partner plans.
Do I need to do anything if I use Encompass Investor Connect for loan delivery to correspondent investors, warehouse lenders, due diligence, or servicing companies?
No, there is no action needed from lenders that use Encompass Investor Connect. The December 2026 transition is a move to current technology such as APIs and Encompass native functionality and a transition away from legacy integrations such as SDK, EPC, EMN and TQL. Encompass Investor Connect continues to be the preferred method of delivery and is not impacted by the December 2026 transition.
Are the Fannie Mae and Freddie Mac services part of this transition?
No, Fannie Mae and Freddie Mac services are not part of this transition currently. You will be able to continue to use the services password management via Encompass to orders services from Fannie Mae and Freddie Mac.
Webinars
Part 3 in our "Maximizing modern technology in Encompass" webinar series
Transitioning from SDK to Encompass Developer Connect.
Part 4 - A lender’s journey from legacy integrations to Encompass Partner Connect.
An Encompass customer and partner share their journeys of transitioning from legacy service ordering to Encompass Partner Connect (EPC).