Legacy and On-Premise Integration for Software With No API
For older or on-premise software that has no API and no vendor left to ask, we build a connection through database access, ODBC or scheduled file exchange, without disturbing the software your team still depends on.
Why Old Software Still Runs the Business
Legacy systems stay in place because they work, hold years of history, and replacing them is a project nobody wants to start. The problem is not the software itself but its isolation: no API, sometimes no vendor still supporting it, and staff who know exactly how to use it but no way to get its data anywhere else automatically.
Routes In When There Is No API
Direct Database Access
Where the application's database structure is understood, a read-only connection or database view extracts the data needed without touching the application layer at all.
ODBC Connections
Many older applications, including accounting and inventory systems, expose an ODBC driver even without a modern API, which is enough to build a reliable extract.
Scheduled File Exchange
Where no direct access is possible, the application's own export function is used to generate files on a schedule, picked up and processed automatically over SFTP or a shared folder.
A Small Installed Agent
For systems that must stay isolated from outside network access, a lightweight agent installed alongside the software reads data locally and sends it out on your terms.
What Has to Be Confirmed Before Starting
- Permission from whoever supports or licenses the software, so the integration does not void a support agreement or breach a licence term
- Whether the database schema is documented anywhere, or has to be reverse-engineered from the data itself
- Whether the system can tolerate a read connection alongside its normal daily use without slowing down
What This Does Not Involve
- Migrating away from the legacy system, which is a separate decision made on its own terms
- Working around a vendor's explicit block on external access, which we will not attempt
- Changing how staff already use the software day to day
Frequently asked questions
Can any old software be integrated, or are some genuinely impossible?
Most can, in some form, through database access, ODBC or scheduled exports. The exceptions are systems where the vendor has actively locked down all access and refuses to permit even read-only connections, which we confirm during discovery rather than assuming.
Will this affect how our team already uses the legacy system?
No. The integration reads or exports data alongside normal use; it does not change the application's interface, its performance for daily users, or how staff interact with it.
Do we need the original software vendor's involvement?
Sometimes, mainly for permission and to confirm the licence allows external database or ODBC access. Where the vendor no longer exists or cannot be reached, we work from what the software itself exposes.
Is direct database access safe for the legacy system's performance?
Read-only connections are designed to add minimal load, and where the system is sensitive, we use scheduled extracts or a database replica instead of querying the live production database directly.
What drives the cost of this kind of integration?
How much the database schema is already documented, whether it must be reverse-engineered, and how much data cleaning is needed since legacy systems often carry years of inconsistent entries.
What sets the timeline for a legacy integration?
Mostly discovery. Understanding an undocumented database or file format takes longer than building the extraction once it is understood, so this phase is where most of the schedule sits.
Tell us what you need.
Send a short brief and one of our engineers will come back to you — usually the same day.
- No obligation
- We reply the same working day
- Your details stay private