You start without switching the old system off. An agent installed on your own network moves data between Mikro or Logo and the cloud. Nobody asks you to rip the old one out first.
The accounting ledger can stay where it is while stock, sales channels and field work move to EQLEM. Entering the same customer and the same stock into two separate programs comes to an end.
Who is it for?
For IT managers, system integrators, and businesses that don't want to shut down their ERP in a day. The business side sees the result (same customer, same stock); the agent, connections and monitoring are IT's job.
Where data must not leave the company network, the agent runs on that network. The cloud side manages the jobs and sensitive connections stay local.
What does it do?
You set up sync over applications and files. Products, customers, stock movements or documents flow in the direction you define. A failed record goes to a queue, gets retried and is monitored. You decide which fields are mastered in EQLEM and which stay mastered in the existing system.
If you don't write that decision down, you end up with data written on both sides and no way to tell which is right. The ownership table is the real work of an integration.
Why does the data stay in one place?
The agent reads from and writes to the existing system; the EQLEM cloud manages business rules and the queue. Platform Web users see integrated records in their own lists. Mobile and B2B use the same master data. When mapping is set up correctly, the product on the dealer portal and the product card in the ERP don't disagree. Data is created once and every screen uses it.
Key capabilities
Cloud orchestration
Sync jobs, schedules, direction (EQLEM ↔ existing system) and mapping rules are set in the cloud. You can see which job runs when. Changes are published in a controlled way.
On-prem agent
The agent inside your network reaches systems behind the firewall securely. Certificates, credentials and network rules follow your IT standards. Plan agent updates.
Mikro and Logo
There are connection scenarios for these two systems. Every installation starts with a look at the version, the modules in use and the data structure. We don't claim everything works out of the box; we do discovery and set up the mapping together.
New: master card and document writing to Mikro
- Missing cards are created with the document. When a document goes to the ERP and the account, stock, service, sales representative, cash or bank card does not exist there, it is created automatically from EQLEM data. Per connection and card type you choose “create automatically” or “reject”.
- Master cards are written from EQLEM to the ERP. For types whose sync direction is EQLEM → ERP, new cards flow to the ERP automatically. Updating existing cards is enabled in the connection settings; it is off by default.
- Newly transferred documents (Mikro v16/v17): stock count, warehouse transfer, cash collection/payment, incoming bank transfer, account transfer (virman), cash expense voucher.
- Settings in one place. Mapping and write settings are managed in EQLEM web under the ERP connection; Connect shows them read-only along with sync status (delivered, pending, error).
- Connect public API can write masters and documents (requires the ERP write API license).
Scope note: cheque/promissory note/credit card collection, outgoing bank transfer and opening vouchers are not included in this release. The new write features are for Mikro.
Application and file integration
File-based bridges (for example periodic export/import) can be set up too. A file should be a monitored job as well: did it arrive, was it processed, what was the error?
Monitoring and error handling
A failed record does not vanish silently. Queues, alerts and reprocessing catch stock or finance mismatches early.
A typical transition
Discovery first: which system holds the master record, which process moves to EQLEM? Then a narrow pilot, for example product cards and stock balances. If that holds, a second step such as sales or e-documents opens. While running in parallel you cut double entry on purpose, and you pick the cutover date with the business. Some companies stay on two systems for a long time, and that is fine.
"Connected" is not success. Less double entry and fewer mismatches is. Watch failed records, average delay and manual corrections, and reconcile daily in the first month, weekly after that.
Relationship to other products
- Platform Web: Integrated data is managed and reported here.
- Mobile / B2B: Cards in the field and on the portal can be fed by integration.
- Modules: Integration scope follows whichever modules are open.
Security
Credentials are protected on the agent side and least privilege applies. Network rules, logs and access records tie into your IT policy. Customer and address fields hold personal data, so check them against your privacy (KVKK) processes. Don't switch on the first production sync before running one full cycle in a test environment.
When you need it
If the current ERP stays live for a while, if accounting stays there while operations move to EQLEM, or if you want to keep product and customer data in one place and push it out to channels. On a fresh setup you often don't need it; when moving off an old system you usually do.
FAQ
Does everything sync both ways? Usually not. For master data, one direction with clear ownership is healthier. Two-way flows raise the risk of collisions and "last writer wins".
What if the agent goes down? Monitoring and alerts will tell you. The queue builds up and is reprocessed once the problem is fixed.
Which versions are supported? That is settled in discovery. Version, modules and customization differ for every customer, so expect a standard connector plus some customization.
Does the old ERP shut down when we move to EQLEM? It doesn't have to. You cut over when the business is ready.
How to start
Write the ownership table first: who owns product, customer, stock, document? Limit the pilot to one data type. Reconcile every day in the first week of production. Don't treat it as finished because "IT is done"; don't widen the scope until the business confirms the numbers are consistent.
Next step
Try it free, or use a technical discovery call to settle your systems, data ownership and the first pilot scope.