Set up ERP synchronization only after the connection path has been qualified for the real environment. Kolva works with the ERP already in place, without turning deployment into an ERP migration program led by IT.
Confirm Readiness
- Sage and SAP families — Follow the validated path shown for the relevant family and environment.
- Odoo and Microsoft Business Central — Use the compact guided trial or demo path before any production scope is confirmed.
- Any other or specific ERP — Complete a private review before Kolva confirms coverage, access requirements, or deployment steps.
Validate Access and Responsibilities
- IT validates the technical access, security conditions, and operational owner for the selected path.
- Kolva validates the connection, agreed data scope, mappings, and observable synchronization results.
- Business owners resolve every ambiguity that requires a business decision, such as the meaning or expected use of a field.
Activate in Controlled Stages
- Confirm the ERP family, version, active modules, and target Kolva use cases.
- Approve the connection path and technical access for the real environment.
- Validate the proposed mappings against representative business records.
- Route unresolved business meanings to the accountable owner.
- Run a monitored initial synchronization on the agreed scope.
- Compare the resulting coverage and quality with the ERP source before enabling the ongoing schedule.
Approval gate Do not treat a successful connection as proof that the business mapping is correct. Activation requires both technical validation and business approval of any ambiguity.
Monitor the Synchronization
Track the current connection state, last successful run, agreed data coverage, and actionable errors in Kolva. Review unexpected gaps against the source ERP before changing the scope or schedule.
Resolve an Issue
- Access or connection issue — Ask IT to revalidate the approved technical access and current security conditions.
- Missing or inconsistent data — Compare the affected records with the agreed source scope and mapping.
- Business ambiguity — Pause the affected mapping and obtain a decision from the responsible business owner.
- Environment change — Requalify the affected path before resuming or extending synchronization.
ERP stays in place The synchronization is built around your existing ERP as the system of record. Replacing it is not a prerequisite for connecting Kolva.