IBM & Tungsten Automation Partner and Primary Support Provider

Modernize your content platform without starting over.

Your FileNet, Datacap, CMOD, and Tungsten Capture systems still run the business. We upgrade, integrate, and modernize them, so the processes, integrations, and content you have spent years building come with you.

Schedule a Platform Health Assessment

Considering a Move Up from Capture to TotalAgility?

The date on the calendar

IBM FileNet Content Manager 5.5.x reaches end of support on September 30, 2026.

That is IBM's published date, not an estimate. 5.5.x moves to Extended Support, which is a paid, time-boxed arrangement. 

If you are running 5.5.x today, you have a decision to make: Upgrade, or start planning a longer transition. Choosing by default is the one that costs the most.

What is actually driving this

Platforms rarely fail. They just stop being supportable.

Legacy ECM and Capture environments do not break on a Tuesday. They get harder to staff, harder to patch, and harder to connect, until one day a vendor date or an audit finding turns a slow problem into a scheduled one. By then the options are narrower and more expensive than they were a year earlier.

A vendor end-of-support date with your version on it
Aging infrastructure and accumulated technical debt
A cloud mandate that your content platform is blocking
An AI initiative that stalls once it meets your actual content

Cybersecurity and compliance requirements the platform cannot meet as configured
Performance and scalability limits users have started to notice
Custom applications and integrations nobody wants to touch
Business continuity and disaster recovery gaps found during a review

Our position

We modernize the platform you have. We do not sell you a replacement for it.

Most of this market wants you to leave. Migration vendors point you at SharePoint. Replacement vendors point you at their own SaaS. The grass isn't always greener. A lesson we've learned through decades of experience. Every one of those recommendations restarts a decade of configuration, integration, and user training you already paid for. 

Your document classes, security model, retention rules, workflows, and the line-of-business integrations wired into them represent years of institutional knowledge. Modernization should carry those forward, not discard them.

Upgrade in place where the version path supports it.
Re-platform to cloud or hybrid when the business case is real, not because it is fashionable.
Rebuild only the pieces that cannot come with you, and tell you which those are up front.

Why organizations trust DAS with the platform they cannot afford to lose.

30+

years modernizing enterprise content, founded 1991

60+

platform certifications

350+

successful implementations

Scope

Seven ways a platform gets modernized, and we do all of them.

Most engagements start with one and expand into two or three. The assessment tells you which ones you actually need.

Platform upgrades, off end-of-life versions

Move from an unsupported release to a current one while your configurations, workflows, security models, and integrations survive the trip.

Platform assessments and health checks

A documented read on what you are running: versions, infrastructure, customizations, integration dependencies, content volume, and the risks attached to each. You get the findings whether or not you hire us for the work.

Application and integration modernization

The custom applications, APIs, and point-to-point integrations built on top of your content platform are usually the reason an upgrade stalls. We replace brittle point-to-point connections with modern APIs and bring client-centric applications forward without interrupting the business processes that depend on them.

Architecture review and optimization

Evaluate the deployment you actually have against the one you need: performance, scalability, resiliency, and the maintenance burden your team carries. Often the fastest win is not a new platform, it is a corrected architecture on the current one.

Metadata and content lifecycle modernization

Retention, records management, classification, and metadata quality. Unglamorous, and the thing that decides whether your compliance posture holds and whether AI can do anything useful with your content later.

Compliance and security modernization

Bring an aging platform up to current regulatory, cybersecurity, and records requirements without a full replacement. For public sector and regulated buyers this is frequently the event that funds the whole project.

Cloud migration and re-platforming

Move on-premise environments to private, public, or hybrid cloud when the case holds up. We run the migration with DASmigrate, our own utility, so content, metadata, annotations, and version history arrive intact.

See our content migration services

From where you are, to where it makes sense to go

Modernizing does not mean leaving FileNet.

IBM's own position is that Content Cortex is the natural evolution of FileNet Content Manager, Content Manager OnDemand, and Content Manager Enterprise Edition. So for most FileNet estates the destination is not a different vendor. It is a current version of what you already run, in the deployment model that fits.

There is one detail the vendor marketing tends to leave out, and we would rather you hear it from us: Content Cortex expects a recent FileNet foundation. On 5.5.x today, "no rip and replace" is true, but it is not free. You still need the version upgrade first. That upgrade is the service on this page, and knowing the sequence up front is what keeps a modernization project from stalling halfway.

From where you are

To where it makes sense to go

FileNet Content Manager 5.5.x, on-premise

A current, supported FileNet Content Manager release

Multiple repositories accumulated through mergers and acquisitions

A single consolidated repository, with the retired systems decommissioned

The prerequisite nobody sells

Your AI is only as good as your metadata.

Every AI initiative that touches enterprise content eventually hits the same wall. The models are fine. The content is the problem. Documents with no reliable classification, metadata that three different teams populated three different ways, retention rules that were never enforced, and four repositories that each hold a partial version of the truth. Fixing that is not an AI project. It is a modernization project, and it is the one that has to happen first. Getting your platform current, your metadata trustworthy, and your repositories consolidated is the first step toward AI, not the last.

Explore AI Enablement Services

Who we do this for

Modernization where the content is sensitive and the audit is real.

The platforms are similar everywhere. The constraints are not.

State and local government

Modernize records, case files, and permitting systems without moving sensitive content onto infrastructure you do not control, and with a documented trail for every decision.

Healthcare

Bring records and forms platforms current while patient content stays secure, compliant, and where your policies require it.

Financial services

Upgrade the systems holding statements, applications, and KYC files with retention and auditability intact throughout the transition.

Manufacturing and distribution

Modernize the document platforms behind supply chain, AP, and compliance so they connect to the systems that act on them.

Insurance

Consolidate the repositories that accumulate through acquisition, and retire the systems you are still paying to keep alive.

How an engagement runs

Five phases, and you know what happens next at every one.

Nothing runs at production scale until you have signed off on a pilot.

Assessment

We inventory what you actually run: versions, infrastructure, customizations, integrations, content volume, and the support status of every component. You get a written findings report and a real scope, whether or not you go forward with us.

FileNet Services

Strategy and roadmap

We build a phased plan tied to your budget cycle and your risk tolerance, sequencing the work so the pieces with a deadline get handled first. Decisions about what does not have a clean path forward get made here, with you, not discovered mid-project.

FileNet Services

Pilot/ Proof of Concept

We modernize a representative slice and you validate it against production. Configurations, permissions, integrations, performance. This is the gate, and nothing proceeds past it until you say so.

FileNet Services

Implementation

We execute at scale with the production load protected, whether that means upgrades, re-platforming, consolidation, or application modernization. Downtime windows are agreed in advance, not discovered.

FileNet Services

Validation and ongoing optimization

We verify performance, security, compliance, and functionality against the plan, then stay on for monitoring, tuning, and managed support. Modernization is a state you maintain, not a project you finish.

FileNet Services

Built for content you cannot afford to get wrong

Modernization that respects where your content has to stay.

Bringing a platform current does not mean moving your content somewhere new. We work on-premise or in your cloud, keep your compliance requirements in the design from the first architecture session, and treat retention and auditability as constraints rather than as things to reconcile afterward.

On-Premise or Cloud Deployments
Strict Data Residency Adherence
Records and Retention Continuity

FAQs

Questions we answer

IBM FileNet Content Manager 5.5.x reaches end of support on September 30, 2026, per IBM's published product lifecycle. FileNet Content Manager 5.6.x, which became generally available on June 28, 2024, has no end-of-support date published yet. If you are unsure which release you are on, that is the first thing our assessment establishes.

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Where to go next

Modernization touches everything. Here is what connects.

Content Migrations

IBM Content Cortex

DASmigrate

Systems Integration

AI Enablement

Where to go next

Start with an assessment, not a proposal.

We establish what you are running, what its support status is, and what your realistic options are. You get the findings report either way, our recommendations given your options, and a straight answer about how much time you actually have.

Schedule a Platform Health Assessment