Fact sheet and videos

Migrate your documents:

  • From: any SQL Server based ECMS or CMS with documents stored in a physical file store
  • To: SharePoint 2013, SharePoint Online / Office 365 document libraries and folders, including record  centers.
  • Map your metadata to ordinary fields or to SharePoint lists, users, or managed metadata
  • Created and last edited dates, and creator and last editor automatically mapped to the corresponding SharePoint fields for each version. Note, creator doesn't always map for Office 365.
  • All versions, or just the latest. Majors and minors supported.
  • Document level security if required
  • A few at a time or a few hundred thousand at a time
  • Control extraction of your document information with your own SQL
  • Pretty quick - speed depends a lot on your physical environment, 2-5GB/hr is fairly typical per instance. One customer used 10 instances on each WFE and APP server, 40 simultaneous instances, and got speeds from 50-80,000 documents per hour
  • Skills required:
    • Setup and initial configuration: Strong SQL and Migration, medium SharePoint
    • Migration runs: Basic SQL, SharePoint, Migration

Supports various document migration processes:

  • Migrate all the documents at once, or selection by selection
  • "Back fill" and then refresh the recently changed documents at Go Live
  • You can run test document migrations, then remove the test documents and retest with just a few clicks. Similarly you can back out a live migration run in a few clicks
  • The old ECMS can be updated as documents are migrated. For example, set security to read-only, update a field with the SharePoint URL.
  • Note: When a migration run is backed out you can restore the security.

Other features:

  • For maximum speed the application is run on a server in the SharePoint farm, and multiple instances can be run simultaneously.
  • For Office 365 it is run from a desktop, and again, multiple instances can be run.
  • Document data is collated in SQL Server Views which you control
    • Site, web, and library can be set for a migration run, or they can be defined in the SQL Views on a document by document basis
    • Content type and folders can be defined in the SQL
  • Easily map metadata to SharePoint text, number, date, list, user, or managed metadata fields
  • Logging to SQL Server tables
    • So the SQL prevents documents being migrated twice
    • Log viewer provided
  • Configuration data is easily set and then stored in an XML file in the application folder
  • The SharePoint “Name” field size and uniqueness constraints can be met in several ways including:
    • using the document number,
    • using the document title optionally shortening and / or appending the document number to conform to size and uniqueness requirements
  • Illegal characters are replaced with “_” in document and folder names
  • Missing or zero byte files are replaced with placeholders ensuring the metadata is migrated
  • Live monitoring – MB/hour, documents/hour, error counts

A few videos ...

Index of videos

  • A quick introduction(1:50)
  • Configuring SharePoint and the Migration Databases(4:58)
  • Configuring the Migration Tool (4:13)
  • End to end walk through of a migration run (5:25)

Video 1: A quick introduction to our SharePoint Migration Tool (1:50)

Video 2: Configuring SharePoint and the Migration Databases (4:58)

Video 3: Configuration the CSw SharePoint Migration Tool (4:13)

Video 4: End to end walk through of a migration run (5:25)