How Long Does an Encompass SDK Migration Take — and What Drives the Cost?
Nobody can quote your SDK migration from a blog post, and you should be suspicious of anyone who tries. What we can do is show you the scoping math — the same structure we use to produce fixed-scope quotes — so you can rough out your own exposure before talking to anyone.
The timeline skeleton
The assessment: about a week. A focused audit of your instance produces the full inventory — every plugin, custom form, batch automation, and legacy service-ordering flow — with each component mapped to its API-era destination and priced. If a firm needs a month just to tell you what you have, that’s a them problem.
Individual components: weeks, not months. A typical headless integration — a polling job becoming a webhook consumer, a batch process moving to the v3 APIs — migrates, runs in parallel against its SDK version, and cuts over inside a few weeks. Components ship independently; you don’t wait for a big bang.
The whole program: driven by your longest pole and your start date. A lender with eight simple automations can be SDK-free in a quarter. A lender with thirty components including UI-heavy plugins and a dozen vendor dependencies is a multi-quarter program — which, with the deadline on December 31, 2026, is precisely why mid-2026 is the last comfortable moment to start.
The cost spectrum, component by component
From cheapest to most expensive:
| Component type | Relative cost | Why |
|---|---|---|
| Retire it | Free | Every audit finds components nobody uses. Deleting is the best migration |
| Replace with native rules/workflow | Config, not code | Field validation and milestone automation often map to business rules — days of admin work, zero hosting |
| Headless automation → API service | Low-to-moderate | Well-understood pattern: OAuth, API calls, webhook triggers, parallel-run validation |
| Custom input forms → Encompass Web | Moderate, scales with form count | Rebuilds, not ports — but also a cleanup opportunity; most lenders rebuild fewer forms than they retire |
| Legacy service ordering → EPC | Moderate, vendor-dependent | The code is manageable; the schedule risk is coordinating each vendor’s EPC readiness |
| UI-heavy Smart Client plugins | The expensive tail | No mechanical translation — these need a design decision before an estimate means anything |
The distribution matters more than the line items: in most instances, the bulk of the inventory sits in the cheap rows. The budget conversation is really about how many components you have in the last two rows — and you don’t know that number until you’ve done the audit.
What makes migrations more expensive than they needed to be
Every driver below is controllable, and every one of them is controlled by starting earlier:
- Undocumented components with departed authors. Reverse-engineering what a 2018 batch job does costs more than rebuilding it. Institutional memory is a depreciating asset — capture it now.
- No parallel-run window. The cheap way to de-risk a cutover is running old and new side by side until outputs match. Start in October and there’s no calendar left for that — you’re doing big-bang cutovers in production during year-end.
- The Q4 capacity crunch. Migration engineering capacity across the whole ecosystem is finite, and every lender that waited is bidding for it in the same final quarter. Scarcity pricing works the way it always works.
- Paying twice. Slip past the deadline and you’re funding the migration and Transitional Access fees — with approval risk on top.
Fixed scope or open meter?
One structural note, because it changes the math: an hourly engagement prices the uncertainty into your bill — every surprise is billable. A fixed-scope engagement prices the uncertainty into the vendor’s estimate, where discovering surprises is their problem. The precondition for fixed scope is a real inventory, which is one more reason the assessment-first sequence exists: nobody can fix a price for a pile they haven’t counted, and you shouldn’t accept one.
The number that matters this week
Not the total cost — the assessment cost, which (at least with us) is zero, and the calendar, which is not. A week from now you can be holding a priced, risk-ranked inventory and deciding with real numbers. That document is worth the same whether you build with us, someone else, or your own team.
Book the free assessment — senior engineers, a written fixed-scope plan per component, and no obligation past the first call.