Lotus Notes to SharePoint Blog

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

Migrating Lotus QuickPlace to SharePoint (Part 1): The basics

[Updating and reposting an old series on migrating QuickPlace and QuickR sites to SharePoint.]

I remember when Lotus QuickPlace was introduced into the marketplace back in 1999.  As a developer then focused on using Domino to built cool web applications, I admit that I did not totally get it at first.  After all, there wasn’t much you could do with QuickPlace that you couldn’t do with Domino… and there was a lot you couldn’t do with QuickPlace.  The point, of course, is that you didn’t need a developer.  Users could spin off their own secure sites, define a few properties, and they were off and running with basic team collaboration capabilities.  Users could even add custom layouts, custom form types, custom fields, and even simple workflows. 

And did these sites ever proliferate!  When we talk to large customers who now want to move off of QuickPlace we are frequently talking about hundreds or (more often than not) thousands of QuickPlace rooms.  The good news is that mapping a QuickPlace to SharePoint tends to be fairly straightforward.  All the capabilities and content types in QuickPlace can be found in the simplest SharePoint team site.  This series of posts describes the migration process at both the conceptual level and a tool level (using Notes Migrator for SharePoint).

For those you who have never seen a QuickPlace, here an example. This particular QuickPlace is based on one of the early samples from Lotus (the “Rapid Response Team” government demo) and thus has a particular look-and-feel and layout.  Like most QuickPlaces, it has rich text publishing pages, a discussion area, a document library area, a team calendar, a task list and a member list.  A navigation menu on the left allows you to navigate around and, of course, you access it all in a browser. 

image  image  image

An important aspect of QuickPlace (not obvious from the above screen shots) is the fact that we are looking at a top level room.  A QuickPlace can have can have multiple sub-rooms, each as big as its parent room, and each having its own layout, theme, security rules, etc.  A tree of over 100 rooms and sub-rooms is not uncommon.

As mentioned above, QuickPlaces are customizable.  A particularly important aspect of this is the ability to create custom Forms or to extend existing Forms.  The following screen shots show customizing a form and adding a new field fields using one of the available field types.

image image

When you add new content to a QuickPlace, you typically press the New button to select a Form.  When you save your new document (a “page” in QuickPlace parlance), you decide which folder to put it in. 

image  image   image

Of course there are some obvious defaults in play here:  If you are in a Calendar, you probably want to create a new Calendar page.  And if you are saving a new Calendar page, you probably want to save it into your Calendar.  But it is important to note that QuickPlace is pretty flexible about that sort of thing.  There is nothing to stop you from putting a Task page in a Document Library or a Discussion folder. 

In fact, this is one of the few fundamental differences between SharePoint and QuickPlace:  SharePoint treats each List / Library as a separate container (each with a  strict schema and list of allowed content types). QuickPlace treats each room as a big bucket of pages and those pages are made to appear in particular places (folders, etc.) and can be easily moved.  There are advantages of both systems but you should be aware of this difference when you migrate. 

By the way, if you have Lotus QuickR, everything in this post (and on this blog) applies equally well to you.  QuickR is simply the new rebranded name for QuickPlace.  If you are running the version of QuickR that sits on top of Domino servers, you can migrate them using Notes Migrator for SharePoint just fine.

I want to end this first post with a comparison of SharePoint and QuickPlace concepts.  As you will see, there is almost a one-to-one mapping of concepts.  In the next post in this series, I will dive into how Notes Migrator for SharePoint handles migrating QuickPlace to SharePoint.

QuickPlace concept SharePoint concept
QuickPlace Site
Room / Sub-Room Site / Sub-Site
Folder List, Library or Folder
Page List Item or Library File
Form List Definition or Content Type
Fields Columns
Members Members
QuickPlace Permissions Site Permissions
Page readers and writers Document Permissions
Library Document Library Template
Calendar Calendar List Template
Task List Task List Template
Menu Quick Launch
Imported File List Item Attachment or Library File

3 responses to “Migrating Lotus QuickPlace to SharePoint (Part 1): The basics

  1. Pingback: Migrating Lotus QuickPlace to SharePoint (Part 2): Migration jobs « Notes SharePoint Blog

  2. Rob Novak January 20, 2011 at 2:35 am

    BTW your table is not current. Please feel free to contact me for the latest comparison.

    • Puja March 22, 2011 at 3:18 am

      Hi,

      We are doing estimation of migrating data from QuickPlace to SharePoint 2010. So, can you share with latest comparision between both. Also, is it possible to manually migrate data from Quickplace to SHarepoint.