You start without switching the old system off. An agent installed on your own network moves data between Mikro, Logo or Piconn 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?
It is designed for IT managers, system integrators, digital transformation teams, and businesses that do not want to shut down their existing ERP overnight. Business units see the outcome (same account, same stock truth); technical ownership sits on the agent, connectivity, and monitoring.
In multi-company or on-prem-constrained environments, running the agent on the corporate network can be critical. The cloud side manages orchestration; sensitive connectivity stays local.
What does it do?
With Integration you set up application- and file-based sync scenarios. Objects such as products, accounts, stock movements, or documents flow in the direction you define. Error queues, retries, and monitoring aim for operational continuity. You clarify which fields are master in EQLEM and which remain master in the existing system.
Without that clarity, integration turns into “we write both sides” chaos. A good integration is an ownership matrix put into practice.
How one database works
The agent reads/writes from the existing system; the EQLEM cloud side manages business rules and the queue. Platform Web users see integrated records in their own lists. Mobile and B2B run on the same master data. So the product shown on the dealer portal does not conflict with the product card in the ERP, when mapping is correct.
Integration stops EQLEM from being a second island. Data is created once, and every screen shares it.
Key capabilities
Cloud orchestration
Sync jobs, schedules, direction (EQLEM ← → existing system), and mapping rules are arranged in the cloud. Operations can monitor which job runs when. Changes are published under control.
On-prem agent
An agent running inside the organization provides secure access to systems behind the firewall. Certificates, credentials, and network policy follow IT standards. Agent updates should be planned.
Mikro, Logo, and Piconn support
Common existing-system/ERP connection scenarios are covered in this family. Every installation needs discovery of version, module scope, and data dictionary; prefer discovery + mapping discipline over a promise that “everything works out of the box.”
Application and file integration
Alongside API/application integration, file-based bridges (for example periodic export/import) can enter the scenario. What matters is that the file is also a monitored job: did it arrive, was it processed, what was the error?
Monitoring and error handling
Failed records must not disappear silently. Queues, alerts, and reprocessing catch finance/stock inconsistency early. Integration health should be visible on the dashboard or operations lists.
A typical transition approach
First discovery: which system is master, which process moves to EQLEM? Then a narrow pilot (for example product cards + stock balances). After the pilot is validated, a second ring such as sales or e-documents opens. During parallel running, double entry is deliberately reduced; cutover date is chosen with the business. Some companies stay hybrid for a long time, and that is valid.
The success measure is not “connected,” but “double entry and inconsistency went down.”
Relationship to other products
- Platform Web: Integrated data is managed and reported here.
- Mobile / B2B: Cards shown in the field and on the portal can be fed by integration.
- Modules: Integration scope is drawn according to which inventory, sales, and finance modules are open.
Integration alone does not create product value; it creates value with open modules and correct ownership.
Security and compliance
Credentials are protected on the agent side; least privilege applies. Network segmentation, logging, and access records bind to IT policy. For account/address fields that contain personal data, align with your privacy processes. First production sync without a test environment is risky.
When is Integration required?
If you will keep the existing ERP live for a while, leave accounting there while operations run in EQLEM, or hold master data in one place and distribute it to channels, Integration is the right product. Greenfield setups sometimes do not need it; brownfield (existing-system) transformations often make it critical.
FAQ
Do we sync everything bidirectional? Usually no. One direction plus ownership is healthier for master data. Bidirectional sync raises collision and “last writer wins” risk.
What if the agent goes down? Monitoring and alerts surface it early. The queue builds; after fix it is reprocessed. Silent loss is not acceptable.
Which system versions are supported? Clarified in discovery. Version, modules, and customizations differ per customer; expect a standard connector plus a customization share.
Does the old ERP shut down when we move to EQLEM? Not mandatory. A hybrid period can last a long time. Cutover happens when the business is ready.
Implementation tips
Write the ownership matrix first (product, account, stock, document). Limit the pilot to one object type. Run at least one full cycle in a test environment. In production, produce a daily reconciliation report for the first week. Do not close integration as “IT is done”; do not expand until the business confirms consistency.
Next step
Try free, or use a technical discovery call to clarify your systems, master-data ownership, and first pilot scope. As Integration stands up, Platform Web, Mobile, and B2B share the same truth.