Many of the IBM Notes customers are switching over to Microsoft SharePoint for their team rooms, discussions, document libraries, and many other custom applications. While this exodus off of Notes has been happening over the past decade, it has become more of a custom in the past year. As an IT Manager owning the migration project, it is imperative that you plan a detailed approach of migration that includes methodology, tools & decide on what to migrate before embarking on this endeavor. Learn about: ● Application analysis methodology ● Migrate/Develop in SharePoint ● Tools to Migrate ● Checklist for Migration ● Pilot Process

1. © Copyright Maarga Systems, 2017. All rights reserved. No content of
this presentation, either in full or in part, may be reproduced without
the express permission of Maarga Systems.
Migrating Lotus applications to SharePoint:
Preparations and Analysis

2. Presenters
Gayathri Vishwanathan| VP Delivery
gayathri@maargasystems.com
@g3vish
© Copyright Maarga Systems, 2017. All rights reserved.2
Rekha Vadivelu | SME, Notes Migration
rekha_v@maargasystems.com
@rekhavadivelu

3. Maarga – An Introduction
© Copyright Maarga Systems, 2017. All rights reserved.3
Presence
Offices in India, USA.
Customers also in
Europe, Middle East,
Asia Pacific and UK
Pathfinder
Maarga literally means
Pathfinder. A leading
provider of enterprise
collaboration and
communications
solutions since 2002
Adroit & Competent
Over 70 consultants
with strong
domain and technology
skills. Aligned with ISO
and CMMi quality and
process excellence
frameworks
Superior Experience
Superior experience in
Web, XPages
Technology, Mobility,
Workflow Automation
and expertise in Lotus
Notes Development
IBM Partner
Premier IBM partner
with skills on Lotus
Notes / Domino, Quickr,
Social Software

4. Poll 1
• Where are you in your overall migration journey?
– Preparing to migrate
– Mails migrated, application strategy being worked out
– Mail migrated, application migration in progress
– Mails and applications migrated, rollouts in progress

5. Agenda
Why Analysis
Applications analysis Methodology
Migrate / Develop
Tools
Challenges

6. Why Analysis ?
Overall timeline Overall Cost
Risks Typical Challenges

7. Factors
Usage Complexity Dependencies

8. Usage Analysis in Detail
Consolidated
databases from
catalog.nsf on all
servers
Identified Unique
Replicas
Filtered out Test,
Backups, Old
Version, Domino
Templates
Filter out
Archives, Logs,
Dev dbs
Filter out
Instances
Filtered out
Mail Dbs
Filtered out
Activity, Admin,
Audit, Stats Dbs
Databases –
Consolidated List
Databases not
available In the
specified path
No of databases
to be ignored
(List given by
Admins/business)
FINAL LIST OF
DATABASES
ANALYZED

9. Archival Process
Identify apps to be archived
Designate a server to hold all archived apps
On request, restoration should be possible
A thorough testing required in restoring the archival database
SOP to be defined for archival procedure

10. Usage Analysis Challenges
Lotus
Notes
Dev/
Support
team
SME
migration
Business
Team / IT
Ignore unused
functions/modules
Archiving Dependencies
Rarely used apps but vital
Identify common usage

11. Complexity AnalysisLow
• 1-2 Forms
• 4 Views
• 1 Agent
Medium
• 4-10 Forms
• 100 Views
• 30 Agents,
outlines
• 2-3 Script
Libraries
High
• 10-20 Forms +
• 50 Views +
• Multiple Script
Libraries
• Multiple Internal
& External
Dependencies

12. Complexity Analysis Challenges
Decide
not by
design
Interfaces
Internal and
External
Dependency
Group
apps with
small
difference
Complexity
Lotus
Notes
Dev/Sup
port
team
Tools
SME
migratio
n

13. Poll 2
What dependency do you think might be
challenging during migration?
- Stakeholders availability
- Third party /vendors involvement
- Other technical team participation/inputs

14. Dependency Analysis
Dependencies
LEI jobs
Web services
Embedded language
scripts
External
dependency
(Import data from
diff sources)
Internal
dependency
(Lookups)

15. Dependency Analysis Challenges
Manual analysis
takes time
Availability of
other teams
Lack of
environment to
test
No
documentation
/ trace exist
Lotus
Notes
Dev/
Support
Team
Other
Tech
Teams
Architects

16. Migration Challenges
Computed for
display fields
Scheduled
Agents
Search /Advanced
Search
Attachments
Subforms
Date & Time

17. Examples
Low complex
app
• Cost -x
• Timeline:
• Requirement gathering – 1
day
• Migration – 1 day
(template based)
• Review – 1 day
• Challenges:
• 1-2 Days of IT Involvement
• 1 Day of Business
Involvement
• Risks:
• Internal lookups
Medium
complex app
• Cost – XX
• Timeline:
• Requirement gathering – 2
days
• Migration – 3
days(template based)
• Review – 2 days
• Challenges:
• 3-4 Days IT Involvement
• 1-2 Days of Business
involvement
• Risks:
• External dependency
• Link between documents
High Complex
app
• Cost – XXX
• Timeline:
• Requirement gathering – 5
days
• Migration/Re-development
– complexity based
• Review – 1 week
• Challenges:
• 7-9 of Days IT Involvement
• 3-4 Days of Business
Involvement
• Risks:
• Web services
• Scheduler Jobs
• Import from other sources

18. Upcoming Webinars
Other Upcoming Webinars
1. IBM Connections 6 - Features That Increase End User Adoption
2. Modernize IBM Notes Applications with JavaScript Framework
3. Driving Business Value Through IBM Connections – Use Case Led Adoption Techniques
NextWebinar

19. Questions ?