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.
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.