Not too many big splashy features this time.  We intentionally took one release to round out the current feature set, improve the underlying plumbing, and catch up on a number of mid-sized customer/partner requests.  Some improvements have been inspired by our experience with Microsoft SharePoint Online and other hosting partners.

Hopefully, there will be something in there for everyone.  In no particular order, here are the new and improved features:

SharePoint 2010

• Version 5.3 of Notes Migrator for SharePoint can migrate to SharePoint 2010.  While not officially supported yet,  this release has been tested with the SharePoint 2010 public betas and release candidate.  All current functionality (the stuff you could do when migrating to SharePoint 2007) works in the beta today and we will be adding additional functionality to support new 2010 features in the coming  months.  Official support for SharePoint 2010 in Quest tools will be announced shortly after SharePoint 2010 is released.

Discovery and Analysis

General Migration Improvements

• It is now possible to map multiple source fields to one target Note field. The result should be one concatenated HTML field with a blank line in between the two parts. The order will depend on the order entries in the mapping table. Using this mechanism, can also concatenate a plain text field or even a constant value to the end of a Notes field.
• A new “AttachmentLinks” construct allows you do include links to document level attachments at the end of rich text areas.  This enables migration of applications that store attachments at the document level (such as QuickPlace) to target formats that do not have an attachments area (such as Word, Basic pages, Wiki pages and Web Part pages).
• When migrating file attachments to alternate SharePoint library locations, you can now add URL fields to main “parent” documents.  This makes it easier for users find the parent document when opening file attachments in search results, etc.
• When migrating parent/response documents to SharePoint “discussion” templates, you can now add URL fields to “parent” documents.  This makes it easier for users find the parent document when opening a response document in search results, etc.

Word Document Generation

• When generating Word documents, you now have the option of encoding file attachments inside the documents instead of migrating them to separate SharePoint library locations.  Since Word does not support true file attachments, these are encoded as embedded Windows Packager objects.
• A new property named "Formatting Style" is available when a target of type "Word Document" is selected. This property allows users to specify which MS Office formatting Style to apply when mapping constant or other plain text source values to the word document body.
• When generating Word documents, you can now migrate content to Rich Text controls.

Migration Console

• A new Extract Database Users tool in the Migration Console allows you to select one or more databases in any database view in the Migration Console and then extract all the user names contained in those databases.  This tool is useful for simply gaining an understanding of the users involved in a group of Notes applications, but the primary purpose of the tool is ultimately to generate a user mapping file that NMSP can use at migration time.
• A completely overhauled job progress / log viewer dialog for both the Designer and Migration Console clients contains many improvements including more useful information display, accurate progress bars, ability to view log details before job is finished, a more responsive cancel button and more. 
• For migration jobs that have been run using NMSP Designer or the NMSP Command Line, the logs can be imported into the Console's Task History. This allows the jobs to be visible in the database’s migration history.

Security / User Mapping

• When mapping Notes Access Control Lists (ACLs) to SharePoint sites, you now have the option to map various access levels and roles to existing security groups such as “Site X Owners”.  While this is not as precise as assigning exact permissions to each user and group, it is much simpler to understand and maintain and is adequate for many situations.
• You now also have the ability to do both “Map Notes Groups to Domain Groups” and “Expand Notes Groups to SharePoint Groups” (they were mutually exclusive before). If you do this, the tool will first try to find a mapping for the group name in the directory or mapping file. If it finds a mapping, it will map to the Domain group. If it doesn’t, it will provision a SharePoint group instead.
• When migrating document level security (reader/writer fields), you can now disable the automatic adding of users to the site collection that were not already here. In prior versions, the tool added such users with “Limited Access” permission to the site so it could give them access to certain documents, but now administrators can decide not to allow that.
• You can now override the ‘distinguishedName’ property used to construct an LDAP query when using Active Directory lookups to map user names. In the User Mapping options, there is a new property, Field to use, where you indicate the field to use in the directory lookup. 

Command Line Utility

• Added -formula and -view options to command line utility (NMSPCMD.exe).  This provides additional flexibility in scripting complex migration tasks using external tools.

Installer

• The installers have been rewritten to better support multi-server environments.  Most server-side components are now deployed as SharePoint “solutions” via WSP packages and administrators have more control over which components are installed on front-end servers vs. central administration servers.  The installers are now simpler and less prone to mistakes.