How to Migrate Major and Minor Versions of Domino.Doc to SharePoint (4250610)

How to Migrate Major and Minor Versions of Domino.Doc to SharePoint

When migrating from Domino.Doc to SharePoint versions can come over correctly.

The option of “Create major and minor (draft) versions” in SharePoint versioning settings could not be automatically chosen by the MNSP tool. In order to migrate the major and minor versions, we need to manually set up the SharePoint document list settings and configure the source data definition in tool.

Steps to migrate the Domino.Doc versions:

1. Create a target document list in SharePoint, enable the document versions

• Document Library Settings -> Versioning Settings -> Document Version History -> Create major and minor (draft) versions
• The value of "Require Check Out" should be as "No"

2. Configure the migration job

• Select “All documents” and “All versions” options in Source Data Definition
• Set the duplicate found as “Create new version (if modified)”

*Note: Minor versions are only available in a hotfix build of 6.6.1 or newer. Please contact support for the hotfix build. If 6.6.2 or newer is released at the time of reading this, these builds will have this hotfix already included.

Limits: 1. Keep the version type but not the version number This is the SharePoint’s limit, the current version of SharePoint does not allow us to explicitly set version numbers as we migrate. For example, if I attempted to migrate version 2.0, 2.1 and 3.0, it would have ended up as 1.0, 1.1 and 2.0. 2. The tool can support most of target templates of Target Data Definition except the “Web Parts” template 3. The Domino.Doc allow the minor version can without major version when the version number is larger than 1 For example, the versions can be 0.1, 1.0, 2.1. There is not a 2.0 version. But this behavior is not available for SharePoint. So for this case, the tool will migrate the versions as 0.1, 1.0, 1.1. (The minor versions will be as the previous version’s minor version.) 4. Versioning is used for document item rather than the attachment. Also the attachment is a part of the content of document item, it can be added, modified or deleted in one of versions. That's why sometimes the versions will be lost after migration. For example, the document item versions is 1.0, 1.1, 2.0, 3.0, and the attachment is created in 2.0. The migration result will be 1.0, 2.0 (1.0 and 1.1 are lost.).