Modules, integrations, upgrade paths, and migration strategy for HPSM — through its Peregrine → HP → HPE → Micro Focus → OpenText lineage.
HPSM (Service Manager (HPSM)) — currently branded as OpenText Service Manager (HPSM) after passing through the HP → HPE → Micro Focus → OpenText lineage — remains mission-critical infrastructure in many enterprises. For teams deep in HPSM, technical decisions matter more than strategic labels.
This page details the HPSM modules, integration surfaces, and upgrade paths we work across. For a broader overview of our practice, see the Service Manager Tools page.
Every HPSM module below has been delivered in production by our team. No theoretical work.
Deep expertise across the module family.
Categorization, routing, SLM integration, self-service.
Root cause, known errors, workaround management.
CAB workflows, change assessments, integrations with monitoring.
uCMDB integration, class model management, discovery reconciliation.
SLA definition, tracking, operational and executive reporting.
Catalog, workflow, task management, integration to fulfillment.
Self-service portal customization, branding, mobile experience.
New processes on the platform — matching your operational reality.
Directory-driven user provisioning and authentication.
Event correlation and enrichment from OM into Service Manager.
Cross-domain event and topology from OpsBridge.
Configuration data flow with reconciliation and health checks.
Version upgrades with test cycles, regression coverage, rollback playbooks.
Data mapping, workflow preservation, dual-run coexistence support.
Ongoing platform admin, patching, enhancement backlog.
Instance audit, module inventory, integration map, upgrade or migration analysis.
Target-state modeled in a dev instance — forms, workflows, integrations, data.
Configuration with unit tests and code review discipline.
UAT scripts, regression, performance, security.
Cutover, hypercare, comms, training.
Ongoing admin and enhancement — same team.
Match the level to platform criticality.
Bring an aging instance to a currently-supported version.
Modernize the self-service portal — mobile, branded, useful.
Replace fragile point-to-point integrations with resilient patterns.
Reconcile uCMDB and restore its role as a trusted source.
Phased migration off Service Manager with data preservation.
Take over daily platform admin so the internal team focuses on outcomes.
Yes — separate but related product. Different architecture, similar processes. We deliver on both.
Yes. This is one of our most common engagements. Phased, with dual-run coexistence if needed.
OpenText continues to invest in the product family. We stay current on the roadmap and can advise on your options.
Yes. Query tuning, index review, web tier optimization, background scheduler cleanup.
Test-driven — regression suite runs before, during, and after. Rollback plan documented up front.
Yes. Service Manager still runs in many federal shops. Familiar posture.
Reach out — we get back within 1 business day.
