Conversion and Migration Services

You will greatly benefit from our 30 Plus Years in Data Capture and OCR.

UFC’s Document Migration Services

UFC, Inc. has a vast amount of experience in document migrations from one ECM (enterprise content management) platform to another, or just to a database or file system while you determine the next steps. Our professional services staff has engineers that are intimately familiar with a variety of enterprise content management systems and we understand how to quickly convert the content to other platforms. Our team follows a structured migration process that is proven and reliable. No doubt, a document conversion project is a serious consulting engagement. Rather than send the customary “AOC” (army of consultants) preferred by our competitors, you will work with one skilled developer during the entire migration process. UFC^® has successfully migrated many millions of documents.

Consider How UFC^® Can Complete Your Migration Project

We can:

Migrate documents and metadata out of FileNet Content Services
Migrate out of or into Oracle Web Center Content or Oracle IPM
Migrate out of FileNet Image Services to FileNet P8 or any other ECM
Migrate out of any other ECM as long as your supply the ECM API’s

A Proven Solution

UFC^® has successfully migrated tens of millions of documents. We developed this process over a ten year period and would be glad to provide you references from our customers. We will work with you to develop and document a methodology, and then work with you to conduct the migration.

Some of Our Conversion Experience:

Multinational oil and gas services company in Houston: FileNet Image Services to FileNet P8, 6 M documents migrated during 2007.
Multinational oil and gas services company in Houston: FileNet Image Services to FileNet P8, 2.5 M documents migrated during 2009.
Multinational gas services company in South Dakota: FileNet Image Manager to FileNet P8, 6 M documents during 2010.
Regional banking customer in the US: FileNet Content Services to file directory system and XML awaiting new repository. This job is currently is process, estimated at 4.5M+ documents.

Consider what could go wrong and please don’t underestimate the scope of any migration project.

Consider What Could Go Wrong

Consider the following scenario. Five years after you did your migration from FileNet Content Services to Oracle Web Center Content a user contacted the help desk saying that they were missing a document from their legal documents class. They explained that they were responding to a litigation request for a document that was created around the same time as your migration. To your horror you realize that this document was stored on the old Content Services system during the critical transition period to the Oracle platform but was never migrated off of FileNet. That wouldn’t be a problem because you kept a backup. But it’s been five years since you loaded Content Services on a server and the backup you created wasn’t a virtual machine (why not?). So now you will need to load Content Services but it’s not support on Windows Server 2016 (or whatever) so you will need to located a copy of Windows Server 2008. But there’s another problem. You no longer have a support contract for your FileNet system, so now you are on your own. Can you get it going and find the missing documents? Did you save the documents in a generation data group such that nothing got overwritten?

Your boss came to you with some questions, since the person that did the original migration left the company three years ago. Did you keep a record or all documents that were moved, when they were moved, and was there any sort of validation performed to verify that they were moved? What was your process for migrating documents during the cut to the new ECM? How were backups done during the transition period, and why wasn’t a virtual machine created of the server? Are you willing to testify on this case in court next month if certain documents cannot be located? Are there any copies of the paper documents in existence, and what about the related documents that were originally linked in the metadata?

UFC’s Proven Methodology and Experience Will Help Your Migration to Succeed

We developed our methodology over the past ten years and have a proven track record in delivering successful migration projects for large firms around the county. Our process is as follows:

We do a comprehensive assessment and create a design document for how the project will be delivered. This includes a plan for migration of metadata, images, linked documents, linked images, document URL’s, and outside database or ERP links (did you consider this?) and database connections.
We license and install a Quillix capture system on a virtual server, and generally this is hosted at your location with VPN access for our developers. If you are thinking about staying with Quillix capture we can install this on a development server inside or our outside a virtual environment, your choice.
We develop a service level agreement with licensing terms for our proprietary migration tool which runs in Quillix Web.
We configure our specialized import utility to connect to your system if it’s a FileNet platform, or we modify our tool to connect to your back-end such as Oracle IPM.
We come onsite and run a series of tests to determine the capacity and timing of the migration.
A detailed “completions” table is completed.
We establish a plan for completion of the migration of the backlog.
Random sampling is done during the migration process. Daily progress reports are issued through our automated project management system.
Once the migration is completed we migrate the documents which were created since the conversion process.
Discuss archival procedures for documents not migrated.
Discuss creation of virtual machines for obsolete ECM systems.

Please contact us today for a comprehensive quote for your document migration.

Consider UFC^® for Your Other ECM Programming and Consulting Projects

FileNet IDM programming in Visual Basic
FileNet Capture Professional programming, with bar-code recognition, FileNet document processing options, and OCR integration
Integration of FileNet with mainframe computers via HLLAPPI and specialized programming in VB, VBA, and ASP
Web integration of FileNet Image Manager, FileNet Content Services, and FileNet Business Process Manager
Configuration of FileNet Image Manager and Content Services servers, including FileNet and HP OSARS
Design and administration of FileNet Visual Workflow systems including eProcess and Business Process Manager
FileNet connector design, for systems desiring to utilize FileNet as a back-end storage repository
Conversion of FileNet systems from Workforce Desktop, Saros, and Watermark systems