Solution package is spin off of SAI MOSS Helper product family, which allows users
to export/import data from SharePoint lists and document libraries. The solution
is available either as a Windows application, which can be installed on any client
machine without the need for server software or as a standard SharePoint SAI Web
Part. The application can either import or export data from SharePoint data store.
Data Import
Overcome the limitations of SharePoint import functionality and allow users to migrate
data and documents into SharePoint lists and document libraries from databases,
spreadsheets, SPS 2003 and MOSS 2007 lists and document libraries.
►
Import of Metadata for document libraries and lists including created and modified
dates.
►
Allow users to map fields between source and destination during migration.
►
Supports multiple sources like databases, spreadsheets, SPS 2003 or other MOSS 2007
sites.
►
Ability to specify List Id for items during migration.
►
Validate and handle duplicate records during migration.
►
Lookup columns for list imports will be supported. If the data from the source does
not match the lookup columns, users can map the expectations manually.
►
For migration of file systems into document library, provides option to maintain the folder hierarchy during export.
►
Export configurations can be saved (XML configuration) and loaded at a later time. The saved configuration can be executed in batch process, automatically scheduled during off peak hours or run in the background process.
Data Export
Users can extract data/documents from SharePoint lists and document libraries to
a local or network file system. The following user friendly features are provided.
►
Export of documents with or without versions.
►
Filters can be applied (CAML query builder provided or selection of views) to lists
or document libraries to be exported.
►
Meta data associated with document library and lists can be exported.
►
Export of Lists items and associated attachments are supported.
►
Folder structure of document library can be recreated during export.
►
Export configurations can be saved (XML configuration) and loaded at a later time.
The saved configuration can be executed in batch process, automatically scheduled
during off peak hours or run in the background process.