Every once in a while, we hear one of theses requirements from customers:

• Extract all the attachments from a Notes database and place them in the file system (instead of SharePoint)
• Convert Notes documents to Word Documents and place them in the file system (instead of SharePoint)
• Convert Notes documents to PDF Documents and place them in the file system (instead of SharePoint)
• Convert Notes documents to InfoPath Documents and place them in the file system (instead of SharePoint)

The trick to doing any of these things is to use our intermediate data file format.  Just design a Notes Migrator for SharePoint migration job and when running the job, select Save to Intermediate File.  This will give you the option of saving any attachments or generated documents as disk file rather than encoding them in the main XML output file.

The problem with this approach is that the files that are saved to disk are not really that useful because they are arranged by Notes UNID, not any way that would be useful to humans.  That’s where the free utility come in.  This utility, which may be downloaded from our Notes migration community site, will take all these files and place them in the folder (or network share) of your choice and arrange them according to your requirements.  If you want to see an example of this tool in action, watch the video of Session 6.  Slides starting at about minute 77 and demo starting at minute 91.  Have fun!

The problem, of course, is that these tags do not do you much good because, by default, SharePoint does not know how to use them.  That’s where Quest Web Parts for SharePoint version 5.7 comes in.  If you place our rich text web part on your page, all those migrated sections suddenly start working!  Even better, users can continue to create expand/collapse sections in new documents.  Won’t your Notes users love that?

See this post on the new version of Quest Web Parts for SharePoint.  If you scroll to the bottom, you will see a section “Improved Integration with Notes Migrator for SharePoint” and a really cool video describing what is going on.

Quest Web Parts for SharePoint has always been popular with Notes customers.  Features such as multi-level threaded discussions, dynamic navigation areas, and tabbed form layouts has been helping migration teams satisfy the requirements of their migrated Notes applications (at a drastically lower cost than hand-coding those features) for years now.  Of course it is not just for migrated Notes apps, but is really useful of many other SharePoint development scenarios.

Design Migration

Migrate Notes Views to SharePoint Views – This feature will allow you to select a Notes view and generate a similar view in any SharePoint list or library.  Because the mapping of columns in your view is intimately tied to the mapping and provisioning of data columns that occurs in your migration job, this new capability is also tied to your migration job.  Specifically, view migration is found on the new Advanced tab of your Target Data Definition.  You can design new views there and the views are provisioned when the migration job is run.  A nice side effect of this model is that you can run the same migration job against many new or existing lists or libraries.

Press “Import from Notes” and then select the Notes view you want to migrate.  The view migration wizard will then attempt to design an equivalent SharePoint view, mapping as many Notes columns as possible to existing SharePoint columns OR to new columns defined in your job’s target data definition.  As you might expect, there are a number of things that can go wrong with such an automated mapping.  The two most likely issues are (1) the Notes data item shown in the view had not been migrated to the SharePoint list yet or (2) the Notes view column is computed and the formula is too complicated for a tool to convert.  For issues like this, manual intervention is required and the migration wizard guides you through that.  In the View Columns step, it gives you a side by side view of the Notes and SharePoint columns and highlights the parts that it needs help with in red.  You can decide to manually map a Notes existing columns, define a new data column (which will be added to your migration job), or even specify a formula for a new computed column in SharePoint.  Similarly you can also specify the sort order, the grouping and the document selection rules, or you can just take the defaults. 

Content Type Generation – These feature takes the tool’s ability to migrate schema (select fields from a custom Notes application and provision a similar schema in a custom list) to a new level.  Now you can migrate your custom Notes application schema to SharePoint content types instead.  You can create new Content Type Definitions on the new Content Types tab of your Database or Technical Class records in the Migration Console.  You can design them from scratch or, more likely, you will generate the Content Type definitions from a Notes Form, from an existing migration job, or from an existing list that you have been working on.  (The last two options allow you to do your initial development and testing on a custom list and then transition to content types later.)

Once you have generated an initial Content Type Definition, you can further customize it, specifying the parent content type, the group, and the columns.  The columns editor looks like the Target Data Definition columns editor, but in this case you are defining Site Columns instead of List columns.  When you are ready to provision your new Content Type, the tool will try to find existing Site Columns that match your specification and will provision new ones if needed. 

New Column Provisioning Options – The ability to provision lists and libraries while migrating content has long been a popular feature.  This capability has been greatly expanded to allow provisioning a nearly complete list of SharePoint column options, such as default values and data validation.  You can even set columns to be read-only (something you can’t normally do in the SharePoint user interface).  Note that as before, the provisioning options only apply when the tool is first provisioning the columns; it does not upgrade existing columns.

Provision Calculated columns – You can now define Calculated columns in your target data definition.  These will be provisioned in SharePoint when your migration jobs are run. This Microsoft documentation page explains the legal syntax for SharePoint formulas:  http://msdn.microsoft.com/en-us/library/bb862071.aspx.  You can also use our new built-in formula editor, which appears at several points in the product.

Provision Lookup Fields – Lookup fields can now be provisioned in SharePoint lists.  Previous versions of the tool allowed you to migrate to Lookup fields, but you first had to manually configure them in SharePoint. You can even configure lookups from lists in other sites in the same site collection (something you can’t normally do in the SharePoint user interface).

Content Migration

New Run Job options – During normal migration jobs, Notes Migrator for SharePoint first takes care of the provisioning steps (creating the list/library if needed, adding the appropriate content types to the list, adding any missing columns if needed, and creating views, setting the list/library permissions) and then migrates the content.  Now you can now choose to run just the provisioning bits without migrating the content.  This will be useful in cases where you want to review the resulting list schema and perhaps make changes to the list settings before migrating content.

Also note that the above screen shots show off the tool’s new Run Job button with the drop down menu of various modes of running the tool, such as importing data to and importing data from intermediate XML files.  Since this button is also available in the Migration Console, users can now leverage the intermediate file options from there (it was formerly available in the Designer Client only).  Similar functionality is also available in the tool menus and the bulk Migrate To SharePoint task in the Migration Console.

Migrate by Form Used – When selecting records from your Notes database, you can now elect to query records by form.  You can pick one or more Forms from the Notes database design or type them manually.  This will limit the records selected to include only those data records that were flagged with the forms you selected (i.e., where the “Form” item was set to one of those form names).

If you specify forms in this way, the Select Items and Columns dialog will also display the data items defined on your selected forms.  (Remember, however, that background agents, etc., may have also set data items on the Notes documents, so you may still need to look at the Sampled Items node to discover those.)

Improved Content Type Support in Migration Jobs – Notes Migrator for SharePoint already had pretty good support for dealing with content types while migrating content, but this release extends those capabilities and also makes it much easier to use.  The new Manage Content Types section on the first tab of the Target Data Definition allows you to push site content types into a new or existing SharePoint list.  Adding the content type to the list is a prerequisite to writing documents with those content types, so this new feature eliminates that manual step and make more automation possible. 

In addition, you can now associate each content type with one or more Notes forms.  If you do this, then the tool will automatically assign the content type for each migrated document without the need to do any explicit mappings.  (For more complex scenarios you can still explicitly map any piece Notes data, including the result of a formula evaluation, to a ContentType field.)

Note that this feature is completely independent of the ability to generate new Site Content Types, as described above under Design Migration, but you may often find yourself using the two in combination.

Normalize multi-valued items to multiple documents – It is common for Notes forms to implement detail records (the things that relational developers would have set up a one-many-relationship for) using multi-valued data fields arranged to look like a table, as shown below. Users would then fill in as many entries as the needed, making sure that the values from each multi-valued item lined up properly.

Now you can use Notes Migrator for SharePoint to extract the multi-valued items as separate records. To do this set the Multi-Value disposition option for the columns that you expect to contain arrays (ContactName, ContactTitle, and ContactPhone in the above example) to “Normalize”. This will cause NMSP to generate multiple SharePoint items (three in the above example) for the values in the columns designated for Normalization.

Note that if you also wanted “header” records you could first migrate those using a separate migration job. You could use lookup fields or some other mechanism to relate the “header” and “detail” columns. In the above example, Customer ID in the Contacts list is set up as a lookup field that references the Customers list (where Customer Name and Category are also stored).

Finally, you may encounter Notes forms that list out each item in separate rows, instead of using multi-valued items. NMSP can handle that case as well, but the migration team will need to do a little work with formulas to generate multi-valued columns to Normalize on.  For example, you could define a source data definition column with the formula “Product_1: Product_2: Product_3: Product_4” to generate a “Products” array.

Dynamic link tracking for URL columns – When migrating Notes data to SharePoint URL fields, you can now leverage the tool’s popular Link Tracking Service for those links (the same way you currently do for Doc Links in Rich Text Fields).  You do not need to do anything special to enable this.  Simply start migrating data items that store notes:// links (or formulas that generate notes:// links) and they will be converted to dynamic links that will ultimately point users to the migrated versions of those documents. 

As a reminder, the tool supports two input formats for Url fields.

• <url> -  sets the url to be the display name in SharePoint
• <url>, < name> -  sets the url and display name separately in SharePoint

Improvements in “Render With Form” function – This very popular feature, which allows you to extract the content of any custom Notes database (regardless of the complexity) so you can archive them as simple rich text documents in SharePoint, has been improved in a number of respects. Handling of dynamic subforms, computed fields, computed text, and keyword fields have been improved, resulting in even better looking rendered documents.

Provision Alternate Libraries – Users have often relied on the tool’s unique ability to migrate images and attachments to a separate location from the main documents being migrated.  For example, you might want to place all attachments in the Shared Documents or Site Assets document library.  Previously you would have had to provision these alternate libraries manually before running your migration job.  Now the tool provisions these automatically if needed.

Analysis / Migration Console

Capture Design Copies during Analysis – Now when you perform a Design Analysis on a set of databases you can elect to also create a local design copy.  For every database scanned, the tool will create a small copy of the database (design elements only, similar to a design template) on the local machine on which the design analysis is being performed.  The intent of this feature is to allow for consultants and other migration personnel to be able to view the full database designs even while they are disconnected from the production environment, which is particularly important on large analysis projects where in-depth manual design analysis is required.  The location of these databases is controlled by a setting on the Analysis tab of your Global Options dialog, and defaults to a folder in the tool’s <ProgramData> area.  Users can the easily open the Local Design Copy from any database view.

Classify by Last Used (All Replicas) – This enhancement expands the available options for automatically determining which Technical Class or Business class a databases belongs to.  Now you create a rule for recognizing class members based on when it was last used across all known replicas.  For example, you can create a class that groups all databases with a Last Used date greater than 356 days ago.

Import data into repository from CSV files – This enhancement allows users to read in records from a CSV file and update vales in certain Quest Repository database records.  The tool is available on the main Notes Migrator for SharePoint node.  First the user is prompted to select a CSV file and then a mapping dialog is displayed.  For each column in the CSV file, the user can choose to map it to one of the available database record properties.  Not all database properties can be imported from external data sources.  The intention here is that users who perform manual analysis/triage projects using spreadsheets or external tools can import that data back into the Migration Console.

This feature can also be used to add new database records into the repository (by Server and File Path, Replica ID, or Database Key).  The intention here is to allow users to import a list of databases to be analyzed or migrated.  Users would typically follow up such an import with a full analysis of those databases to populate the remaining database properties.

General

Performance and scalability for Migration Console – The database views have been re-architected to support 60,000+ databases at a time.  With a very large repository, users may experience a delay while starting the tool as all the records are loaded into memory.  After that, scrolling, sorting and filtering database views and opening additional views should be very fast.  Special protections have also been added to prevent you from running very large reports that are likely to crash the migration console.

New User/Group Mapping options – When performing user/group name mapping, the Output Translation option now allows you to further transform the name that results from your name lookup before submitting that name for resolution in SharePoint.  This may be useful when your environment requires specific name formats that are not immediately available in your mapping source.

Also, the Test User/Group Mapping tool now has a Validate in SharePoint button which will try to resolve the name that your configured mapping process produces so you can verify that it really works in SharePoint. This should make experimenting with and debugging various user mapping options a little easier for everyone.  Note that this capability is only available when using client-side user mapping (not when configuring server-side mapping in the Import Service).

Improved CBA/FBA support – Connections to SharePoint sites using Forms Based Authentication now automatically renew cookies as needed during long migration jobs and other operations.  The tool will routinely check the expiration time of the authentication tokens that it holds for the client and, if a token is due expire within a certain window, it will force a new authentication.  (The time limit will be 30 minutes, but this can be changed in your SharePoint Environment settings.)  Depending on your particular authentication system, this may appear to the user as a browser prompt forcing the user to re-authenticate.  In other cases, it may appear as a browser window that opens briefly and then closes again.

Windows Authentication using alternate account for Link Tracking Database – One new connection option is available for connection to the Link Tracking Database.  You can now specify that you want to use Windows Authentication, but supply an account other than your own.

Bulk Editing of certain database / class / job properties – Expanding on the tool’s capability to select multiple databases and set properties in bulk, you can now set a number of additional properties in a large number of selected databases.  You can even set certain properties inside the migration jobs assigned to the selected databases.  Finally, you now have a similar set of options for Technical Classes and Business Classes as well.

Usability improvements – A number of things have changed in the product to improve to make the tool easier to use, including rearrangement of dialogs and additions of menus.  More pop-up help icons and more context sensitive links to help topics have been added.  A completely rebuilt “Add/Remove Columns” dialog and the built-in documentation describing the 170 possible built in columns makes customizing views much easier.

Note that this list is probably way more than anyone would want to include in any one evaluation project.  My suggestion is to take this as a list of possible items to consider and then select which points will be most important to your users and your particular applications. 

General

• Tool performs complete pre-migration analysis
• Tool can be installed and run without consultant intervention
• Analysis functionality is fully integrated with the migration tool (flowing smoothly from pre-migration analysis, detailed analysis and application consolidation, project management, assignment of targets, design of migration jobs, automated provisioning and bulk migration based on analysis results)
• Tool facilitates migration project costing with the ability to track estimates for individual applications as well as  consolidated application designs
• Tool supports migration to SharePoint 2007 and 2010
• Includes option to migrate over native SharePoint 2010 web services, without installing any vendor code on SharePoint server
• Includes option to migrate over vendor’s web service optimized for high performance migrations
• Tool supports migration to Office 365 (SharePoint Online)
• Supports migration to Office 365 standard (multi-tenant)
• Support migrating to Office 365 Dedicated via an on-premises staging environment
• Supports direct migration to Office 365 Dedicated
• Tool includes a Command Line utility for scripting migration
• Tool supports migrating to SQL Server, including data normalization, rich text, images, attachments, doc links
• Tool supports migrating to the file system
• Supports generating XML files from Notes content
• Supports exporting file attachments, etc. to file system
• Supports generating files in the file system (HTML, Word, PDF)

Core Content Migration Details

• Supports mapping Notes data to any SharePoint column
• Migrate from Notes items
• Transform data at migration time using formulas
• Tool can migrate to SharePoint choice columns
• Includes option to add missing values to column schema as needed
• Tool can migrate Notes names to User columns
• Tool can preserve Notes document metadata
• Preserves Created/Modified dates
• Preserves Created By/Modified By identities
• Tool supports migrating Notes rich text with full fidelity
• Preserves fonts, table, nested tables, bullets, margins, etc.
• Preserves embedded images
• Preserves embedded image resources
• Converts embedded OLE objects to equivalent file type
• Migrates embedded attachments
• Migrates document level attachments
• Preserves collapsible sections and section headers
• Tool supports full provisioning of security constructs
• Provides several options for mapping Notes names to SharePoint (AD) names
• Maps ACL permissions to either the site level or the list/library level
• Can set explicit permissions for SharePoint objects based on Notes ACL, including support for custom permission levels
• Can add users to the existing site security groups based on Notes ACL, including custom site groups
• Can provision and populate SharePoint Groups from Notes ACL roles
• Can provision and populate SharePoint Groups from Domino directory groups
• Tool supports incremental migration
• Can rerun job, detecting new and changed documents
• Can write modified documents as new SharePoint versions
• Tool supports migrating Notes calendars to SharePoint calendars
• Supports repeating meetings, all day events, etc.
• Tool supports for migrating Notes discussions to SharePoint discussions lists
• Supports threaded discussion
• Preserves subject fields of response documents
• Offers optional custom web part for presenting discussion lists with a more Notes-like user interface
• Tool correctly handles Notes doc links and HTTP links
• Preserve links between documents in different applications at different times
• Links can work between all types of migration targets (lists, pages, etc.)
• Intra-document HTTP links (in QuickPlace or other Domino web-enabled apps) are recognized as doc links and translated accordingly
• Link tracking system that continuously manages doc links as content moves through staging, deployment and production
• Link tracking system allows finalization (replacing dynamic links with permanent links) after the migration is complete (even on SharePoint Online)
• If company also provides mail migration technology, are links preserved between migrated mailboxes in Exchange and migrated applications in SharePoint?
• Tool can provision sites, list and libraries using custom SharePoint templates

Advanced Content Migration Details

• Tool provides a sufficient choice of migration SharePoint migration targets to accommodate various business and end-user application requirements:
• Migrate to List Items
• Migrate files to Document Libraries
• Generate generic Word documents
• Generate Word documents using custom templates, properties and content controls
• Generate PDF documents
• Migrate to Wiki pages
• Migrate to Basic pages
• Migrate to Publishing pages (Other tools advertise advertises this but is very limited)
• Migrate to Web Part pages, mapping Notes content to any property on any web part
• Tool can render complex Notes Documents into rich text (for archiving purposes)
• Tool can render entire Notes documents with their original Notes form to a single rich text column or generated rich text document
• Tool can render entire Notes documents with a designated form to a single rich text column or generated rich text document
• Tool supports mapping document approval/publishing status from Notes data to the out-of-box approval/publishing feature in SharePoint
• Tool can migrate Notes content to SharePoint 2010 Managed Metadata columns
• Support matching terms by alias or locale
• Support matching terms by hierarchy
• Supports adding missing terms to term store
• Tool supports SharePoint 2010 Document Sets
• Individual Notes document can be mapped to individual doc set (splitting out all the generate files, attachments, etc., as members of the doc set)
• Multiple related Notes documents can be merged into a single doc set
• Tool can support data normalization
• Embedded images, attachments and objects can be normalized to separate SharePoint libraries or folders (keeping the various parts linked)
• Documents with multi-valued items can be normalized into header and detail documents
• Documents with tables of related items can be normalized into header and detail documents
• Tool can dynamically set content types based on data in the Notes document
• Tool can migrate to InfoPath form libraries
• Generates documents according to any XML schema
• Supports rich text, embedded images, attachments
• Supports migrating multi-valued items to repeating XML elements
• Supports user (people picker) fields

Design Migration Details

• Tool supports extracting the schema of a Notes application and provisioning  a similar schema in SharePoint lists and libraries
• Can determine schema based on Notes forms
• Can determine schema based on sampled Notes documents
• Tool supports extracting the schema of a Notes application and provisioning  a similar schema as SharePoint Content Types
• Can also push these content types into specific lists and libraries as they are provisioned
• Tool can provision new columns in new or existing lists and libraries
• Including choice and lookup columns
• Including data validation, required field, and other standard column options
• Tool can generate “classic” InfoPath Document Form templates (for use in SharePoint form libraries)
• Includes form layout for form and all mappable field types
• Includes rich text and attachment areas
• Includes option to generate InfoPath sections for area with hide-when logic
• Includes special handling for Notes static subforms and computed subforms
• Provides a detailed report itemizing whatever elements could not be migrated
• Tool can generate InfoPath List Forms (new with SharePoint 2010) from existing Notes forms
• Tool can provision SharePoint Views based on Notes views
• Includes a migration wizard allowing users to define computed columns, etc., where needed
• Tool includes support for consolidating applications with similar designs and automating their migration
• Recognize class members using template names
• Recognize class members using full design comparison

QuickR / QuickPlace Details

• Tool automates the provisioning of SharePoint sites based on the QuickR / QuickPlace room hierarchy
• Each sub-room is mapped to a SharePoint sub-site
• Uses SharePoint Team templates or custom site templates
• Preserves the access control settings of each room and sub-room
• Tool migrates all types of QuickR / QuickPlace pages
• Migrates all standard page types: Imported pages, Link pages, Discussion pages, Task pages
• Migrates custom Page Types, including custom Fields
• Offers migration of Published documents, Unpublished documents, or both
• Offers migration of “orphan” documents that are accessible through navigation hierarchy
• Tool correctly migrates rich text in QuickR / QuickPlace pages
• Full rich text fidelity is preserved
• Embedded images are retained
• URL links that point to other QuickR / QuickPlace pages are converted to SharePoint links
• Preserves document level permissions
• Tool preserves QuickR / QuickPlace navigation
• Converts place menus to SharePoint QuickLaunch area
• Tool includes pre-migration analysis features that are QuickR / QuickPlace aware
• Excludes configuration documents from data analysis
• Summarizes data documents by Page Type used in each room
• Includes configuration documents in design analysis
• Detects rooms where custom Page Types and Fields have been defined by end users

Analysis Details

• Tool performs application usage analysis
• Includes exclusion of designated user names who should not count as real users
• Can aggregate usage information across multiple replicas of each database
• Tool performs Data analysis, finding patterns of actual usage in a particular database
• Includes detection of blocked file attachment extensions and oversized files that will not be allowed on SharePoint
• Includes analysis by Form Used, making it easy to extract the “document types” actually used in a database instance
• Tool performs Design analysis,  summarizing design element details
• Includes initial complexity calculations
• Tool can compares all application designs to a predetermined set of templates, which assists in  consolidating applications with similar designs and automating their migration
• Tool can capture design copies of each database while scanning the environment 
• Tool can extract all users and group names contained in a set of databases (ACLs, document metadata, usage history, etc.) making it easy to proactively plan for how they will map to SharePoint
• Data repository is an open format that customers are free to use in any way they see fit
• All analysis details may be exported to external format such as CSV or XML for use with other reporting tools such as Microsoft Excel

Company

• Describe track record of delivering top-notch support around the world
• Support call centers located globally for 24×7 coverage
• Many counties are staffed with presales and post-sales consultants
• Company offers well-defined SLA’s including policies for escalating to development
• Company frequently delivers feature enhancements to unblock large migration projects
• Company has tools for moving content from SharePoint to SharePoint (upgrades, reorganization, deployment to production) and well as from other data sources to SharePoint
• Company has related tools for managing SharePoint environments, including discovery, reporting, policy enforcement, and granular recovery
• Company also has tools for performing Notes-to-Exchange migrations and directory migrations
• Company offers a set of advanced web parts for reducing the time and cost of rebuilding complex custom applications
• Company has an experienced professional services team to participate in and/or deliver migration projects to ensure project success
• Company has an experienced partner network able to deliver migration projects.  For large Notes projects this should include partners with off-shore resources who’s teams utilize tool in a migration factory approach to deliver high-volume, low-cost migrations
• Company has an established track record in this unique migration space.  Company is able to provide case studies, project references, best practices materials, facilitate POCs, etc.

• NMSP overview
• Migrating standard template databases
• Migrating custom database content
• Managing document links
• Mapping security permissions
• User/group mapping options
• Transforming data with formulas
• Migrating to Wiki pages
• Rendering and archiving documents

Session 2: Analysis and Automation with the NMSP Migration Console
[view recording]

• First time Configuration Wizard
• Database discovery
• Usage analysis, data analysis
• Introduction to design analysis and application complexity
• Classifying and consolidating applications
• Utilizing console views and reports
• Exporting data for external reporting
• Importing data into the repository
• Provisioning SharePoint sites
• Running migration jobs from the console
• Automated provisioning and migration

Session 3: Advanced Content Migration Jobs
[view recording]

• Overriding Document Metadata
• Working with Lookups and Managed Metadata
• Migrating images/attachments to alternate Libraries
• Dealing with multi-valued items
• Normalizing multi-valued items to multiple documents
• Working with Content Types
• Dealing with Response documents
• Generating Microsoft Word and PDF documents
• Setting links to parent documents

 Session 4: Tool Deployment, Domino.Doc and QuickPlace/QuickR migrations
[view recording]

• Understanding tool deployment options
• Migrating via SharePoint 2010 Web Services
• Migrating via the NMSP Import Service
• Installing and configuring the Import Service
• QuickPlace/QuickR migration jobs
• Automated QuickPlace/QuickR migrations
• Domino.Doc migration jobs
• Automated Domino.Doc migrations

 Session 5: Migrating Application Designs 
[view recording]

• Overview of design migration capabilities (and limitations)
• Migrating Notes schema to custom lists
• Migrating Notes schema to Content Types
• Advanced SharePoint column provisioning
• Migrating Notes forms to InfoPath list forms
• Migrating Notes forms to InfoPath form libraries
• Migrating Notes views to SharePoint views

Session 6: Tips and Tricks for Managing Large Migration Projects
[view recording]

• Design analysis revisited
• Capturing copies of application designs during analysis
• Blending tool and manual analysis
• Rethinking application complexity
• Triaging value of applications
• Working with business owners
• Managing the migration process
• Managing doc links
• Using Intermediate files
• Migrating with the NMSPCMD.EXE command line 

Session 7: Even More Advanced Content Migration Jobs
[view recording]

• Working with Document Sets
• Migrating to Wiki and Basic Pages
• Migrating to Web Part Pages
• Migrating to Publishing Pages
• Migrating to InfoPath Form Libraries
• Introduction to SQL Server Migrations

Here is a walkthrough of how to create a small empty Notes database with just one document in it.

1. In the Notes client, select the Notes documents you want to send to Quest and copy them to the clipboard (Ctrl-C).

2. In the Notes client, create a new database (Ctrl-N).  Specify a title and a file location on your local machine.  (You may want to specify your Desktop or some other folder you can easily locate later.)  Specify that you want to use the –Blank– template, and double check that you are not locally encrypting the database. 

3. When the new database opens up, paste the documents you copied in step 1 (Ctrl-V).

Note that the default view in the “blank” database will not show any columns (except the document number) and you will not be able to open the documents here.  But the data documents will be there and that should be enough for Quest to test the migration job.  If you want to, you can verify that you got the right documents using Document Properties (Alt-Enter).

4. Make sure that the database will be readable by Quest support by going to Database -> Access Control (Notes version 7 or earlier) or Application -> Access Control (Notes 8 or later). On the Basics tab, select the –Default– user and make sure that the Access level is set to “Manager”. On the Advanced tab, make sure that “Enforce a consistent ACL” option is NOT checked.

5. Close the database in the Notes client and locate the NSF database in the file system (in the folder you specified in step 2). This database should be very small (512 K plus the size of the document you copied) and you can probably email it “as is” or you can encode it inside a ZIP file.

75% of the presentation was about the concepts in Ira’s book for “Creating Enterprise Class Applications in SharePoint without Code”.  The rest was me trying to add the Notes migration perspective.  I thought the combination was very good and we had some good Q&A.

The webcast recording is here: http://www.quest.com/webcast-ondemand/-migrating-notes-applications-to-sharepoint-with-fewer-development-res816018.aspx. 

PS:  If you want to get a copy of Ira’s book for yourself, go to www.ihfpublishing.com and use coupon code “QUESTDISC” for a 30% discount.

Design Migration

• Migrate Notes Views to SharePoint Views
• Content Type Generation
• New Column Provisioning Options
• Provision Calculated columns
• Provision Lookup Fields

Content Migration

• Migrate by Form Used
• Improved Content Type Support in Migration Jobs
• Normalize multi-valued items to multiple documents
• Dynamic link tracking for URL columns
• New Run Job options
• Provision Alternate Libraries

Analysis / Migration Console

• Capture Design Copies during Analysis
• Classify by Last Used (All Replicas)
• Import data into repository from CSV files

General

• Performance and scalability for Migration Console
• New User/Group Mapping options
• Improved CBA/FBA support
• Windows Authentication using alternate account for Link Tracking
• Bulk Editing of certain database / class / job properties
• Usability improvements

Once again, the beta will be managed on the new SharePoint for All community site.  If you would like to participate in the beta program, go to http://communities.quest.com/groups/notes-migration-product-beta-group.  Sign in with your Quest Community ID, or register to create a new one.  Then press the “Ask To Join This Group” button.

One of the site owners will review your request and will typically approve it the same day.  You will receive a notification and then get full access to technical content and (of course) the beta build itself.

Quest Support will not be able to help you with this version until it releases, so please use the group’s Discussion area for any questions, problems or suggestions.