1 / 24

Content Migration

Content Migration. Welcome and Introductions. Rick Parke, Sr. Systems Engineer rick.parke@knowledgelake.com Neta Bikovsky, Regional Sales Director n eta.bikovsky@knowledge lake.com. Founded in 1999 with HQ in St. Louis, MO and sales/service offices across the country

wyatt
Download Presentation

Content Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Content Migration

  2. Welcome and Introductions • Rick Parke, Sr. Systems Engineer • rick.parke@knowledgelake.com • Neta Bikovsky, Regional Sales Director • neta.bikovsky@knowledgelake.com

  3. Founded in 1999 with HQ in St. Louis, MO and sales/service offices across the country • First mover With SharePoint for ECM – 20035+Years of Effort Delivering ECM for SharePoint • Market Leader & Developer of Document Imaging and Capture Solutions for Microsoft SharePoint • Managed Microsoft Gold Certified Partner Independent Software Vendor (ISV) • Member of MS Partner Advisory Counsel (PAC), Technology Adoption Program (TAP) and Developer Advisory Counsel (DAC) • 2009 Partner of the Year in two categories • ISV/Software Solutions • Information Worker Solutions: ECM • 1,300+ Clients Using KnowledgeLake with SharePoint for Capture & Document Imaging

  4. Paper Emails Electronic Files KnowledgeLakeConnect File without opening SharePoint Client KnowledgeLakeCapture Client Batch Scanning SharePoint Aware Save & Index Email Electronic Files TWAIN or ISIS Scanners PDF, TIF & XPS creation Paper Files - Scan Save & Index any Document OCR (full text & zonal) Barcodes & Patch codes Auto Index - KL Imaging Scalable SP Release Auto Index-KL Imaging Managed by SharePoint KnowledgeLake Branch Capture Server Client Search Index & Scope WSS or MOSS WSS or MOSS KnowledgeLakeImaging Server Auto Index - DB Lookup Throttle & Schedule Remote Capture Portal Portal Cache Search Results Export Import Collaboration Collaboration Viewer - TIF, PDF, JPG Content Mgmt Content Mgmt Content Mgmt Viewer Annotations Workflow Workflow Workflow Integration Collaboration Business Intelligence Business Intelligence Print from Server Business Intelligence KnowledgeLakeCapture Server Server Content Doc Mgmt Web Content Mgmt Web Content Mgmt DocClass for Auto Filing Batch Management MFD/Fax Integration SharePoint Web Capture & Indexing Fully Searchable PDF Workflow Portal Folder Monitoring CSV & XML Import Web Mgmt

  5. Legacy Imaging Systems Migrations to SharePoint • Brokerage Firm – Westbrook Conversion 40 million images • Manufacturing – Documentum Conversion • Human Resources – FileNet Imaging and COLD Conversion • Health Insurance – FileNet Imaging Conversion • University – Stellent Conversion • Distributor – Optika Conversion • Oil & Gas – FileNet Conversion Microsoft SharePoint 2007 With KnowledgeLake Imaging

  6. Benefits of Content Migration to SP • SharePoint trained IT staff are abundant in the industry. • Increases the ROI which lowers the total cost of SharePoint ownership. • KL/SP offers Out-of-the-box features that were previously achieved by custom code. Streamline the business-critical processes simply and efficiently. • Specialized training on propriety platform for IT staff is no longer required. • Eliminate maintenance fee from legacy vendor Minimize the loss of information.

  7. Migration Drivers • Leverage what you own • So we wrote Microsoft a big check, why are we not using what we bought • Why do we have three different systems that all do the same thing • Need to reduce costs across the board- HOW? • (Fire employees or cut software and maintenance cost) • Annual legacy maintenance • Internal support costs (redundant: staffing, training…) • Supporting multiple platforms • Forced upgrades • Custom code • Outdated and expensive hardware

  8. Economic Migration Drivers Avoid Forced Upgrade • Legacy maintenance • What would an 80% reduction in legacy maintenance mean to you? • What if you only had to renew 10% of your expensive legacy licenses? • Is your next “upgrade” a migration in disguise • FileNet is EOL two products • Documentum is consolidating from 3 to one DB • OpenText has 5 or more DM systems • Application code cannot be reused • It can take more time and money to upgrade an existing product than to switch platforms

  9. Economic Migration Drivers • Infrastructure and IT • Cost of multi platform development (.Net and Java) • Dedicated application staff vs. multi purpose SharePoint .Net • Proprietary hardware support (OSAR) • Application programming • Small application changes can take weeks (why not use standard features?) • Large projects can cost months of extra labor during a legacy upgrade • Hidden costs • Time to market • Opportunity costs – when competing for finite resources business will give up on worthy projects

  10. Motivations for Migration • Enterprises today need a simple solution that migrates all of an organization’s content to their SharePoint systems.

  11. Content Migrator from KnowledgeLake

  12. Planning The Migration • What is the volume of documents to be migrated to SharePoint? • What types of documents are stored in the current system? • Where are the documents stored (File System, Blob, OSAR)? • How are documents currently added to the system?

  13. Planning The Migration • Does the current system use Foldering? • How do users search for documents? • How is security handled? • Are there multiple versions of a document?

  14. Planning The Migration • Are annotations used? • Are compound documents used? • Are overlays used? • Are workflows used with the documents? • Are there any retention policies in place?

  15. SharePoint Architecture • How does the organization of your current legacy system map to the topology of SharePoint? • Sites • Document Libraries • Content Types • Metadata Columns

  16. Migration Strategies

  17. Migration Process • Metadata Extraction from Legacy System • Export Documents to Foldering System with Manifest XML File • Import Documents into Capture Server and Release to SharePoint • Reconciliation

  18. Hardware/Software Requirements

  19. Hardware/Software Requirements • Speed of the migration is heavily dependent on the number of Migration servers, processing power, and network communication speed.

  20. Export Architecture

  21. Import Architecture

  22. Transform Meta-Data SQL Server

  23. Connect:Ad Hoc Content Migration

  24. Connect Demonstration

More Related