DASmigrate

The Trusted Solution for Migrating Content Into or Out of FileNet

DASmigrate is our proprietary migration utility, built and refined over 20 years of FileNet work. Annotations, version history, metadata, permissions, and original entry dates arrive intact. Our team runs it, so you're not buying software and hoping it fits.

Schedule a FileNet Data Migration Consultation

See our content migration services

How FileNet migrations go wrong

Moving the documents is the easy part.

Every organization eventually faces the same question: what do we do with decades of content sitting in a system we've outgrown? Most teams assume the hard part is volume. It isn't. The hard part is everything attached to the documents. 

To satisfy business requirements, annotations may need to be converted between formats . Versions have to keep their original entry dates, not the date you ran the migration. Document classes, security models, and workflows have to be mapped from one system's logic into another's. Image formats have to be reconciled.

Miss any of it and you haven't migrated your content, you've relocated it and broken it.

Tool and team, not one or the other

A proven migration utility, operated by the expert team who built it.

DASmigrate isn't a one-off service engagement built from a blank page, and it isn't off-the-shelf software you install and run yourself. It is a purpose-built migration utility that the DAS team configures and operates inside your environment, carrying logic that has already been proven across some of the largest content migrations we've completed. 

That matters because the two usual options both fail the same way. Buy a generic tool and you inherit whatever its authors didn't anticipate about FileNet. Hire a services team with no tooling and you pay them to rediscover the same edge cases we solved years ago. DASmigrate is the third option.

Configured for your source and target systems, not shipped as a one-size default.
Run by a DAS developer who have completed these migrations before.
Continuously refined. Every migration we complete makes the next one better.

Why DASmigrate Delivers Better Migrations

99.5%

data integrity maintained

85%

reduction in migration time

600M+

documents migrated

20+

years of FileNet experience

Capabilities

Purpose-built for real-world migrations

Every scenario below is one we've run in production, not a spec sheet of what the tool could theoretically handle.

Annotations that land where they belong

DASmigrate converts XFDF and other formats and places annotation content correctly on every page. When output converts to PDF, it accounts for image DPI so placement stays accurate rather than drifting.

Full version history, original dates intact

Every version exports with its change history and lifecycle. Each can carry different content and properties, and the entry date reflects the document's original entry into the source system, not the day you migrated it.

Image conversion during export

Convert TIFF, BMP, JPEG, PNG, and GIF to PDF as part of the migration. FileNet's proprietary single-page TIFF is one of the most common reasons a migration stalls, and this handles it in flight.

Metadata to and from anywhere

Migrate document metadata to and from CSV, XML, JSON, or a database, so content can land in a line-of-business application that isn't an ECM platform at all.

Interrupted transfers pick up where they stopped

If a network disruption stops a migration mid-process, DASmigrate detects it and resumes from the point of failure. It doesn't start over. On a multi-million document migration, that difference is measured in weeks.

Throughput without touching production

DASmigrate supports multiple concurrent instances, so throughput scales up when you need it and dials back during business hours. Your production systems stay under an appropriate load while the migration runs.

WHAT NOBODY TELLS YOU ABOUT MIGRATION DAY

The question to ask any migration vendor: what happens to the documents that fail?

Every large migration produces items that won't move. Corrupt source files, documents locked by a user, records with retention holds, objects whose properties don't exist in the target model. The difference between a migration you can sign off on and one you can't is whether those items are found, logged in enough detail to fix, and re-run.
 
DASmigrate logs every failure with the detail needed to resolve it, and delta passes move items that failed the first time along with anything created or modified since the run began. You reconcile against the source and know the count, not a guess.

Migrations We Have Completed

DASmigrate isn't theoretical.

These are real routes we've run, not a list of what the tool supports

You're hiring the migration, not licensing the tool.

Four steps, and you know what happens next at every one.

Quick Consultation

We inventory your source system: volume, document classes, annotation formats, version depth, security models, and the integrations that depend on it. We assess and then provide a quote.

Mapping and configuration

We map document classes, metadata, and permissions from source to target, then configure DASmigrate against that map. Decisions about what doesn't have a clean equivalent get made here, with you, not discovered mid-migration.

Pilot

We migrate a representative slice and you validate it against the source. Annotations, versions, dates, permissions. Nothing runs at full volume until the pilot is signed off.

Full migration and
reconciliation

We run at volume with concurrent instances tuned to your production load, then reconcile counts against the source and run delta passes for anything that failed or changed. You close the project with a number, not an assumption.

FAQs

Questions we answer

Both. Most migration tools on the market only move content out of FileNet, usually to SharePoint or Microsoft 365. DASmigrate runs in both directions. We've migrated SharePoint and OpenText content into FileNet Content Manager, and FileNet content out to SharePoint, M-Files, AWS S3, Azure, and line-of-business applications.

Neither, exactly, and the difference matters. DASmigrate is our proprietary utility and DAS configures and operates itfor your migration. You're not licensing software, installing it, and then discovering what it doesn't handle about yourenvironment. You're hiring a migration that happens to run on a tool we've spent years refining.

IBM FileNet Content Manager and P8, FileNet Image Services, IBM Content Manager OnDemand (CMOD), SharePoint,OpenText, M-Files, DocStar, local file systems, and cloud storage including AWS, Azure, Google Cloud, and Oracle.Metadata can move to and from CSV, XML, JSON, or a database, which is how content reaches line-of-businessapplications that aren't ECM platforms.

They are converted and repositioned, not dropped. Annotation formats differ between systems, so DASmigrateconverts XFDF and other formats and places the annotation content correctly on the page. When output is convertedto PDF, it accounts for image DPI, which keeps placement accurate instead of drifting. Annotations are one of themost common things a generic migration tool loses.

Yes. Every version exports with its full change history and lifecycle, and each version keeps its own content andproperties. The entry date reflects when the document first entered the source system, not the date of migration.Getting this wrong is a compliance problem, not a cosmetic one, which is why it's handled automatically rather than asan option.

They are logged with enough detail to resolve, then re-run in a delta pass. Every large migration produces items thatwon't move on the first attempt: corrupt source files, locked documents, records under retention hold, properties withno equivalent in the target. Delta passes also pick up anything created or modified after the initial run started, so thefinal reconciliation matches the source.

Yes, along with BMP, JPEG, PNG, and GIF. Legacy FileNet environments frequently store proprietary single-page TIFFfiles that most modern systems can't use well. Converting during export means it's part of the migration rather than aseparate remediation project afterward.

DASmigrate detects the interruption and resumes from where it stopped rather than restarting. On a migration ofseveral million documents, restarting after a network disruption can cost weeks. This is one of the specific problemsthe tool was built to solve.

It doesn't have to. DASmigrate runs multiple concurrent instances, so throughput can scale up during off-hours anddial back during the business day. We tune the concurrency to your environment during the pilot, before anything runsat volume.

Yes. CMOD migrations are among the least well-served in the market and among the most common reasonsorganizations call us. DAS has deep CMOD experience alongside FileNet, so the same team handles the sourcesystem and the target.

Start with a discussion, not a proposal.

Before anyone talks about scope or timeline, we inventory what you actually have: volume, document classes, annotation formats, version depth, and the integrations that depend on your current system.