Notes Migrator for SharePoint 6.0 now allows you to migrate directly to SharePoint 2010 environments without needing to install the Notes Migrator for SharePoint Import Service (or any other Quest code) on your SharePoint front end servers. This of course is a huge win for anyone who operates a highly secured SharePoint environment where asking to install a third product raises eyebrows. It is also essential for migrating to SharePoint Online / Office 365 (option 3 in this blog post).
Enabling this migration mode in Notes Migrator for SharePoint is simple. Go to the SharePoint tab in Advanced Configuration Options and set the connection type for your environment to “SharePoint 2010 Web Services”. You will notices that there are actually two choices here, one that uses “Classic Mode Authentication” and another that uses “Claims Based Authentication”.
For SharePoint Online (Office 365 or BPOS-Dedicated) use “Claims Based Authentication”. For most other sites, use “Classic Mode Authentication” unless you know your SharePoint environment is using CBA. We will cover more about how authentication works with CBA sites in a separate article.
For environments configured to use “SharePoint 2010 Web Services”, the Settings dialog is slightly different than for environments that use the Import Service.
The main option here indicates whether to you want to use the Quest Link Tracking Service for documents migrated to this site. For most people, the answer would be “yes” because the value of preserving intra-document links is so high. One thing to be careful about however is that the default URL for resolving dynamic links is a layouts page in the current site. Unless you are planning to install Quest’s Front End Services or Sandbox Link Redirector solution, that redirector page is not going to be there. It is a good idea in this case to specify an alternate Redirector page URL, otherwise users would see broken links until you got around to finalizing them.
Back on the main environment configuration dialog, click on the Credentials link to specify your method of authenticating with the server.
Once you have configured the type of connection you want and related options, everything else works pretty much the same as it did when you were migrating via the Import Service.
So what are the limitations of migrating via web services instead of via the Import Service? The good news is “not much”. The new SharePoint 2010 web services are surprisingly complete and our developers have found ways to do almost everything our tool needs to do through them. As of today, there is only one known limitation:
- Can’t migrate to SharePoint 2010 managed metadata fields.
To overcome this and any future limitations, we have introduced a new component called the “Lightweight Migration Service”, which I will discuss in more detail tomorrow. (Unfortunately, this option is not yet available on Office 365, but it is available for BPOS-Dedicated and on-premises servers.)
One additional issue is performance. In some (but not all) cases, it takes longer to migrate through the SharePoint 2010 web services than it would have to migrate through the Quest Import Service. Also the default connection timeouts etc., for the web services reside in SharePoint config files and some people would not want to have to reconfigure them for the sake of a migration tool.
For these reasons, we don’t expect the Import Service to go away any time soon. But for many people the ability to get up and running without having to install anything on the server is a huge benefit.