Federal Partner · OpenText

OpenText for federal records — on the cloud path.

FCI is an authorized OpenText partner and the federal channel for the OpenText platform — Documentum, Content Cloud, Records Management, Aviator. Sold on GSA MAS, modernized to the cloud, benchmarked against the federal pricing band.

Talk to the OpenText team
Modernization economics

Modernize now, or pay to retrofit later.

The Partnership

FCI is the federal channel for the OpenText platform.

The OpenText platform is the world's leading information-management suite — Documentum, Content Cloud, Records Management, eDiscovery, Aviator. OpenText markets the platform. FCI lands it inside federal records and content programs. One firm carries the buy from GSA MAS through cloud migration and into the renewal.

Learn about the OpenText platform at opentext.com →

The OpenText stack

Everything FCI resells from the OpenText platform.

The OpenText suite is large. We've stacked it the way federal agencies actually adopt it — the anchors first, the strong supporting layer second, the long tail third. Every product is sold by FCI on GSA MAS and deployed against the agency's federal cloud posture.

Tier 1 · Anchors

The four products federal agencies buy first.

The records backbone — the platforms most federal OpenText programs are built on.
Documentum The federal ECM standard for decades. The records platform.
Content Cloud Cloud-native content services. Modern federal teams' default.
Records Management NARA-aligned schedules, retention, disposition. The compliance layer.
Aviator Generative AI on the federal record — in-boundary, cited, audited.
Tier 2 · Strong support

Where most federal records programs expand next.

Capture, governance, eDiscovery — the layer that operationalizes the anchor platforms.
Extended ECM Content in SAP, Salesforce, Microsoft 365, and federal LOB.
Intelligent Capture AI-driven federal forms, paperwork, and correspondence intake.
Axcelerate eDiscovery for FOIA, investigations, and litigation.
Information Governance Cloud Governance and disposition across the federal content estate.
Tier 3 · Long tail

Specialty SKUs federal programs reach for case-by-case.

Where the OpenText suite gets deep. FCI scopes these to the mission, not the catalog.
Insight Investigative analytics
Magellan Analytics & ML
Voltage SecureData Data-centric encryption
Captiva Heritage capture pipelines
Archive Long-term WORM storage
Legal Hold Defensible hold orchestration
FOIA Response Automated FOIA workflows
Forms Federal form intake
Identity (NetIQ) Federal identity & access
Core Signature Federal e-signature
Brava! Secure viewer / redaction
Migrate Records migration tooling
Why buy OpenText through FCI

There are other federal OpenText channels. Here's where FCI is different.

Five distinctions that hold up against the catalog resellers above us and the boutique systems integrators below us — anchored in federal records depth, not catalog breadth.

02 · Records-mandate fluency

NARA M-19-21, M-23-07, DoD 5015.2 — defensible on day one.

Records compliance isn't a downstream check; it's a design constraint. FCI brings the federal records policy fluency into the OpenText implementation — schedules, retention, disposition, audit posture — so the program holds at the next inspection.

03 · Cloud Editions migration experience

We've moved petabytes off legacy Documentum — without losing audit lineage.

Cloud Editions migration is the federal modernization story for the next 24 months. FCI has the runbook: assessment, custom-code remediation, records re-certification, and the lift to OpenText U.S. Federal Cloud with the agency's RM schedule intact.

04 · Federal-grade quality posture

The credentials a big partner has — in a small-business package.

ISO 9001 quality management. CMMC Level 1 certified. DCAA-compliant timekeeping. GSA MAS contract vehicle. Most small federal partners carry one or two of these. FCI carries all four — set-aside eligible where the acquisition allows it.

05 · Records-program specialized

Federal records practice, not federal catalog.

Concentrated in federal civilian, defense records, postal, and federal infrastructure — the missions whose records estates actually require Documentum-grade discipline. We don't carry 4,000 SKUs; we run the OpenText products federal records programs actually need.

Cloud migration · Modernization ROI

The defer-and-retrofit cost is the cost no one budgets for.

Federal Documentum environments cost more to retrofit for AI workloads after the fact than to modernize directly. The cheapest version of the work is the one done before the AI pilot lands on the records.

Three modernization paths

FCI structures the migration around total federal cost, not next-quarter ease.

The in-place upgrade is cheapest this fiscal year. The defer-and-retrofit path piles cost up across the AI deployment curve. The modernize-now path costs more upfront — and meaningfully less across three to five years.

  • Version is an AI-readiness signal. Modernization plans that target operational stability without targeting integration-surface modernization solve the wrong problem.
  • Content-model rationalization is load-bearing. Type-based models built for 2010 workflows don't support retrieval or agentic patterns without remediation.
  • Records-mandate alignment is the natural moment. Every modernization cycle is an opportunity to re-baseline against NARA's current expectations.
Defer-and-retrofit Highest TCO

Patch the legacy version. Retrofit for AI later as workloads arrive. Most expensive across the term — and the gap exposes the program to operational risk.

3-yr TCO · ~100% baseline
In-place upgrade Cheap now · costly later

Move CS 7.x → CS 16.x. Lowest disruption, preserves custom code, keeps RM certs intact. Doesn't deliver the AI-ready integration surface modern workloads require.

3-yr TCO · ~80% baseline
Pricing & ROI

The federal records buy has a market price. Here's where each path lands.

Three ways to buy OpenText for a federal records program. Same license at the bottom — very different all-in posture by the time the platform is in production. FCI sits in the middle for a reason.

Catalog Reseller
Large federal SKU channels
OpenText license on a federal vehicle
Fast quote, broad SKU catalog
Migration or implementation — separate integrator
Federal records-mandate fluency in the deal
Documentum estate diagnostic / version advisory
!Renewal advocacy — moves with the SKU, not the program
Federal all-in posture
$$$$$
License-only. Migration partner adds ~30–50% on top.
FCI Advisory
Boutique federal channel + records implementation
OpenText license on GSA MAS
Migration & implementation bundled — same firm, no handoff
NARA mandate fluency in the design, not a downstream check
Documentum estate diagnostic & modernization plan
Same firm to renewal · partner-attended
Small business · set-aside eligible
Federal all-in posture
$$$$$
Bundled, federal-market priced — license, migration, and lifecycle in one engagement.
Large SI
Big-bench federal integrators
OpenText license + migration
Deep bench across most federal categories
!Premium-loaded labor rates — federal price band exceeded
!Records mandate often a separate work stream
!Multi-year LOE — lock-in often baked into the stack
Small-business set-aside eligibility
Federal all-in posture
$$$$$
Premium rates · multi-year LOE · proprietary lift on top of the platform.
FCI lands inside the federal market price band — license, migration, and records lifecycle from one accountable firm at a total cost that typically sits between the catalog reseller's downstream all-in and a large-SI engagement. You don't pay a markup for the handoff and you don't pay a premium for the brand. Cost ranges shown qualitatively; FCI provides specific federal pricing benchmarks against the OpenText platform during the engagement.
From the field

A program we run.

One pattern FCI delivers across federal OpenText programs — anonymized at the engagement level. The structure repeats across mission programs.

A program we run
Cloud Editions
Moving federal records off legacy Documentum onto OpenText U.S. Federal Cloud — schedules, audit lineage, and AI-readiness preserved.
FCI · OpenText Authorized Partner

"FCI modernizes federal Documentum environments to OpenText Cloud Editions on the agency's timeline — schedule import, content-model rationalization, custom-code remediation, records re-certification, audit lineage preserved. One firm handles the license, the migration, and the records program — and stays through the AI workloads that arrive next."

— From the FCI OpenText practice

Other federal partners.

View all partners
Boomi
Boomi
Microsoft
Microsoft
Google Cloud
Google Cloud
ServiceNow
ServiceNow
Cisco
Cisco
Appian
Appian
Datadog
Datadog

Modernize federal records to the cloud.

Tell us the agency, the Documentum version, the records schedule, and the AI roadmap — we'll come back with the product mix, the migration path, the records re-certification plan, and the price.