The document outlines a comprehensive migration roadmap for organizations transitioning from Lotus Notes, emphasizing detailed planning, stakeholder engagement, and the importance of pilot programs to understand usability and challenges. It highlights opportunities for consolidation, seamless integration, and future-readiness through careful selection of technologies and design processes. Additionally, the document emphasizes the need for effective risk management and change management to ensure successful migration and adoption.

1. © Copyright Maarga Systems, 2015. All rights reserved. No content of this
presentation, either in full or in part, may be reproduced without the
express permission of Maarga Systems.
Lotus Notes Application Migration
Gayathri V | CTO

2. AGENDA
• Migration Roadmap
• Plan & Prepare
• Prototype/PoC
• Piloting
• Migration & Closeout
• Opportunities & Benefits
• Check-List

3. Roadmap
Clean up legacy
infrastructure
End User
Training
Learnings,
Documentation
CLOSEOUT
Planned,
Controlled ,
Gradual
Migration
Intermediate
Milestones
Implement
Envisaged
Process Changes
MIGRATE
Detailed Feature
Planning
Tool Based
Migration
Additional
Development,
Customizations
Security
Configuration,
Modelling
Migrate Data
Staging and User
Acceptance
Testing,
Feedback
Transition to
Support
Update Plan
PILOT
Prototypes
Finalize Target
Platform
Finalize
Migration
Approach
Detailed Project
Planning
PLAN & POC
Initiation
Meeting
Domino
Migration Terrain
Workshop
Application
Portfolio
Inventory &
Analysis
Stakeholder
Survey
Create the
Business Case
Create Goals and
Project Charter
Risks &
Mitigation
PREPARE

4. Understand, Plan & Prepare
Choose
Platform
Organization’s
size, existing
technologies,
future plans,
application
complexity,
everything needs
to be looked at
Identify and
Consult
Stakeholders
It is essential to
ensure that all
stakeholders are in
on the migration
plan.
Rationalize
Portfolio
Maarga’s Portfolio
Analyzer tool can
assess and advise
how to rationalize
your application
portfolio before
migration.
Plan
Create a detailed
plan for the
portfolio. Can be
based on
business unit,
critical
applications etc.
AGILE model
works best
Explore the
Scope for
Tools
How much of
the portfolio
can be
migrated with
tools? How
many standard
templates?
How much
customization?
How complex?

5. Prototype & Plan
Ability to
Demonstrate
Familiarizes one
with the complete
range of a
solution’s
capabilities and
provides hands-
on experience to
managers, IT
personnel, and
users.
Quick
Turnaround
A POC can be set
up fairly quickly.
This can bring
down the decision
making time as a
lot of features
and usability
issues can be
tried first hand.
Foresee
Challenges
Vendor support
quality,
Limitations of
target platform,
Technical
problems, etc. can
be foreseen.
Bring
Stakeholders on
Board
Gives the
opportunity to
demonstrate the
product’s benefits
to upper
management and
reinforce data on
Return on
Investment
A proof of concept
enables you to
determine whether a
solution is
appropriate for your
organization’s needs
and goals.

6. Gather Momentum with Pilot
Understand
Environmental
Challenges
Familiarizes one
with the complete
range of a
solution’s
capabilities and
provides hands-
on experience to
managers, IT
personnel, and
users.
Plan for
Adoption
A Pilot can be set
up fairly quickly.
This can bring
down the decision
making time as a
lot of features
and usability
issues can be
tried first hand.
Estimate
Accurately
Vendor support
quality,
Limitations of
target platform,
Technical
problems, etc can
be foreseen.
Get
Endorsement
Gives the
opportunity to
demonstrate the
product’s benefits
to upper
management and
reinforce data on
Return on
Investment
Pilot to
understand all
the realities on
the ground

7. Migration
Planned, Controlled ,
Gradual Migration
Advance though
Intermediate Milestones
Implement Envisaged
Process Changes

8. Close Out
Plethora of Apps
and Tools
Moving from a
legacy system
also needs
managing and
phasing out a ton
of apps and tools
that are left
behind
Redundancy
from
Consolidation
Redundancy
could be due to
apps developed in
geographical or
departmental
silos. It takes
planned effort to
identify,
consolidate and
move out of
redundant
applications
created from
same Notes
template.
Data Cleaning
Great information
is often trapped
Re-chunking
improves data
usability.
Free data tied to
tools or
technologies.
Poor data quality is
a primary reason
for 40% of all
business initiatives
failing to achieve
their targeted
benefits. (Gartner
- Measuring the
Business Value of
Data Quality,
2011)
Free up
infrastructure
Efficiency gained
during migration
will be maximized
by simultaneously
freeing tied up
infrastructure.

9. Final Words
About Maarga & a Reminder

10. Opportunities & Benefits
Consolidate
This is an
opportunity to
consolidate your
existing suite of
applications.
Integrate
Seamlessly
Move out systems
which are operating in
silos. Seamless
integration can be
brought forth with
careful planning and
choice of
technologies.
Redesign
Processes
Redesign
processes that
have not changed
in years due to
being tied to
legacy systems.
Reduce
Operating Cost
Add supporting
statistical
and research
information
as an appendix for
readers who want a
deep dive.
Collaborate
Better
Businesses are
moving to a world
where email will be
effectively replaced
with collaboration
tools. Ensure future
readiness by planning
and moving towards
better collaboration of
your global workforce,
today.
Leverage New
Technology
Link to in-depth
materials (forums,
discussion boards,
white papers) for
readers
who want to research
further.
Build For the
Next Decade
Cite resources and
give credit to your
sourced authors so
readers can gain more
insights.
Migrating from Lotus Notes is huge and challenging. And beyond challenges lie worthy prizes. Maarga
helps organizations to capitalize the host of promising possibilities that arise from a rebuilding exercise

11. Watch Out!
Protect Stakeholders
End Users:
Productivity
Training and Adoption
Time for adoption
Decision Makers:
Cost and Time for
Migration
Return On Investment
IT Team:
Availability of capable
developers
Retraining and
Redeployment
Additional Workload
Transition
Two Decades with Notes
Organic Growth:
Complexity
Scale
Siloed Growth
Plethora of Apps
Pressure on
Infrastructure
Entire systems to have two
versions during migration
Like for Like Migration?
Staged Migration?
Future Technology Stack
Shortfalls of Target
Environment:
Workflow capability
Scale and Data Volume
Offline Capability
Lists and Forms
Lack of Enterprise Focus
Seamless Integration
Future and
Consolidation:
Existing Technologies in
the organization
Tool and Skill availability
Strategic Relevance
Here is
the list of
things to
be wary
of while
planning
migration
from
Lotus
Notes

12. Maarga Capabilities
Code Assets
and
Frameworks
-XMAP
-Portfolio
Analyzer
-Third party
tools through
partnerships
Partnerships
-IBM
-Dell Quest
-Gupta
Technologies
Expertise
-10+ years of Notes
-Availability of
resources familiar
with both
technologies
-In-house tools and
proven automation
capabilities
Risk
Management
-Ensure
availability of
both platforms till
the new apps
stabilize
-Accurate
estimation
through pilot
Change
Management
-Maarga’s
adoption
approach
-Specialized
Adoption
Manager
-End user training
Gamification
Capable
Architects
-Experienced
technology
architects
-Expertise in
BPM
-In-house
expertise in
multiple
technology
stacks
Scaled up Team
-With Excellent
Lotus Skills that
differentiates us
from 1-2 people
boutiques with
exceptional skills
or from 100,000
people factories
with poor skills

13. © Copyright Maarga Systems, 2015. All rights reserved. No content of this
presentation, either in full or in part, may be reproduced without the
express permission of Maarga Systems.
Thank You
sales@maargasystems.com
www.maargasystems.com