While the server side components of Notes Migrator for SharePoint are pretty light-weight and unobtrusive, we do still meet customers who have hard and fast rules that NO third-party software be installed on production SharePoint servers...  ever. 

The problem is that the remote access capabilities provided by Microsoft are not nearly powerful enough to do what we need to do when migrating data.  (For example, they do now allow us to set the Date Created and Created-By metadata for migrated documents.)  Therefore it is critical that some part of our code (typically our Import Service) be able to write write to the managed SharePoint APIs that are only available on front-end SharePoint servers.

So are we simply out-of luck here? 

No, happily there is a work-around works for most customers.  It involves creating an additional server dedicated to doing migration work, but today's virtualization technology makes that relatively easy.

1. Build out a temporary SharePoint server and add it as an additional front-end server in your production server farm.  (In Notes terminology, add it to your cluster.)  This server will be for migration only.  Do not configure your load balancer to send ordinary end users to access this server.
2. Install the Notes Migrator for SharePoint Import Service on the temporary migration server.  Configure the Import Service for any site collection you plan to migrate to.  Be sure to use the machine name of the temporary migration machine (not the load balanced URL) when specifying the Import Service location.
3. Migrate data to the temporary migration server.  Note that all content will be saved in the same content databases as the other servers in the farm and will be immediately visible to users.
4. When the migration work is done, remove the temporary migration server from the farm.

At the end of the day, you will have migrated documents and your production SharePoint servers will not have been compromised!