The Trusted Solution for Migrating Content Into or Out of FileNet
Moving the documents is the easy part.
Organizations outgrow their legacy systems, but moving decades of content to a new platform isn't as simple as transferring documents. The real challenge is making sure everything associated with those documents comes along with them.
Annotations may need to be converted to different formats. Version histories and original entry dates must be preserved. Document classes, security permissions, and workflows need to be mapped to the new system. Legacy image formats may also require conversion.
If these details aren't handled correctly, documents may make it to the new system, but important information and functionality can be lost along the way.
A proven migration utility, operated by the expert team who built it.
DASmigrate isn't a 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 or target systems, not shipped as a one-size default.
- Run by a DAS developer who has 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
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.
The question to ask any migration vendor: what happens to the documents that fail?
Not every item may move successfully on the first attempt. Source files may be corrupt, documents may be locked, records may be subject to retention holds, or properties in the source system may not exist in the destination. What matters is knowing what didn't migrate, why it failed, and what needs to happen to resolve it.
Without that visibility, it's difficult to confirm that a migration is complete.
DASmigrate logs migration failures with details to help identify and resolve issues. Subsequent delta passes can retry failed items and pick up content created or modified since the previous run. The results can then be reconciled against the source system to account for what migrated and what still needs attention.
DASmigrate isn't theoretical.
These are real routes we've run, not a list of what the tool supports
Featured Result
Over 600 M+
Documents Migrated
Proven across enterprise migrations. Real volume. Real outcomes.
FileNet Image Services
FileNet Content Manager
FileNet
Azure Blob Storage
FileNet
M-Files
FileNet
AWS S3
FileNet
Local file share
OpenText COOL
FileNet Content Manager
FileNet P8
Microsoft SharePoint
Microsoft SharePoint
FileNet Content Manager
FileNet
line-of-business apps
FileNet
Salesforce
FileNet
Box
FileNet
SoftExpert
FileNet
.webp)
V3elocity (Majesco)
You're hiring the migration, not licensing the tool.
Four steps, and you know what happens next at every one.
01
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.
02
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.
03
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.
04
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.
Questions we answer
Both. Most migration tools on the market only move content out of FileNet. 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.
No. DASmigrate is our proprietary utility and DAS configures and operates it for your migration on your system. You're not licensing software, installing it, and then discovering what it doesn't handle about your environment. 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, OpenText, OnBase, DocStar, local file systems, and more. 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-business applications that aren't ECM platforms.
They are converted and repositioned, not dropped. Annotation formats differ between systems, so DASmigrate converts XFDF and other formats and places the annotation content correctly on the page. When output is converted to PDF, it accounts for image DPI, which keeps placement accurate instead of drifting. Annotations are one of the most 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 and properties. 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 as an option.
They are logged with enough detail to resolve, then re-run in a delta pass. Every large migration produces items that won't move on the first attempt: corrupt source files, locked documents, records under retention hold, properties with no equivalent in the target. Delta passes also pick up anything created or modified after the initial run started, so the final reconciliation matches the source.
Yes, along with BMP, JPEG, PNG, and GIF. Legacy FileNet environments frequently store proprietary single-page TIFF files that most modern systems can't use well. Converting during export means it's part of the migration rather than a separate remediation project afterward.
DASmigrate detects the interruption and resumes from where it stopped rather than restarting. On a migration of several million documents, restarting after a network disruption can cost weeks. This is one of the specific problems the tool was built to solve.
Migration timelines depend on the amount of content, the complexity of the source environment, the target platform, and how much metadata, version history, and other information needs to be preserved. A straightforward migration may take a few weeks to a month, while larger projects involving legacy systems, complex mappings, or multiple repositories can take several months or longer.
DAS works with each organization to define the scope, identify potential challenges, and establish a realistic timeline before migration begins.
Yes. CMOD migrations are among the least well-served in the market and among the most common reasons organizations call us. DAS has deep CMOD experience alongside FileNet, so the same team handles the source system and the target.
