On September 23, 2025, Solifi announced its acquisition of DataScan, which now operates as DataScan by Solifi. Both companies' customers keep their existing service level commitments, so nothing has to change today. The decisions arrive at renewal: what your custom work costs to carry forward, and whether to stay, extend your current system or migrate.
We've kept the facts about both companies to what they published themselves, linked below. Everything else is written as questions to put to your own account team.
What Solifi and DataScan announced
Solifi's acquisition announcement describes DataScan as "a trusted North American leader in wholesale finance and inventory risk management." DataScan posted the same announcement on its own site. The parts a client needs:
- DataScan was founded in 1989 and is headquartered in Alpharetta, Georgia.
- Its products, per the release, are Wholesale Intelligence for wholesale loan servicing; RiskGauge, a digital audit platform; and Onsite, for field audits.
- DataScan operates under the "DataScan by Solifi" brand. Its CEO, Brian Koprowski, continues to lead the business as President and General Manager, and he joined Solifi's executive leadership team.
- "Customers of both companies will continue with their existing service level commitments."
- Solifi plans to integrate DataScan's wholesale lending and inventory risk solutions with what it calls its "API-driven, cloud-based Open Finance Platform." Financial terms weren't disclosed.
Solifi came out of an earlier round of consolidation. IDS bought William Stucky and Associates and White Clarke Group, then in 2021 the three relaunched under the Solifi name.
None of that makes the combined company better or worse for your program. It does put the product you license inside a larger portfolio, and decisions about that portfolio will shape what happens to yours.
What usually changes after a software consolidation
Acquirers promise continuity first. Change arrives later and at the edges of the relationship. It follows a familiar pattern across software deals:
- Product plans get re-sorted. When two product lines overlap, someone eventually decides which products stay as they are and which get folded together or retired. Enhancement requests filed before a deal end up competing with integration work for the same engineers.
- Support gets reorganized. Portals and ticketing tools get combined over time. So do professional services teams, and the people who know your setup may move.
- Commercial terms get redrawn. Renewal is where redrawn bundles and SKUs show up. With fewer independent vendors in a category, buyers have fewer alternatives to point to in a negotiation.
- Interfaces change. Combined products generally move toward a shared data model and a shared login. The APIs follow, and that's the change that reaches furthest into your own code.
There are real upsides too. A lender that runs wholesale next to leasing or ABL could end up with fewer contracts and one accountable vendor when an incident spans products. Servicing data and audit data under one owner could also make exception routing simpler, if the integration delivers on it.
Questions to bring to your account review
Bring these before the renewal quote arrives:
- Product plans. Which of the modules you run will stay as they are? Which will be combined or retired, and on what dates? Will those dates go into your contract?
- Contract carry-through. Will your current SLAs and price protections carry into the next term? If modules are re-bundled under new SKUs, how is renewal pricing calculated?
- Services capacity. Who delivers implementation and support for your instance after the close? Is it the team you know today or a combined services group? What are current lead times for statements of work and change requests?
- Data and interoperability. How will the other tools in your stack get data and events from the combined platform? Ask whether there's a documented data dictionary. Then ask which export formats and what exit assistance are guaranteed in writing.
- Audit continuity. Will your current audit providers and workflows keep working as they do now? Are any changes planned to where audit evidence and reconciliation records live?
Get the answers in writing. A product plan described on a call doesn't bind anyone at renewal.
What your custom development costs to carry forward
Plenty of wholesale and equipment lenders spent the last decade turning their loan management system into a one-of-one build. Older cores often lacked the APIs a lender needed, so teams filled the gaps with whatever worked at the time. That work falls into four piles:
- Custom features that filled gaps in the core product, such as special funding flows or bespoke dealer hierarchies.
- Integration jobs that sync the core with the CRM and general ledger or with audit and title vendors.
- Reports and extracts built directly against the vendor's tables.
- Workarounds your team runs beside the official system, like spreadsheet trackers or exception handling by email.
Each piece was built against one version of one vendor's data model. When that changes through an upgrade or a product merge, every piece has to be re-mapped or re-tested. Some of it gets rebuilt. You paid once to build it. You pay again to carry it forward.
That second bill rarely shows up on the renewal quote. It arrives as professional services hours, plus internal project time that would otherwise have gone to new work.
So count it before you renew. Pull the services invoices and internal hours spent keeping customizations working through your last two upgrades, and put that number next to the quote. Then ask your vendor which of your customizations its upgrade path covers. Ask who pays to re-certify the rest, and whether that cost sits in the license or gets billed as services.
Three options for what comes next
Every lender on either system is choosing between the same three paths. Which one is cheapest depends mostly on how much custom work you're carrying.
Stay and negotiate
If the system does what your program needs and your team knows it well, staying is a reasonable choice. A migration costs money and staff attention; don't spend either to escape a problem you don't have.
Stay on terms you've written down. Put the answers to the account-review questions into the renewal itself. Then confirm services capacity for any change requests you already have queued. Ask how they'll be scheduled against the integration work.
Extend with an orchestration layer
The middle path keeps your current core as the system of record. The work you differentiate on moves into a layer above it, which talks to the core through APIs. Funding requests can move there first. So can title operations or the dealer portal.
The point is where your custom logic lives. Today it's code written against one vendor's schema; in an orchestration layer it's configuration you control. The next upgrade or product merge then touches one set of integrations instead of every customization you've built.
VeroOS is designed to work this way, as well as to run as a full core. It has more than 40 live integrations, and Title Management is the capability lenders most often run standalone next to an existing core. Audits and the Dealer Portal can deploy the same way. We'd scope any connection to a Solifi or DataScan instance with you and your vendor before promising anything, because this option only works if your current system exposes the data the layer needs. We wrote more about how VeroOS works as an orchestration layer.
Migrate
Migration makes sense when your renewal window is open and the answers to the product-plan questions don't cover the modules you depend on. It also makes sense when your custom work is heavy enough that you'd be rebuilding it anyway.
It's the most expensive option. Data has to move and be reconciled. Staff retrain while the old system is still running, and dealers need to hear what's changing before it changes.
If you go this way, compare buying a platform with building one in-house; our buy vs. build breakdown covers the trade-offs. VeroOS can also be the core system of record for a whole floor plan program, from application to payoff. The wholesale finance software page shows what that covers. We run every implementation in five phases with a sign-off between each one, and data migration happens in the Build phase. We don't publish a standard timeline because it depends on scope and on the integrations involved.
Before you give notice, read our floor plan conversion checklist for what moves and how to tie it out. For a side-by-side look at the systems, see VeroOS compared with DataScan or VeroOS compared with Solifi.
Where we'd start
If we were running a program on either system, we'd do the custom-work count before anything else. It decides between the three options, and no renewal quote includes it. A lender with little custom code and a system that works should stay and negotiate hard. A lender carrying years of custom work has the most to gain from moving it into a layer it controls, whatever it decides about the core.
Solifi and DataScan questions
When did Solifi acquire DataScan?
On September 23, 2025, Solifi announced the acquisition. DataScan published the same announcement on its own site. Financial terms weren't disclosed. DataScan now operates under the DataScan by Solifi brand. Its CEO, Brian Koprowski, continues to lead the business as President and General Manager, and he joined Solifi's executive leadership team.
What is DataScan by Solifi?
It's the brand DataScan operates under as part of Solifi. DataScan was founded in 1989 and is based in Alpharetta, Georgia, according to the acquisition release. Its products are Wholesale Intelligence for wholesale loan servicing; RiskGauge, a digital audit platform; and Onsite, for field audits. Solifi said it plans to integrate those products with its Open Finance Platform.
Do Solifi or DataScan customers have to change systems?
The acquisition announcement doesn't mention a required migration. Solifi said customers of both companies will continue with their existing service level commitments. Plans for specific modules are a question for your account team. Ask which modules will stay as they are and which will be combined. Then ask what dates and contract terms come with each change.
What should lenders ask about Solifi integration?
Solifi describes its Open Finance Platform as API-driven and cloud-based. What that means for your stack depends on the APIs and export formats available for the products you license. Before you renew, ask for the data model documentation in writing. Ask for the export guarantees too, along with the terms for connecting third-party audit and title tools.
Can VeroOS run alongside Solifi or DataScan?
VeroOS is designed to run either as a lender's core system or alongside a core it already has. Title Management is the most common standalone deployment. Audits and the Dealer Portal can deploy the same way. Whether it fits a specific Solifi or DataScan setup depends on what that instance exposes. We'd scope that with you and your vendor first.




