Supported databases
SQL Server, PostgreSQL, MySQL, Oracle and others with a standard driver, always through a dedicated user.
Integration · Legacy system
Your legacy ERP connects too.
Most mid-market and enterprise companies run at least one old, bespoke or discontinued system that nobody wants to replace because it works. brisk4 integrates with it without demanding a migration, using whatever path that system allows.
Possible paths
How to reach a system with no API.
| System scenario | Integration path | Note |
|---|---|---|
| Database is reachable | Direct SQL reads | A read-only user on dedicated views, never touching production tables. |
| Exposes SOAP or XML | Web service consumption | brisk4 translates SOAP into the conversation flow, with no rewrite of the service required. |
| Only produces files | Scheduled import | CSV, fixed-width TXT or XML dropped into a folder, SFTP or storage, read on a defined window. |
| Has a terminal or green screen | Purpose-built middleware | An intermediate layer built during rollout, with agreed scope and staging. |
| Exposes nothing at all | Case-by-case assessment | With no interface whatsoever, integration may not be viable. You hear that during the assessment, not after signing. |
Ready-made flows
What goes live first.
- Read-only views instead of broad accessInstead of a credential with access to the whole database, the IT team creates views carrying exactly the required fields. brisk4 reads only those, which lowers risk and simplifies internal approval.
- Caching for slow systemsLegacy systems tend to answer slowly. Low-volatility queries such as catalogue and price tables are synced on a scheduled window, and the customer gets an instant answer.
- Queued writes instead of direct onesWhen writing to the legacy system is required, brisk4 queues the operation and delivers it with retries and logging. An unstable old system does not take customer service down with it.
How we connect
Method and prerequisites.
Bespoke middleware
When there is no ready path, we design the intermediate layer during rollout, with fixed scope and staging.
Network security
Access over VPN, allow-listed IP or tunnel, according to your infrastructure team policy.
- Typical systems
- Senior, Sankhya, Microsiga and proprietary systems
- Required access
- Read-only user on dedicated views, or the service credential
- Network
- VPN, allow-listed IP or tunnel opened by your infrastructure
- Documentation
- A data dictionary, or support from whoever knows the system
- Write scope
- Defined case by case, with a queue and audit log
- Feasibility
- Assessed during the diagnosis, before any proposal
Frequently asked questions
Legacy ERP: questions.
My ERP has no API. Can it still be integrated?
In most cases, yes. Without an API the paths are direct database reads through a read-only user, SOAP web service consumption, structured file import, or an intermediate layer built during rollout.
Do I have to replace my ERP to use brisk4?
No. The premise is exactly the opposite: brisk4 adapts to the system you already have. Replacing the ERP is an expensive, risky project that integration exists to avoid.
Is database access not a security risk?
That is why the standard is a read-only user on dedicated views carrying exactly the required fields, access restricted by VPN or allow-listed IP, and logging of every query. Your IT team approves the scope before any connection is opened.
What if the system exposes nothing at all?
That case exists. A fully closed system, with no reachable database, no web service and no file output, may not be integrable. This is assessed and stated during the free diagnosis, before any commercial proposal.
Bring us your hard case.
In the free assessment we evaluate what your system exposes and tell you straight whether integration is feasible.