Table of contents
With modernization already underway and a major platform upgrade ahead, the next step was to replace the remaining low-level OScript connectors - reducing technical debt and operational risk without disrupting the business.
The challenge
The customer's on-premises environment included more than 30 integrations, 50+ Business Object types and over 10 years of customizations.
A key area of complexity was the integration layer. Many integrations relied on custom SPI adapter connectors developed in OScript to create Business Workspaces and synchronize taxonomy and metadata with external systems. The objective was to modernize these legacy integration channels while preserving what was already working.
This meant:
- Supporting the planned upgrade from Content Management 22.2 to 25.4
- Removing technical debt from low-level custom connectors
- Keeping the existing data model and repository structures
- Maintaining dependencies with connected systems
- Minimizing downtime
- Preserving the existing user experience
For business users, the modernization had to be practically invisible: everything should simply continue to work.
An inspection-driven approach
Because the customer had strong internal technical expertise, comprehensive system and source access, and clear ownership of its architecture, we could work directly with its IT team to inspect the existing implementation in detail.
Rather than redesigning an already mature ecosystem, we focused on optimizing the path to a known modernization target. We started with representative use cases, validated the proposed approach, refined it based on real results and then repeated the process across the integration landscape.
Validate. Learn. Repeat. This allowed us to address the areas with the greatest complexity and impact first, before scaling the approach.
From low-level connectors to a repeatable integration standard
The core of the project was the modernization of 15 legacy connectors, replacing low-level OScript implementations with a higher-level integration approach based on Content Management for Everything, a Module Suite functionality.
Content Management for Everything provides a standardized framework for connecting any external application with OpenText Content Management, enabling business objects, documents, metadata and processes to stay synchronized across systems.
In this case, it allowed us to modernize how external data enters Content Management and drives the creation and synchronization of Business Workspaces, metadata and taxonomy.
Modernize the path, keep the data
One of the most important findings during the analysis was that the underlying data model did not need to change. The customer's 50+ Business Object types were already compatible with the new integration approach, and repository structures remained valid.
As a result, the modernization could focus on the integration channels rather than the data itself.
No structural data migration or major reengineering was required. Existing data could remain in place while the new integration model was introduced progressively.
A resilient background process handled the required transformations in parallel, creating Business Objects and relationships, synchronizing taxonomy, and applying the appropriate roles and permissions while normal business operations continued.
The result
The project transformed a complex legacy integration layer into a more standardized and maintainable architecture while protecting business continuity.
Key benefits included:
- Reduced technical debt by decommissioning low-level OScript connectors
- Lower modernization risk through incremental validation and deployment
- Minimal business disruption, with the existing user experience preserved
- No major data migration, retaining established data models and repository structures
- Greater maintainability through a repeatable integration standard
- Improved upgrade readiness for the customer's evolving OpenText environment
- Greater internal ownership, with the customer's IT team building knowledge throughout the project
Modernization therefore became part of the customer's ongoing approach to risk and TCO mitigation.
What comes next
With the integration foundation modernized, the customer can continue simplifying and extending its ecosystem.
The roadmap includes new integrations and functionality, AI-assisted capabilities, and the progressive modernization of more than 800 WebReports, Step Views, dashboards, jobs, custom views and custom actions.
