Migrating Collaboration to the Cloud & Mobile

Risks, Cost & Payoff

5 Takeaways

#1: The best collaboration platform is the one with no users!

Users, NOT technology are the largest contributors to risk. User behavior can increase cost and WILL migrate to the new platform, whether Email, Web, Cloud or Mobile, if not identified and modified quickly!

Example: Did you know that less than 1% of users are responsible for 4% of the email messages that account for 80% of the cost of email?

#2: Walking away from an existing platform can cost up to 6X more

Migrating to a new platform can increase cost and risk by up to 6X more and deliver lower returns.

Example: Large collaboration environment at one of the largest development banks in the world. Only 5% of Notes of databases needed to be considered for partial design migration to XPages. Whereas, over 30% of Notes databases need to be considered for complete design and data migration, for migrating to a different platform!

#3: Maximize bang for the buck – Use “Responsive & Extensible” design

Applications need to be extensible in the future. For example, Bootstrap implementation is a great way to provide a natural path to mobility and extend application usability to multiple devices.

#4: Automate the journey and achieve scale!

Pilots are not representative and provide a false impression that XPages or Mobile migration will not scale to large projects. Using established processes, standards, best practices and automation can save up to 90% of the cost and time.

Example: “HCL Trouble Tickets” application

    • Manual conversion - An “experienced” XPages developer, with “NO” understanding of application functionality – 8 person days. An “experienced” XPages developer, with a “COMPLETE” understanding of application functionality – 5 person days.

    • Automated Conversion using XPager - A “fresh” XPages developer, with “NO” understanding of application functionality – 0.5 person day .

#5: Going Mobile – Simple but IMPORTANT lessons

  • Less is more. Start mobile enabling what your users need most.

  • The Phone is not a Tablet. Design to meet the needs of users of both devices.