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
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
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
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
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
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