Many organizations move to SharePoint
to leverage its collaboration and communication capabilities, but the transition from older systems can be cumbersome. Data
and content are often stuck in old formats and locations, increasing
the time it takes before users can leverage the new platform for day-to-day activities.
Allowing users to quickly access their legacy data from SharePoint
enables faster adoption of the platform and reduces data sprawl.
List Bulk Import from Bamboo allows you to migrate data, documents, and pictures into SharePoint from legacy databases, spreadsheets,
local/network file shares, and even from other SharePoint Lists and Libraries.
Getting your data into SharePoint 2007, SharePoint 2010, SharePoint 2013, or SharePoint Online/Office
365 is quick and easy, as is keeping that data up to date.
List Bulk Import includes the following features:
SharePoint provides a foundation for corporations to modernize and centralize their
communication and collaboration tools, and move away from older technologies like
email and locally stored files, allowing users to interact in real time with better
visibility, and stopping the proliferation of duplicated, out-of-sync files.
The first step in moving away from old systems is how to get to the data you already
have. List Bulk Import allows you to migrate data, documents, and pictures into SharePoint
from legacy databases, spreadsheets, local/network file shares, and even other SharePoint
Lists and Libraries. The following comparison chart shows SharePoint out-of the-box versus List Bulk Import:
List Bulk Import Web Part can be run on a client machine (server installation is not required, but it is recommended). Once installed, you simply
connect to a SharePoint server to which you want to import data, select a data source to import from (i.e., Excel, ODBC driver, or a SharePoint List), map fields from
the data source to the target SharePoint List, determine how you want to handle duplicate records, select whether to import all versions (if importing an Issues List or
Document Library with versioning) if needed, and then import the data. You can also choose to save the import configuration to reload it again manually, or schedule regular
imports of data to run unattended according to that configuration. To view the process or status of an update, or to help resolve any import errors, there is a log file that
can be viewed from within the application.
Knowledge Base Articles: