Managed services for OpenText
Not every estate needs a programme wrapped around it. Most need someone specialist keeping an eye on the platform, the database underneath it and the day-to-day running.
Close enough to the estate to catch things before they surface, senior-led, with one team and one SLA. OpenText depth, priced for operations, for a predictable monthly cost.
15 checks you can run yourself. No form, no email, nothing to sign up for.
At a glance
Critical-incident response
At every tier, not only the premium one.
24×7×365
One SLA, one team
Platform, database and business administration.
3 layers
Combined experience
OpenText ECM, Oracle, SQL Server and enterprise infrastructure.
35+ yrs
Senior-led, alongside your teamWhat goes wrong
OpenText holds the documents and records wrapped around your most important processes: invoices matched to purchase orders, contracts tied to customers, records held for a retention period. Most of the people who depend on it never see OpenText at all. They reach it through SAP, Salesforce or Microsoft 365.
So the first sign of a problem is rarely “OpenText is down”. It is:
Recognise any of these? Run the 15 checks on your own estate.
Already know something is wrong? Talk it through with us.
The usual causes
What we do
Nuca keeps production OpenText estates running as an ongoing managed service. Not a project, not an implementation. The day-to-day run: monitoring, patching, incident response, database administration, upgrade readiness and change control, under one SLA with one team accountable.
We do not do implementations, migrations or custom development. We run what is already live. If someone else built it, they keep that relationship.
Where an estate is short-handed right now, we can cover it directly. Interim cover keeps the platform stable while you recruit, starting in days and running month to month.
Working alongside your team
We relieve your specialists of the operational load. We do not replace them. Your people keep their knowledge and their standing and get the work only they can do, while we keep the platform running underneath. The internal expert usually ends up our strongest advocate, because they finally get to take a holiday.
Three layers, one team
An OpenText estate has three layers, and the hardest problems fall across the boundaries between them. We cover all three, so an incident is diagnosed once rather than handed between vendors.
Layer one
Content Server, OTDS, Archive Server, Records Management, xECM connectors, Extended ECM. Monitoring, patching, upgrades, performance, incident response and change control.
Layer two
Oracle and Microsoft SQL Server, run specifically under OpenText workloads. Backup and recovery, high availability, performance and capacity planning.
Layer three
Users, permissions, categories, workflows and records-management policy, with our specialist partners. The functional layer most technical managed services do not touch.
The service, at three depths
Most estates join at Tier I and grow into the depth they need. Every tier carries the same 24×7×365 response to critical incidents.
Tier I
The platform and the database, production-stable, with 24×7×365 cover for critical incidents. A complete service in its own right.
Tier II
Everything in Tier I, plus the business-administration layer, delivered with our specialist partners.
Tier III
Everything in Tier II, plus upgrades, migrations and a named Technical Account Manager.
Most engagements start smaller than a tier, with interim cover or a single estate review.
Common questions
Next step
No form, no gate. The checklist is written to be run without us.