Migrating BDLC to a new SharePoint Version
Planning to migrate your SharePoint 2010 / 2013 / 2016 to the next version? Learn
here how to keep all your BDLC connections and continue synchronizing your
external data sources into your new SharePoint environment.
When migrating your SharePoint version from 2010 -> 2013, 2013 -> 2016 or 2016 -> 2019,
it is possible to take your BDLC environment and all connections with you.
The easiest way to do so is to re-attach the database. Here are some points
to consider when doing so:
- Make sure the BDLC is installed in the appropriate version in your new
- BDLC is not meant to run in 2010 compatibility mode AND in the standard 2013
mode on the same farm. While the BDLC timer job will work properly in both
modes, the UI in either 2010 or 2013 is not usable.
- BDLC configuration items identify their connected lists through the ID of
the list and the ID of its website. Migrating by re-attaching the database will
not alter these IDs so your configurations are still valid and you can use BDLC
immediately after upgrading.
- When using migration tools, the possible change of the list and web IDs
should be looked over carefully. If, after a migration your BDLC connected lists
seems to have no connection settings anymore, it is most likely that the IDs
have changed and no longer refer to the values in the configuration list
BDLC itself does not provide functionality to detect changed IDs. You
will have to correct all these IDs manually before the BDLC will be able to run
as expected within your new environment.
Please note that you will need a new license for the new server(s). Contact
assistance in getting the updated licenses with the new server names.