Kolva connects to the ERP you already run without migration and without mobilizing IT beyond a focused technical-access validation. Business owners arbitrate any ambiguity that requires a decision.
3
Production-ready
2
Trial/demo
0
Inbound ports on production paths
Maturity
Your ERP remains the system of record. IT validates technical access, Kolva handles the connection work, and business owners arbitrate any ambiguity that requires a decision.
Detailed, production-ready paths for Sage X3, Sage 100/300, and SAP. Downloads appear only when the corresponding binary is published.
Odoo and Business Central are available through a guided trial/demo request. No binary is offered from this state.
Other environments are handled privately as specific cases. Their names and technical details are not published in this catalog.
Production-ready paths
These are the only ERP paths presented with technical scope and direct package actions in the public catalog.
SQL Server (TDS)
Sync clients, products, receivables, orders, contacts, pricing, stock, deliveries, and full finance data from Sage X3 to Kolva.
Validated source scope
Direct downloads are shown only for production-ready packages whose Windows and macOS binaries are published.
View Sage X3 integration pageOData REST API
Sync clients, products, invoices, orders, deliveries, production, maintenance, and finance data from SAP landscapes to Kolva.
Validated source scope
Direct downloads are shown only for production-ready packages whose Windows and macOS binaries are published.
View SAP integration pageODBC / SQL / API
SQL-driven agent for Sage 100 and Sage 300 estates, with finance, inventory, receivables, cost evidence, and configurable readiness coverage.
Validated source scope
Direct downloads are shown only for production-ready packages whose Windows and macOS binaries are published.
View Sage 100 / 300 integration pageGuided trial/demo
These paths are introduced by name and status only. The Kolva team confirms the right next step privately; no binary or technical scope is published here.
Private compatibility path
Kolva handles other environments as specific cases without publishing their names, links, or technical details in this catalog.
Clear role split
Kolva reads the existing system while the ERP remains the operational system of record.
IT confirms the technical access and security conditions required for the connection.
Kolva handles source discovery, technical mapping, and connection setup.
Business owners arbitrate any source ambiguity that requires a decision.
Refresh cadence and source timestamps remain visible after activation.
A connection goes live only after access, mappings, controls, and monitoring are verified.
Whether it is a public production path, a guided trial/demo, or a specific private environment, Kolva confirms the right connection path without turning deployment into an ERP migration program led by IT.