3-18-11
- 4. Lotus Notes to Force.com
- 7. Assuming this... ...while customers do this
- 11. Easier To Use ‣ User Experience Modeled after the “consumer web”
- 13. Faster Development Cycle ‣ Nimble to meet business needs ‣ Reduce IT debt Actual CoC Cost of Change (CoC) Technical Product Debt Release 1 2 3 4 5 6 7 8
- 15. Force.com Surpasses Notes /Java/.NET Productivity Force.com has 5 times faster development capability than .NET/Java, while Lotus Notes does just 2 times faster than .NET by independent research. “76% to 85% less development time. 54% reduction in 3 year TCO” “80% less development time. 50% cost reduction” “80% less development time. 50% cost reduction”
- 17. Robust Integration Mash-ups from Native Integration Native ERP Developer Web and Desktop Partner Connectors Toolkits AppExchange Connectors Ecosystem
- 19. Less Expensive Less Capital Expenditure (CAPEX) ‣ No Hardware ‣ No Software ‣ Just Service Less Operating Expenditure (OPEX) ‣ Lower Administration & Support Cost ‣ No Maintenance Fees
- 21. Easier To Govern ‣ Centralized ‣ Multi-Tenant ‣ Granular Security Control
- 23. Force.com is a Better Way “Companies were able to reduce their three year TCO by 54%, saving $560,00 per application.” Open your Build your and let force.com browser... apps... worry about the rest
- 27. Architectures Side by Side ‣ Profile and role-based ‣ ACL/Document access ‣ Standard & Custom Objects ‣ Data Notes ‣ Field-level security/encryption ‣ Field-level encryption ‣ Page Layouts/Visualforce ‣ Design Notes ‣ Force.com IDE ‣ Domino Designer/IDE ‣ Formulas ‣ Formulas ‣ Buttons ‣ Buttons ‣ Workflow, triggers, validation rules ‣ Form view/Database event ‣ Apex, triggers & classes ‣ Agents ‣ Force.com Sites ‣ Public Web Apps ‣ Workflow, approval processes ‣ Workflow ‣ Apex2WSDL, Force.com ‣ Web Services web services API
- 29. Build the Build the Incorporate Migrate Legacy data model User Interface Business Logic Lotus Data
- 31. Lotus Notes Migration Challenges ‣ Organizations often do not know how many databases exist ‣ Often legacy databases are unsupported and lack documentation ‣ Complex security often obscures and hides data ‣ Migrations require both Force.com & Lotus expertise ‣ Volume of Notes databases makes it difficult to answer, “Where to begin?”
- 33. Value Proposition ‣ EscapeNotes provides automated assessment and migration technology ‣ Drastically reduces migration costs and time (1 month/app down to to several days) ‣ Easily identify where migration complexity resides ‣ Preserve value of legacy Notes data ‣ Core team includes members of the original Lotus Notes engineering team
- 35. Infrastructure Complexity ‣ Top 1% apps = 20% of the complexity ‣ Top 10% apps = 66% of the complexity ‣ 2% apps have code score > 5,000 ‣ 25% apps have complexity > 300 ‣ 15% apps have a score > 2000 As a benchmark, the Lotus standard R5 mail template, considered by most as complex, has a Design score of 300 and a Code Score of 2,000.
- 37. Ownership
- 39. Application Rationalization ‣ Tool rapidly identifies and profiles all Lotus applications within the enterprise ‣ Proprietary scoring algorithm baselines the complexity to migrate each application ‣ Identify which applications have the highest usage and by which users ‣ Determine the level of customization present in each application
- 41. Application Migration ‣ Automated Lotus applications & data migration to Force.com ‣ Ability to identify hidden Lotus data ‣ Visibility into custom Lotus Script and Agents ‣ Direct Lotus to Salesforce conversion preserves legacy
- 43. Escape From Notes Offering ‣ Escape From Notes Environment Analysis ‣ Detailed analysis of Applications, Server, and Security Models ‣ Migration Roadmap ‣ Assessment of Analysis including a migration approach and roadmap ‣ Identification of high value applications for migration ‣ Recommendations for consolidation and migration approach ‣ Meta Data Extract ‣ Consolidated view of Agents & Lotus Script
- 45. Deliverables
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: \n
- #51: \n
- #52: \n
- #53: \n
- #54: \n
- #55: \n
- #56: \n
- #57: \n
- #58: \n
- #59: \n
- #60: \n
- #61: \n
- #62: \n
- #63: \n
- #64: \n
- #65: \n
- #66: \n
- #67: \n
- #68: \n
- #69: \n
- #70: \n
- #71: \n
- #72: \n
- #73: \n
- #74: \n
- #75: \n
- #76: \n
- #77: \n
- #78: \n
- #79: \n
- #80: \n
- #81: \n
- #82: \n
- #83: \n
- #84: \n
- #85: \n
- #86: \n
- #87: \n
- #88: \n
- #89: \n
- #90: \n
- #91: \n
- #92: \n
- #93: \n
- #94: \n
- #95: \n
- #96: \n
- #97: \n
- #98: \n
- #99: \n
- #100: \n
- #101: \n
- #102: \n
- #103: \n
- #104: \n
- #105: \n
- #106: \n
- #107: \n
- #108: \n
- #109: \n
- #110: \n
- #111: \n
- #112: \n
- #113: \n
- #114: \n
- #115: \n
- #116: \n
- #117: \n