Kolva connects to the ERP already in place. The connection path is qualified against the real environment, without turning deployment into an ERP migration program led by IT.
Choose the Right Connection Path
- Validated public paths — Use the guided path available for the relevant Sage or SAP family.
- Guided trial or demo — Odoo and Microsoft Business Central can be explored through a compact trial path before any production scope is confirmed.
- Specific environment — If no validated public path matches your ERP, Kolva reviews it privately before confirming coverage or implementation details.
Who Decides What
- IT validates the technical access and the security conditions required by the selected path.
- Kolva validates the connection, data mapping, and observable sync results against the agreed scope.
- Business owners resolve any ambiguity that requires a business decision before activation.
Prepare the Connection
- Confirm the ERP family, version, active scope, and the Kolva use cases to enable.
- Select the validated public path, guided trial, or private review that applies.
- Have IT validate the requested technical access in the real environment.
- Review the proposed mapping and send business ambiguities to the relevant owner.
- Approve activation only after the connection and expected results have been verified.
No ERP migration Your ERP remains the system of record. Kolva qualifies the connection around it; it does not require replacing the ERP to start the integration.
After Activation
Monitor connection status, last successful sync, data coverage, and actionable errors in Kolva. If the environment or business scope changes, revalidate the affected access and mappings before extending the sync.