Many businesses place EQLEM beside a working existing system / ERP rather than starting from zero. System sync manages data flow between EQLEM and sources such as Mikro (v15 / v16 / v17), Logo, and Piconn. The goal is not double Excel and double entry: keep the right record in the right place, accelerate operations on Platform Web and Mobile, and avoid cutting the link to accounting or a legacy core.
On this page, third-party products are referred to as the “existing system” or “existing ERP.” Sync works with the Integration product and integration module: orchestration in the cloud, an on-prem agent when needed.
Who is it for?
IT and integration teams manage mappings, agents, and service monitoring. It is critical for firms that run orders/stock in EQLEM while closing books in an existing system. In holdings, one company may be EQLEM-heavy and another existing-system-heavy; sync is the bridge. Warehouse and sales teams tired of double entry benefit indirectly.
How it works
Application integration (system sync), file integration, integration data, and the integration service are designed together. An on-prem agent reaches the local existing system / ERP; the cloud side manages queues, status, and mapping. Which cards and vouchers flow in which direction is defined at setup.
Typical flow: an account, stock card, or order is created/updated in EQLEM; sync writes the related record to the existing system; or the reverse, pulling master data from the existing system into EQLEM. Error queues and integration data screens provide visibility instead of silent failure. File-based integration complements specific scenarios.
Scope is clarified per customer setup: which companies, warehouse codes, and document types. If multi-company mapping is wrong, stock lands in the wrong place; so sync projects start with definitions and tests.
Benefits
You reduce double data entry. You keep existing investment while using EQLEM for operations, mobile, e-invoicing or CRM. Transition stays controlled: phased sync instead of a big bang. Support can inspect “which record stuck in sync?” from integration data.
You can separate operational speed from accounting discipline: the field flows in EQLEM while closing stays in the existing system; or the reverse, by design. What matters is consciously choosing the system of record.
Relation to modules and products
Integration management and the Integration product are the product counterparts. Inventory, sales, purchase, finance, and definitions are the most common sync domains. Monitoring and mapping are done in Platform Web. Licensing and authorization also cover integration service accounts: write rights must be granted carefully. Notifications can alert operations on critical sync failures.
FAQ
Does EQLEM replace my existing ERP? Not necessarily. In many scenarios EQLEM is the operations / solution layer while the existing system remains accounting or legacy core. Scope is project-specific.
Which systems are supported? Mikro v15/v16/v17, Logo, and Piconn are in the inventory. Other systems are evaluated separately and are not claimed on the site.
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? Flow depends on queue and service design; the goal is observable, reliable transfer rather than promising every line instantly.
Next step
Write down your existing system, the cards/vouchers to sync, and the system of record. After Try Free, run an integration discovery to produce a mapping plan; see the Integration product page.