System

Integrating a bespoke or legacy system that has no API

In short: A system with no API can usually still be integrated. The routes, in order of preference, are import and export files the system already supports, direct read or write to its database, a vendor-provided interface such as a COM or SDK layer, and, as a last resort, controlled automation of its own screens. Better Systems Co. chooses the most reliable route the system owner is willing to approve in writing, and reads back every write to confirm it.

Phil's supplier runs an ordering system built years ago for its own staff. There is no way in from outside, so every door Phil sells is typed into an email and typed again at the other end. Everyone has always said the system cannot be connected to. Usually that is not true.

The people are made up. The facts about Bespoke and legacy systems with no API below are checked and sourced.

What is true about Bespoke and legacy systems with no API

  • Most legacy systems store data in a database that can be read, and many accept import files, which is enough for one-way automation.
  • Screen-level automation is fragile when screens change and is used only where no other door exists.
  • Better Systems Co. connected a bespoke ordering website to a supplier's legacy ordering environment by a method the supplier permitted; see the case study.

Checked 11 November 2026. Vendors change their products; we confirm the current position during the audit.

Routes in

RouteWhen it fits
Import and export filesReliable, supported, one-directional.
Database accessRead for reporting and checks; write only where the schema is understood and the owner approves.
Vendor SDK or COM interfaceWhere the vendor provides one, such as Sage Data Objects for Sage 50.
Approved screen-level automationLast resort, with read-back confirmation and alerts.

What Better Systems Co. does with it

We put the automation in front of Bespoke and legacy systems with no API. It reads what arrives by email, PDF, spreadsheet or from another system, checks it against your records and your rules, and lines it up for a person to approve. Only what your team approves goes into Bespoke and legacy systems with no API, by one of the routes above. Your team keeps the screens they know. See order processing automation, invoice and document automation and connecting existing systems.

Most firms run this alongside other systems, each with its own login. We can put what all of them know on one screen with one login, and build the weekly figures from every one of them with reporting automation.

Guides

Other systems we work with

Find out what the typing is costing you

A 20-minute call. You tell us about your Sandra, your Dave or your Phil, and how the job gets done today. We tell you honestly whether automating it would pay, and what it would cost.