The CPQ Blog

Maintaining Model Integrity: SAP VC/AVC to Tacton CPQ Post-Go-Live

Written by Rolf Staflin | Jan 8, 2026 7:00:00 AM

You have converted your SAP data, built the test suite, and deployed the model in Tacton CPQ. The hard work is done, right? Not quite.

The real challenge starts after go-live: keeping the model aligned with reality. SAP and CPQ evolve at different speeds, and without ongoing governance, model drift can quietly appear and cause major issues.

The risk of drift

Model drift happens when the SAP and CPQ models no longer reflect each other.

  • A component is retired in SAP but remains selectable in CPQ.

  • A new variant appears in SAP but never reaches the configurator.

  • Constraint updates in SAP change valid combinations that CPQ still allows.

Once these gaps appear, sales teams lose confidence in the configurator. Rebuilding that trust can take far longer than preventing the issue in the first place.

Build a governance loop

At cpq.se we recommend a simple but disciplined governance cycle built on four pillars:

  1. Version control
    Store every exported rundown and TCX model in a repository. Document which SAP snapshot it came from and what changed since the previous version.

  2. Automated validation
    Run your test suite regularly. Catch regressions automatically instead of relying on manual testing.

  3. Change review
    Involve both a modeler and a domain expert in every major update. One checks technical consistency, the other ensures that the product logic still makes sense.

  4. Visual diffs and dashboards
    Use your intermediate Excel format to compare versions side by side. Seeing which variants or rules have changed makes reviews faster and clearer.

Governance as a quality enabler

Governance is not bureaucracy. It is what keeps automation reliable. When handled properly, it turns your conversion process into a repeatable and trusted system that stays synchronized with SAP.

Looking ahead

Future setups may integrate AI-based validation, automated release notes, and dashboards that connect SAP and CPQ data in real time. But even a basic governance loop today can prevent costly rework and confusion later.

Key takeaway

A well-governed model is a living system. With continuous validation and clear ownership, your CPQ configuration will stay aligned with the real product offering and continue to deliver reliable results long after go-live.