Most lenders reading about the Encompass SDK transition deadline have nothing to migrate.

That is not what the coverage suggests. The subject has produced a steady run of posts about an Encompass SDK sunset, an end-of-life, a cutover. Several carry a countdown clock. Some of it is written by firms that sell migration work.

Here is what ICE actually says, what it covers, and why your CRM connection is probably not in it.

The Encompass SDK transition deadline is not a sunset

The SDK does not switch off that day.

ICE’s own transition page puts it plainly. Lenders are required to transition off the SDK by December 31 2026. The SDK continues to be maintained, with no new features added. On what happens after December 31 2026, ICE says they remain committed to a hard sunset at a future date. They will communicate it with appropriate advance notice.

Read that again. The sunset is undated, and ICE has committed to warning you before it happens.

That changes the shape of this. It is a required migration with a date, not a shutdown with a countdown. Both deserve a plan. Only one of them deserves panic.

The date has also moved before. ICE originally set October 31 2025, then extended to December 31 2026 in August 2025. Treat the current date as firm and the framing around it as something to re-check.

What is actually in scope

Two things, and they share a date.

SDK applications and plug-ins. Anything built against the Encompass Software Development Kit. The Encompass SDK to API migration has three destinations. Developer Connect APIs, Encompass native functionality such as business rules and the workflow engine, or Plugins 2.0.

Legacy service ordering, moving to Encompass Partner Connect. The old-style vendor connections for appraisal, title, flood, verifications, documents, pricing and similar. This replaces EMN, PSDK, TQL and ePass.

Those are two separate projects on one deadline, and lenders routinely plan for one and forget the other. The plug-in question belongs to whoever owns your Encompass configuration. The service ordering question belongs to whoever manages your vendor connections. At many shops those are different people and neither has asked the other.

Two separate Encompass transition projects sharing one December 31 2026 deadline

What is not in scope, which is most of it

Four exclusions sit in ICE’s FAQ and almost nobody repeats them.

Custom forms are not included. ICE says custom forms with custom code bases continue to work in Smart Client after the transition. If you want the same behavior for web users, that is a separate move to the SSF framework.

Encompass Investor Connect is not impacted. No action for lenders using it to deliver to correspondent investors, warehouse lenders, due diligence or servicing.

Fannie Mae and Freddie Mac services are not part of it. ICE’s wording is “not part of this transition currently,” so this is the one to re-check rather than assume.

It is not a transition to the web. ICE answers that directly with “No.” Desktop and web are two ways into the same files, and features stay interoperable.

And the one that matters here: an API integration was never in scope. The SDK transition is a move away from SDK technology toward APIs. A system already connected through Developer Connect is on the destination, not the thing being retired. Shape’s Encompass integration is API-based and has never used the SDK. There is nothing in this for a Shape customer to migrate.

If you are not sure which yours is, establish that before budgeting for anything. It is the same question as what your LOS connection actually carries, asked one level down.

A platform decision made now should account for it too. Connection type is one of the four tests we apply. And mortgage CRM integrations built API-first were never exposed to this deadline.

The fee advice in circulation is out of date

If you have read that transitional SDK access will cost you monthly from January 2027, that was true when written. It is not ICE’s current position.

ICE’s page now says two things. To get access after the deadline, you reach out to your ICE Relationship Manager and request complimentary transitional SDK access. And for anyone already signed up under the previous arrangement, ICE is explicit. If Encompass Transitional SDK Usage was added to your contract, you will not be billed for the access you requested.

Free, on request, and lenders already on a paid arrangement are being released from it.

The fee claim traces to ICE’s August 2025 announcement and was reported accurately at the time. ICE changed the policy afterward. Several pages still carrying the old version were correct on the day they published. That is an argument for checking the vendor’s page rather than an article about it.

Request the access if you need it. It is not automatic and it goes through your Relationship Manager.

The plugin limit nobody mentions

Plugins 2.0 is the replacement path for SDK loan plug-ins. It comes with a constraint buried in an answer about something else.

ICE says lenders moving to Plugins 2.0 will have a limited number of active plugins. It encourages consolidating several into one where possible, to improve startup times and network performance. ICE has said more detail comes before release.

For a shop running six or seven plug-ins, that is not a port. It is a consolidation project, and consolidation means deciding which behaviors survive. That decision takes longer than the technical work and it needs the people who use the plug-ins in the room.

Worth knowing now rather than in November.

What to do before December

Six things, and the first two cost nothing.

Inventory what uses the SDK. Applications, plug-ins, and anything a vendor built for you. Most shops do not have this list.

Separate the two projects. Plug-ins and service ordering are different work with different owners. Put a name against each.

Ask every vendor what their plan is and by when. The answer you want is a date and a replacement path. “We are working on it” in September is a flag.

Check which Encompass features now replace what your plug-ins do. ICE publishes a mapping table covering address verification, AUS automation, conditions management, role assignment, notifications and field-change automation. Several plug-ins are now native functionality.

Request transitional access if you need it, through your Relationship Manager. It is complimentary and it is not granted automatically.

Confirm your CRM connection type. If it runs on Developer Connect APIs, it is out of scope. Establishing that is part of our read on CRM implementation. Where a connection does have to change, filling the gap the integration leaves is a separate piece of work.

Frequently asked questions

What is the difference between Encompass Developer Connect and Encompass Partner Connect?+

Developer Connect is the API set for building integrations against Encompass, and it is where SDK applications move. Partner Connect is the platform for ordering services from vendors, covering appraisal, title, flood and verifications. Both are current ICE technology, both appear in the December 31 2026 transition, and they solve different problems.

Does the Encompass SDK transition change loan data or field structure?+

ICE describes it as a technology transition rather than a data migration. The change is in how software connects to Encompass, not in what the loan file contains. Custom forms continue to work in Smart Client. If a vendor tells you the transition requires remapping your fields, ask them to show you where ICE says so.

What happens if the vendor who built our SDK plug-in is no longer in business?+

The problem is yours and it is worth finding now rather than in November. Check what the plug-in actually does, then look at whether Encompass native functionality covers it. ICE publishes a mapping of common plug-in behaviors to native features. It covers address verification, conditions management, role assignment and field-change automation.

Do lenders who use a different loan origination system need to do anything?+

No. This is an ICE Mortgage Technology change affecting Encompass customers and the partners who build against it. Running LendingPad, Byte, ARIVE or anything else puts you outside it entirely. The question worth asking is whether any of your vendors connect to Encompass on your behalf.