Lotus Notes to SharePoint Blog

Blog about Dell's Notes Migrator to SharePoint tool and other things related to Lotus Notes migration projects

Migrating Domino.Doc version histories (and unpublished documents) to SharePoint

Here is a screen shot of the new Domino.Doc selection options in Notes Migrator for SharePoint with the “versioning” parts highlighted in red:

image

For backward compatibility, the defaults are “Latest Major Versions” and “Published Documents” only, which migrate just one copy of each document.  However, you now have the ability to request prior versions and unpublished versions of each document as well.  This, of course, can result in multiple copies of each document.

image  image

In Notes Migrator for SharePoint terminology, these extra versions of the same document are treated as duplicates of the same document and thus our duplicate document handling options are triggered.  Our “If duplicate found” options were actually first implemented to handle incremental migrations (migrate the same database over and over and pick up any changes since the last time) but they turn out to be pretty darn useful for migrating version histories.

image

If you wanted to make each version appear as a different document in SharePoint, select “Write New Item”.  A more interesting choice, however, is to select “Create New Version”.  This will cause each version of your Domino.Doc document to become a new version of the same document in SharePoint. 

image

Note that you need to make sure that Versioning is enabled in your target SharePoint list or library:

image

One caveat here…   Notice that I did not migrate unpublished versions (for example, version 2.1 in the above document).  Unfortunately the current version of SharePoint does not allow us to explicitly set version numbers as we migrate.  So if I attempted to migrate versions 1.0, 2.0, 2.1 and 3.0 it would have ended up as 1.0, 2.0, 3.0 and 4.0.  Similarly, if my Domino.Doc library had pruned old versions and we now had only 3.0 and 4.0, that would have become 1.0 and 2.0 in SharePoint.  We are trying to convince the SharePoint product team to address this limitation for SharePoint 14, but for now keep in mind that this feature works best if you select all published versions in your query.  A workaround when you can’t do that is to explicitly migrate the “{VersionNumber}” field to an additional SharePoint meta-data field so you will always have that as a reference.

Comments are closed.