Most businesses put EQLEM next to a system that already works rather than starting from zero. System sync manages the data flow between EQLEM and Mikro (v15 / v16 / v17) and Logo. The point is not to enter the same record twice: operations speed up on Platform Web and Mobile while accounting can stay in the old system.
Sync works together with the Integration product and module: the cloud manages the jobs, and an agent on your network reaches the existing system when needed.
Who is it for?
IT and integration teams manage mappings, the agent and service monitoring. It is a core need for firms that see orders and stock in EQLEM but close the books in their existing system. In holdings, one company may lean on EQLEM and another on the old system, and sync links them. Warehouse and sales teams tired of double entry benefit indirectly.
How it works
The agent on your network reaches the existing system; the cloud side manages the queue, status and mapping. Which cards and vouchers flow in which direction is defined at setup. File-based transfer is used as a complement in some scenarios.
Example flow: an account, stock card or order is created in EQLEM and sync writes it to the existing system. Or the reverse: master data comes from the existing system into EQLEM. Failed records show up in the error queue and on the integration data screen instead of disappearing.
Scope is settled in each setup: which companies, which warehouse codes, which document types. If the multi-company mapping is wrong, stock lands in the wrong place, so the work starts with definitions and tests.
Don't start with "let's connect everything". Begin with account and stock cards, then orders and vouchers, and don't move to the next document type until the error queue is empty. Try it first on a test account or a small company scope.
Benefits
Double entry goes down. You keep your existing investment and still use EQLEM for operations, mobile, e-documents and CRM. The move happens in stages, not in one day. Support can answer "which record got stuck?" from the integration data.
The field can run in EQLEM while closing stays in the old system, or the other way round. What matters is that you decide on purpose which system holds the record of truth.
Relation to modules and products
The product counterparts are the Integration module and the Integration product. Stock, sales, purchasing, finance and definitions are the most commonly synced. Monitoring and mapping are on Platform Web. Grant write permission to integration service accounts with care. You can receive notifications on critical sync failures.
FAQ
Does EQLEM replace my existing ERP? Not necessarily. In most setups EQLEM runs operations while accounting stays in the existing system. Scope is set per project.
Which systems are supported? Mikro v15/v16/v17 and Logo. If you use something else, we look at it separately.
Is an agent required? When on-prem access to an existing system is required, an agent is used. The cloud side manages orchestration.
Is sync real time? No, it runs through a queue. We don't promise every line instantly; we aim for transfers you can follow and rely on.
Next step
Write down your existing system, the cards and vouchers to sync, and which system holds the record of truth. Then we'll produce the mapping plan in a discovery call; see the Integration product page.