SaaS-native with no capture infrastructure to run
Core Capture operates as a SaaS service. Programs do not stand up scanning servers or classification engines on-prem.
OpenText • Process automation
OpenText Core Capture
Core Capture is the SaaS capture product for departmental scope and AI-classified ingestion, OCR, and direct release into Content Management. Merito tunes classification models against your real document mix.
Merito sells OpenText Core Capture and delivers SaaS capture for departmental volumes and AI classification, OCR, and direct handoff into Core Content Management with faster deployment than the full Capture platform.
- Best for
- Departmental leaders automating single document flows, Mid-market AP, HR, or customer service teams adopting IDP, IT leaders modernizing off aging on-prem capture tools
- Hosting
- SaaS
- Time to value
- Single departmental capture process live in as little as one week. First departmental process live in two to three months. Multi-department adoption in four to six months.
- Security posture
- SOC 2 Type II, ISO 27001, GDPR
- Last reviewed
- 2026-04-26
What it is
OpenText Core Capture in the enterprise stack
OpenText Core Capture is the SaaS capture product for departmental and mid-market programs. It provides AI-driven classification, OCR, and direct handoff into the OpenText Content catalog without the operational overhead of a full Capture deployment. Programs that want IDP capabilities without running capture infrastructure on-prem pick Core.
Core Capture shares the Content catalog's governance patterns. Captured documents arrive in Content Management or Core Content Management with retention tags, permission inheritance, and audit trails already applied. The capture-to-content handoff is not a custom integration; it is a native flow.
The trade-off against the full Capture product is scope. Core is sized for departmental volumes and SaaS-native operations. Programs with enterprise production capture operations, heavy custom-rule extraction, or specific on-prem regulatory requirements still run Capture. Core could be the right call when SaaS fit and faster time-to-value matter more than maximum scale.
Ideal use cases
- Departmental AP, HR, or customer service document capture
- Mid-market IDP rollouts with SaaS operational posture
- SaaS-native capture programs feeding Core Content Management
- Faster time-to-value alternative to full Capture where scope fits
- Organizations transitioning off legacy on-prem scanning tools
What it is best at
Where OpenText Core Capture earns its seat
Native handoff into Content Management
Captured documents arrive in Content Management or Core Content Management with retention, permissions, and audit applied. No custom integration needed.
AI classification out of the box
Machine-learned classification ships with the product, tuned through training against customer content rather than configured rule by rule.
Core capabilities
OpenText Core Capture capabilities, grouped by outcome
Ingestion and OCR
SaaS ingestion with high-quality OCR for common document types.
Multi-source ingestion
Email, direct upload, scanner, and API ingestion supported.
Multi-language OCR
OCR with multi-language support for international programs.
Image pre-processing
Rotation, skew correction, and quality normalization before OCR.
AI classification and extraction
Machine-learned classification and extraction for mid-market diversity.
Automatic classification
Documents classified by type through machine-learned models.
Field extraction
Key field extraction for downstream business system consumption.
Human review queues
Exception workflows for low-confidence classifications and extractions.
Content catalog handoff
Native release into the OpenText Content catalog with governance applied.
Content Management release
Direct release into Content Management or Core Content Management.
Retention applied on ingest
Retention tags and classifications applied as documents enter the repository.
Audit trail continuity
Capture activity and release events logged into the same audit trail as the downstream repository.
Where it fits in the stack
How OpenText Core Capture connects to the rest of your landscape
OpenText Content catalog (native)
Native- OpenText Content ManagementNative release with retention and permissions applied.
- OpenText Core Content ManagementNative release for mid-market content programs.
- OpenText Content AviatorCaptured documents available to Aviator grounded AI immediately after release.
Ingestion channels (certified)
Certified- Email (Outlook, Gmail)Direct ingestion from email for departmental document flows.
- Scanner fleetsDirect-to-Core-Capture scanning from departmental MFD fleets.
Custom (custom)
Custom- Customer business applicationsAPI release into customer-built departmental business applications.
Deployment and implementation
How it rolls out
- Hosting
- SaaS (North America, EMEA, APJ)
- Implementation complexity
- Moderate
- Typical time to value
- Single departmental capture process live in as little as one week. First departmental process live in two to three months. Multi-department adoption in four to six months.
- Prerequisites
- Named departmental process owner
- Document-type scope agreed
- Downstream repository (Content Management or Core Content Management) identified
- Volume projections for the first year
- What Merito usually handles
- Merito handles Core Capture tenant setup, process design, classification model training against customer content, and release configuration into the target content repository.
Licensing and packaging
How it is bought
- Model
- Subscription
- What to expect
- OpenText Core Capture is subscription-licensed with packaging keyed to document volume, user seats (operators and reviewers), and ingestion channels. Pricing is positioned below the full Capture product for departmental scope. Merito sells Core Capture alongside the process design and integration work that realizes the faster time-to-value.
- Editions and modules
Core Capture standard
SaaS capture with AI classification and release into the Content catalog.
Best for: Departmental and mid-market capture programs.
- Common expansion areas
- Additional document volume tiers
- Content Cloud for Microsoft 365 for Microsoft-anchored release patterns
- Content Aviator for AI retrieval after release
- Managed Services for ongoing operations
- Transition to full Capture if scope outgrows Core
Merito services
How Merito helps you win with OpenText Core Capture
Merito sells licenses and the delivery work around them. Pick the service that matches where you are in the lifecycle.
01
Core Capture Rollout
Process design, classification model training, release configuration, and adoption.
Explore service02Upgrade and Migration
Migration from legacy departmental scanning tools into Core Capture.
Explore service03Premium Support
Named engineer, priority SLAs, and release-time coverage for Core Capture in production.
Explore service04Managed Services
Long-term run support for Core Capture sized to departmental operations.
Explore service05Training and Enablement
Role-based training for operators, reviewers, and administrators.
Explore service06Staff Augmentation
Merito-placed capture analysts and departmental process specialists.
Explore serviceCore Capture licensing
Buy Core Capture from the partner that sizes the rollout to the actual scope.
Merito sells OpenText Core Capture and delivers the departmental process design, AI classification tuning, and native release into the Content catalog that turn SaaS capture into measurable lift.
Merito point of view
Core Capture could be the right answer when scope is departmental. For enterprise production, buy the full Capture.
Merito has seen customers try to run enterprise production AP through Core Capture and outgrow the product. Core is excellent at departmental scope and specifically positioned below the full Capture product for a reason. Enterprise programs with heavy rule-based extraction, specific on-prem needs, or peak-event production volumes belong on Capture.
For mid-market programs and departmental flows inside larger enterprises, Core Capture could be the right shape. SaaS posture, AI classification out of the box, and native release into Core Content Management mean the program goes live faster with less operational overhead.
The upgrade path from Core Capture to full Capture is supported; customers whose scope grows can transition. Merito designs the Core deployment with upgrade-readiness in mind so the transition is smooth rather than a re-platform.
What buyers usually underestimate
- Selecting Core Capture for enterprise production volumes better served by full Capture.
- Skipping classification model training and expecting generic output.
- Not designing the downstream process redesign that makes capture pay off.
- Running Core Capture without release into a Content catalog product.
- Treating Core Capture as a scanning tool instead of an IDP platform.
Related from Merito
Continue exploring OpenText Core Capture on Merito
Related solutions
Related services
Related products
- OpenText CaptureEnterprise edition for high-volume production capture.
- OpenText Core Content ManagementSaaS content destination for captured departmental documents.
- OpenText Content ManagementFull enterprise content platform for customers that grow beyond Core.
- OpenText Content AviatorGrounded AI over captured content after release.
- OpenText (vendor portfolio)OpenText hub and the full DevOps and Content catalogs.
Frequently Asked Questions
OpenText Core Capture FAQs
Consultation request
Talk to Merito about OpenText Core Capture
Share the departmental flow you want to capture and the Content repository you want documents to land in. A Merito Core Capture specialist follows up within one business day.
SaaS posture
No capture servers to run
Core Capture operates as a SaaS service so departmental programs skip infrastructure setup.
Native release
Governance applied on ingest
Documents enter Content Management with retention and permissions already in place.
Next step
Pick one department. Train the model. Measure the lift.
A Merito Core Capture engagement starts with one departmental flow, trains classification against real content, and measures improvement before expanding.