This project is read-only.

Import folders and files with all subfolders

Import files and folders from a file system to a document library.
Every imported item has a reference to it's source, stored in the "_Source" field.

Retain creation and modified date fields after moving to SharePoint

Files will keep their original creation and modification dates. In SharePoint 2007 editing these fields was only possible inside the object model, requiring installation on the server. This is no longer the case.

Can be run from outside the SharePoint Server.

Every action is done using the Client Object Model. The import can be run from a client machine.

Retain author/editor fields from office documents after moving to SharePoint

Typical Microsoft Office fields are automatically populated

Incompatible file names are renamed (filename too long, illegal characters)

Filenames are automatically sanitized to conform to the sharepoint naming requirements. This includes stripping illegal characters, trimming leading and trailing spaces and dots, and truncating the filename if it is too long.

The maximum file name length in SharePoint 2010 is 123 characters.
The characters that are blocked by SharePoint 2010 for filenames are the following: " # % & * : < > ? \ / { | } ~ }

Unsupported files (large filesize, blocked file extension, …) are skipped

SharePoint 2010 blocks a list of about 100 file extensions. They are automatically skipped during the import.
The list of blocked extensions can be viewed in the Central Administration > Security > Define Blocked File Types
By default SharePoint 2010 is configured to allow files up to 50mb. The importer currently uses a limit of 200mb.
This will be configurable in a next version.

Files already existing on SharePoint are skipped (no overwrite)

The importer will never overwrite files that are already in SharePoint. Files that are already in the document library will be skipped. Matching files is done based on the original file locations. The location is saved along with the file (in the _Source field). If there is a match the files are considered the same.
Importing the same file from a different location will import the file as if it were another file.

Successfully migrated files and folders can be moved to an “archive” folder

Optionally, files can be moved to an archive folder. This can help to ensure that the original files on the file system will no longer be used.
When a file is moved a shortcut file is created in the containing folder wit ha link to the location in the document library. This ensures the file is still easily reachable from it's original location.

Detailed logging (Log4Net)

By default the application is configured to write to the console window and to a log file. It is possible to configure additional appenders. For more information consult the log4net documentation (

Import files conserving the original file system structure or merge the files into a flat list.

The original folder structure can be kept if required.
The files can be merged into a single flat list in order to leverage the metadata based filtering and sorting in SharePoint 2010

Duplicate name resolving

When a deep folder structure is imported into a flat list thete is a chance that there will be filename collisions. The importer ensures that all files are imported by adding a sequence number to the file name if multiple files with the same name exist.

Option to skip creation empty folders in SharePoint

Last edited Apr 28, 2010 at 2:08 PM by melg, version 4


No comments yet.