SAP Visual Enterprise - migrate, modernise or extend
Strategic architecture for the SAP VE installed base, from someone who built the platform.
I was Product Owner for SAP Visual Enterprise Generator at SAP and Architect/Lead Developer at Right Hemisphere before the acquisition. For ten years I architected the platform you're now running. Today I help organisations decide what to do with it — and execute that decision without losing the digital twin assets and process maturity they've built.
SAP Visual Enterprise is in a strange place.
SAP has shifted its investment to Enterprise Product Development (EPD). The active development pipeline on VE has slowed. Existing customers are increasingly hearing the migration conversation from SIs and SAP account teams. But for most installed-base customers, the migration story doesn't hold up under scrutiny:
You are being told that your solution is outdated
EPD isn't a like-for-like replacement. Significant capability gaps exist around heavy-CAD ingestion, the Visual Data Integration workflow, and custom Python operations.
SAP VE is already an integral part of your business
Years of digital twin asset libraries, custom integrations, and trained business processes don't transfer cleanly.
Push for migration
Migration estimates are usually 18-30 months and seven figures, with substantial business risk during transition.
A functionally adequate solution
Meanwhile, VE itself remains functionally adequate for what most customers actually do with it day-to-day.
Being pushed to move into the Cloud
You like your data on-premise but you are being told that you need to move to the cloud.
The honest answer for most VE customers isn't migration. It's extension - adding modern capability around VE - or modernisation - bringing VE itself into a cloud-hosted, modern-integration posture. The hard part is figuring out which path actually fits your specific situation. Most consultancies have a financial incentive to sell migration because migrations are large projects. I don't.
Our SAP VE Decision Framework
After working with multiple VE customers across manufacturing, aerospace, and industrial equipment, three questions determine the right path:
1. How business-critical is VE to your daily operations?
2. How deep is your existing investment in digital twin assets and integrations?
3. What's your team's internal VE capability?
_
The answers map to one of three paths:
EXTEND (recommended for ~50% of installed base)
You have meaningful digital twin assets, VE works for current workflows, but you need new capability — AI-augmented agents over your VE data, modern web/AR/VR viewers, custom Python operations for emerging business needs, or digital thread connections to PLM and data platforms. You're not leaving VE. You're making it do more.
MODERNISE (recommended for ~30% of installed base)
You're committed to VE for the next 3-5 years. The platform itself is working, but everything around it is showing its age. Cloud-host the on-prem deployment. Refresh ECC integrations to S/4HANA-native patterns. Replace legacy custom code with modern equivalents. Add support for newer CAD formats. You're keeping VE at the core but modernising its environment.
MIGRATE (recommended for ~20% of installed base)
VE is genuinely no longer the right fit — usually because business direction has shifted, internal capability has eroded, or strategic mandates require a cloud-native platform. A planned, phased migration to SAP EPD, a third-party visualisation platform, or a custom modern stack — without losing the assets and process maturity already built. Migration here is a deliberate choice, not a default.
Architecture Services
Common questions
Ready to fix your SAP Visual Enterprise architecture?
Schedule a 30-minute call to discuss your specific requirements and see if we're a good fit for your project.