Lotus Notes to SharePoint Blog

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

How to migrate to SharePoint Wiki pages

Notes Migrator for SharePoint has allowed for migration to SharePoint wiki pages for over a year now.  Wiki pages were of mild interest in SharePoint 2007, but as described in my last post they have evolved into an awesome target choice in SharePoint 2010.  For example, you may have noticed that the Site Pages library in many of the new 2010 site templates is now a Wiki library.

The following steps recap the basic steps and some of the advanced options for migrating Notes documents to Wiki pages.  These steps apply equally well for SharePoint 2007 or SharePoint 2010 (but SharePoint 2010 requires the use of Notes Migrator for SharePoint 5.3.1 or higher).

Basic Steps

  • If using the Designer client, select a source Notes database, QuickPlace or QuickR room, or Domino.Doc library and then select a corresponding source data definition.  If using the Migration Console, simply open the Database Properties, got to the Migration Jobs tab, and add a new migration job.


  • On the second tab, select a target SharePoint site and Wiki page library (or any document library).  When asked whether you want to load a default target definition, say “Yes” and load the “Wiki pages” data definition.  You can also provision a new library on the fly here.

image image

  • On the third tab, press the “Auto Map” button.  The default mappings will create Wiki pages with the same name as the original Notes document, use the rich text Body field as the Wiki page content, and map any embedded elements to files in a subfolder.


  • Press the Run Job button and go!


What you get in the end is a bunch of new Wiki pages in your SharePoint library.  Any embedded images, attachments, or OLE objects shown on the Wiki pages are really stored in the “Attachments” subfolder.



Advanced Job Customizations (optional)

  • If you prefer to put images and attachments into a separate library, simply edit the target data definition, select the Files field, and specify the Alternate Library property instead of the  Alternate Folder property.  (By the way, this is definitely the “2010” way to organize things.  Many 2010 templates contain a “Site Pages” wiki library and a “Site Assets” library where all the images and attachments are intended to go.)


  • If you would like to migrate the original attachment icons for your Notes attachments, simply edit the target data definition and check the “Migrate Attachments as Image files” checkbox.  The additional image files will be saved to the same alternate folder or library described above.

image   image

  • If you are migrating a QuickPlace site or other Notes/Domino application that does not store attachments inside the rich text Body field, you may wish to concatenate a rendered “attachment links” area to the bottom of the page so you can link to them.  QuickPlace and QuickR data definitions already have a built-in “{OtherAttachmentLinks}” section that you map to the existing WikiField in your target.  (If you are using other data sources. you will need to define an AttachmentLinks section in your source data definition.)


  • Notice how you the above job maps multiple source columns to one target WikiField?  You can actually concatenate as many things as you want (multiple rich text fields, text fields, and even static labels) to your WikiField.
  • If you want to map additional Notes items to SharePoint metadata fields, just do that as you would for list items.  The extra fields will show up in the page properties and you can use them in view columns.

image  image

  • Of course, you can use many other Notes Migrator for SharePoint features with your Wiki pages:  created/modified metadata, document level permissions, content types, folders and subfolders, approval status, incremental migrations, and much more.

Comments are closed.