The materials available in this article are for informational purposes only and not for the purpose of providing legal advice. You should contact your own advisors with questions regarding the mortgage loan origination software content herein. The opinions expressed in this article are the opinions of the individual authors and may not reflect the opinions of MeridianLink, Inc.
If you’ve been putting off a mortgage loan origination software upgrade because it feels like a project for “someday,” or your LOS contract renewal is quietly creeping closer, you’re not alone.
That was the backdrop for a recent MeridianLink® Mortgage webinar, where Vince Furey, SVP of Mortgage, and Lester Alitagtag, Services Program Manager, walked through one of the most frequently asked questions: how long does a mortgage LOS upgrade actually take, from the first conversation to the day your team goes live?
The answer is more nuanced than most institutions expect. And the gap between what people assume and what the process actually requires is exactly where projects go sideways.
The question behind the question
When lenders ask how quickly they can complete a mortgage loan origination software implementation, what they’re really getting at is how to ensure a smooth, successful transition.
As Furey put it during the webinar: “You shouldn’t look at it from the perspective of how quickly you can do it. You should look at it from the perspective of what are the key things you need to be planning for to have a very smooth, successful transition.”
That reframe matters. Speed is not the goal. Confidence is. When your team goes live on a new system, the measure of success is not how fast you got there. It’s whether your staff can do their jobs without hesitation, whether your workflows are actually configured rather than just replicated, and whether leadership can point back to the original business case and say the outcomes were achieved.
Execution readiness is what ultimately enables velocity. When requirements are clear, configuration is deliberate, and collaboration between lender and platform provider is tight, implementation timelines can compress without sacrificing stability. That pattern shows up in the scale of delivery across the industry, with MeridianLink completing 39 mortgage LOS deployments in a single year, including multiple implementations delivered in under 60 days. It reflects not a rush to go live, but the ability to reach value faster when the groundwork is strong.
Its fastest implementation on record was 58 days, completed by Essex Mortgage, a high-volume independent mortgage banker.
Three stages, one timeline
Alitagtag framed the full scope of an LOS upgrade as three distinct efforts, each with its own timeline and resource demands. Understanding them is essential to planning a realistic go-live date.
The first is a current-state assessment. Before a lender can evaluate new solutions, they need an honest picture of where they are today. Can your existing system support where your organization needs to go? Where are the operational pain points? Which departments are most constrained by the technology they’re working around? This stage involves internal conversations across origination, underwriting, processing, and closing. It takes time to do well.
The second stage is due diligence and vendor selection. This is where many institutions underestimate the internal complexity. Budget approvals, board sign-offs, steering committee formation, and RFP processes don’t happen quickly in regulated institutions. For credit unions and banks especially, these steps can extend the timeline by months. Alitagtag’s advice: build a project plan for this stage before it begins. Know when your budget decisions happen, when board meetings are scheduled, and whether this is realistically a 2026 effort, a 2027 effort, or a 2028 one. Targets should be based on those constraints, not wishful thinking.
The third stage is the actual implementation: configuration, testing, and go-live. This is where the clock most people think of actually starts. But by the time you reach it, the groundwork from the first two stages either sets you up for a clean run or leaves you chasing a compressed timeline you were never going to meet.
The preparation stage is not optional
Once the contract is signed and the implementation begins, Alitagtag emphasized that what happens before a single system configuration decision is made can determine whether the whole project succeeds.
Customer engagement and responsiveness are the most common early risks. Implementation teams need information from their clients to move forward. When responses are slow, when third-party vendor credentials haven’t been secured, or when internal project ownership is unclear, momentum stalls.
Alitagtag emphasized the importance of timing: “During your implementation project is not the time to be shopping for vendors for a new CRA or a new flood vendor. That should be things that come into the preparation even before the selection has been made.”
This is the kind of detail that sounds obvious in retrospect and gets missed in the optimism of a new contract signing. If your team is still evaluating credit reporting agencies or flood vendors while configuration is underway, you’ve introduced a dependency you didn’t need to.
On the people side, Furey returned to a consistent theme: define success before you start. What does a successful deployment actually look like in measurable terms? Is it a reduction in underwriting touch points? A faster turn time from application to close? Specific pull-through rate improvements? Defining that early gives the entire implementation a direction and gives leadership something to point to when the project is complete.
The configuration mindset shift
Alitagtag addressed a pattern he sees consistently: teams trying to rebuild their old system inside the new one.
“A common risk that we see during the configuration stage is resistance to change. Folks are trying to replicate their old system in the new system…because that’s how they’ve always done it and that’s the only thing they know.”
As an example, he walked through closing cost templates. Many lenders manage dozens or even hundreds of templates, assigning them loan by loan. In MeridianLink Mortgage, that process is automated entirely: the system calculates fees based on scenario logic configured upfront by an administrator. The efficiency gain is significant. But realizing it requires letting go of the old approach, not recreating it.
This isn’t about forcing change for its own sake. It’s about recognizing that the new system was built with different capabilities, and the value is only accessible to teams willing to use them. Alitagtag framed it keenly by pointing out that the initial go-live is not the final form; it’s the starting point for any continued innovation.
Testing: More than checking if it works
The testing phase often gets treated as a technical exercise. Alitagtag reframed it in a more constructive light.
“It’s not really: ‘Is APR calculating correctly?’ It’s: ‘Do I know how to send disclosures in the new system? Can I do my job?’”
The functional questions matter too, of course. Documents, disclosures, pricing engine eligibility, and profit margins all need to be validated. But the deeper goal of testing is role-level confidence. Every processor, underwriter, loan officer, and closer should be able to perform their core tasks without hesitation before the organization goes live.
He also advised being strategic about scenario coverage. Test against the scenarios that represent the bulk of your loan volume first. The edge cases can come later. A well-organized testing plan—one that includes explicit checklists, documented progress, and strong management enforcement—is more valuable than a rushed pass through every possible workflow.
The 30–60 day window you should plan for
Alitagtag noted that lenders should target going live on the new system 30 to 60 days before they lose access to the old one. The reason is straightforward: loans already in flight through your old system need to complete their lifecycle there. Trying to migrate disclosed loans mid-process creates compliance complexity and operational risk that almost no one is prepared for.
When asked about how often that window gets overlooked, Alitagtag’s estimate was about 85% of the time. Most lenders aim for a go-live date that coincides exactly with when their old system access expires, and then scramble to manage in-flight loans under pressure they created by not planning earlier.
If your contract renewal is on the horizon, that 30–60 day buffer needs to be built into your planning from the beginning as a required part of the timeline.
What the hindsight data says
MeridianLink surveys its customers after implementation, and a few themes surface consistently. Lenders wish they had involved loan officers in testing earlier rather than keeping the process too close to an internal project team. They wish they had stronger leadership support to enforce testing participation across staff who were already managing full workloads. They wish they had been more intentional about moving users off legacy habits rather than leaving adoption to happen organically.
None of these are surprises in isolation. What makes them meaningful is that they come from real institutions that went through the process—and, in hindsight, identified exactly where the work could have been better distributed and more deliberately managed.
Where to start
The institutions that have smooth, confident mortgage loan origination software go-lives are the ones that start earlier than they think they need to, plan for the full three-stage arc rather than just the implementation phase, and approach the transition with a clear definition of what success is supposed to look like.
“How long does this take?” has a real answer. But that answer only makes sense when you’re counting the right things from the right starting point.
If your contract is set to renew in the next 12 to 18 months, that starting point is now.
