Export (0) Print
Expand All

Application Coexistence and Migration

 

Topic Last Modified: 2006-09-14

Microsoft has developed a methodology for categorizing Lotus Domino applications based on whether the application incorporates workflow or back-end connectivity, and whether the application was created from a default Domino template (.NTF file) that ships with Lotus Domino. These criteria determine whether the application should be migrated using the Microsoft Domino Data Migration tool, requires other tools/functionality, or is best left on the Domino platform. Figure 1 shows how Microsoft categorizes Lotus Notes/Domino applications, based on whether the application was created from a standard Lotus Domino template, and if the application includes connectivity to other sources or workflow.

Figure 1   Application Framework (Quadrants)

Application Framework (Quadrants)

In classifying Domino applications, consider the following four criteria:

  • Data-centric   Applications primarily focus on collecting and sharing data. There is no workflow or connectivity to other applications or databases in this type of application. These applications are relatively straightforward to migrate because they require migration of data to an application on the Microsoft side that has corresponding fields and forms.

  • Process-centric   Applications that incorporate workflow or back-end connectivity to other applications or databases. These applications are more difficult to migrate because the logic and process must be re-created to migrate the applications.

  • Template-based   Applications created from the default Lotus Domino templates that are installed on a Domino server during the server installation.

  • Custom   Applications are either template-based applications that have been modified to contain additional fields, or applications that were created from the "blank" template.

When you create an application from a standard Domino template and do not modify it, it is relatively straightforward to anticipate the application fields, field types, and application purpose, and then map this information to the Microsoft collaboration products. Any application that you created from a standard Domino template and did not modify is a prime candidate for migration.

Lotus Domino ships with many default templates. Several of these templates are used for administering the Domino servers and the Domino infrastructure. Databases created from these templates are not considered for migration.

The following table lists the templates that ship with Lotus Domino R5 and 6.

Table 1   Templates that ship with Lotus Domino R5 and R6

Lotus default template Associated Microsoft Windows SharePoint Services template

SmartSuite Library

Document Library

Document Library

Document Library

Microsoft Office Library

Document Library

TeamRoom

Team Work Site

Discussion

Discussion Database

Quadrant 1 applications are data-centric and template-based.

Examples:

  • Applications based on the Discussion Template

Solution:

  • Use Microsoft Application Migrator 2006 for Lotus Domino to migrate data to the associated Windows SharePoint Services template.

Quadrant 1 applications are process-centric and template-based.

Examples:

  • Applications based on the Document Library Template

  • Applications based on the Microsoft Office Library Template

  • Applications based on the SmartSuite Library Template

  • Applications based on the Team Room Template

Solution:

  • Use Microsoft Application Migrator 2006 for Lotus Domino to migrate data to the associated Windows SharePoint Services template. If workflow functionality is required, integrate third-party workflow solutions or Windows Workflow.

Use Microsoft Application Migrator 2006 for Lotus Domino, or consider using a third-party tool to migrate the application:

  • Any application that was not created from a default Lotus Domino template.

  • Any application that was created from a template but was modified to contain additional fields or data that need to be migrated.

Alternatively, you can use functionality such as Web services to integrate the data between Lotus Domino and Windows SharePoint Services.

Quadrant 3 applications are data-centric and were created from the blank template, or were based on a standard Lotus Domino template and then modified to contain additional fields.

Example:

  • Applications based on default Lotus Domino templates that contain additional fields or data that need to be migrated.

  • Custom data-centric applications that were not created from default Lotus Domino templates, such as client information.

Solutions:

Quadrant 4 applications are process-centric and were created from the blank template, or were based on a standard Lotus Domino template and then modified to contain additional fields.

Examples:

  • Applications based on default Lotus Domino templates that contain additional fields or data that need to be migrated, such as a Discussion that has been modified to include a group or team name field.

    • Custom applications that incorporate workflow, such as expense reporting.

Solutions:

Microsoft has developed many templates that can be used with Windows SharePoint Services. These templates should prove to be helpful both when you migrate Domino databases to Windows SharePoint Services and when you create new SharePoint Portal Server sites.

For more information about these templates and to download them, see Applications for Windows SharePoint Services. New templates are regularly created and added to the Web site.

For more information about analyzing and understanding Lotus Notes applications, see Application Analysis Envisioning Framework.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft