Migrating from Domino to Exchange 2010

21,328
-1

Published on

A Binary Tree Webinar: A Comprehensive Strategy for Migrating from Lotus Domino to Microsoft Exchange 2010

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
21,328
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
945
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • Key Success Factors for MigrationsTransparency of End-user ExperienceUsers must be able to continue performing their routine activities regardless of their migration state.CommunicationCommunication to users must be distributed in an easy to read, understand, and respond manner.Predictability and ManageabilityMigration activities must be completed in the expected amount of time.Complete and accurate report of results must be generated for easy review and broadcast.FlexibilitySpecial requirements must not become insurmountable obstacles.
  • Understanding the Challenges of MigrationThe wrong approach or the wrong tools can undermine your initiativePotential pitfalls of the wrong approach or wrong tools:A longer and more complex migration project due to improper up-front analysis and/or not streamlining the Domino environment prior to setting up coexistence and starting the migrationDeclines in the productivity and collaboration of your users and executives due to calendars and free/busy lookups that are out-of-sync The delay of key business processes due to the inability of Outlook users to see or act on Notes email-enabled applicationsMissing data from not selecting high-fidelity coexistence and migration tools
  • This slide is to give and overview and review each of the BT offerings. More detail will be covered throughout the day.
  • There are several consideration associated with Migrations to Microsoft Online (BPOS-S). Traditional on premise migrations provide the customer a higher sense of control and ownership of the process. This does require a significant investment into hardware, software, and staffing to manage the Exchange migration.With a hosted migration there is still a level of control provided to the customer but this almost entirely eliminates the customer investment of hardware, software, and staffing. For general migrations, an on premise migration may be suitable for a gradual migration from Domino to BPOS. For rapid migrations the only way to move forward would be through a Host migration.Rapid
  • Instructor Notes:
  • The Microsoft Hosted Migration approach to BPOS –D utilizes a hosted migration farm. Traditionally these migration farms are hosted on MSO migration workstations and migration software is managed by a partner. As a result there is:No hardware to purchaseNo software to purchaseNo software to install or configureNo need for local migration expertise.When working with BPOS-D it is important to note that there are no offerings for an on-premise migration.
  • The standard approach to an on premise migration requires a number of different requirements to successfully migrate to Microsoft Online. These may include:Hardware procurement to execute the migrationProcurement of software to execute the migrationRequires installation of software and the associated configuration of the software, and It requires a knowledge of the migration process.
  • The Third Party Hosted Approach such as Weekend Express from BinaryTree is a much simpler methodology for a migration to BPOS-Standard.With migration such as these, the Domino mail files are replicated to a secure data center. This replication is enabled through cross certification between the customer location and the hosted Domino servers. A migration farm located in this data center then executes the migration directly to BPOS-S. As a result there is:No hardware to purchaseNo software to purchaseNo software to install or configureNo need for local migration expertise.When utilizing this rapid approach, such as BinaryTree’s Weekend Express, for migrations to BPOS-S it is important to note that these migrations could take longer than a single weekend, and it may also include more than 90 days of mail or a year of calendar entries.
  • There are several consideration associated with Migrations to Microsoft Online (BPOS-S). Traditional on premise migrations provide the customer a higher sense of control and ownership of the process. This does require a significant investment into hardware, software, and staffing to manage the Exchange migration.With a hosted migration there is still a level of control provided to the customer but this almost entirely eliminates the customer investment of hardware, software, and staffing. For general migrations, an on premise migration may be suitable for a gradual migration from Domino to BPOS. For rapid migrations the only way to move forward would be through a Host migration.Rapid
  • Migrating from Domino to Exchange 2010

    1. 1. Welcome to the Binary Tree Webinar…A Comprehensive Strategy for Migrating from Lotus Domino to Microsoft Exchange 2010<br />Vadim Gringolts, CTO, Binary Tree<br />April 22, 2010<br />We’ll get started in just a few minutes…<br />
    2. 2. Welcome to the Binary Tree Webinar…A Comprehensive Strategy for Migrating from Lotus Domino to Microsoft Exchange 2010<br />Vadim Gringolts, CTO, Binary Tree<br />April 22, 2010<br />
    3. 3. Who is Binary Tree?<br />The leading provider of cross-platform migration & coexistence software<br /><ul><li>Migrated over 4,000 customers and more than 15,000,000 users
    4. 4. Authorized ISV for Microsoft Enterprise Notes Migration (ENM)
    5. 5. Focused exclusively on successfully completed migration initiatives</li></ul>Authorized ISV for Microsoft Enterprise Notes Migration (ENM) Methodology<br />
    6. 6. Key Success Factors for Migrations<br />The end-user experience must be transparent and the user workflow must be maintained<br />Communications to end-users must be simple<br />The project must be predictable and manageable<br />The project plan must be flexible and focused on reducing costs and risks<br />The technology you choose can make a big difference in the results you realize<br />
    7. 7. Understanding the Challenges of Migration<br />The wrong approach or the wrong tools can undermine your initiative<br />Potential risks of the wrong approach or wrong tools:<br />A longer and more complex migration project<br />Declines in the productivity and collaboration of your users and executives<br />The delay of key business processes<br />Missing data <br />Budget overruns<br />Higher on-going costs from not consolidating and retiring the legacy Domino environment<br />
    8. 8. A New Challenge for Migrating to Exchange 2010<br />Microsoft is no longer providing directory synchronization or free/busy<br />
    9. 9. A Proven Migration Strategy & Methodology<br />A Comprehensive Best Practices Strategy to Coexistence & Migration<br />This is an overview of a best practices strategy and methodology forreducing costs, effort, and business disruptions when transitioning from Lotus Notes and Domino to the Microsoft platform or to Microsoft Online. <br />RE-TRAIN USERS<br />EMAIL<br />EMAIL<br />EMAIL<br />PLAN &PREPARE<br />LAUNCH& RETIRE<br />ANALYZE<br />COEXIST<br />MIGRATE<br />APPLICATIONS<br />APPLICATIONS<br />APPLICATIONS<br />CONSOLIDATE & RETIRE DOMINO<br />
    10. 10. Software that Supports the Methodology<br />A complete software suite for migrating Notes mail and applications to Microsoft<br />Coexist<br />Migrate<br />Analyze<br />CMT for Exchange<br /><ul><li>Migrate messaging and directory information to Exchange
    11. 11. Comprehensive migration includes attachments, rules and encrypted items
    12. 12. Centralized migration management tools</li></ul>CMT Inspector Express<br /><ul><li>Pre-sales analysis of messaging and application environment (mailboxes, servers, replicas, application design)
    13. 13. Free to Microsoft and trained partners</li></ul>CMT for Coexistence<br /><ul><li>Allows all email enabled applications to function properly without any change!
    14. 14. Maintains data and calendar workflow fidelity with users across both systems
    15. 15. Prevents incorrect processing of updates to recurring meetings
    16. 16. Resolves user names with “friendly names” to reduce confusion and security concerns</li></ul>CMT for SharePoint<br /><ul><li>Migrate Lotus Notes applications to Microsoft SharePoint, InfoPath, WebParts
    17. 17. Migrate content and design
    18. 18. Preserve site and application security and data fidelity</li></ul>CMT Inspector<br /><ul><li>Detailed analysis of the messaging and application environment (design matching, design and data analysis, detailed reporting)
    19. 19. Help manage user surveys and analysis communications</li></li></ul><li>Perform a Pre-Project Mail and Application Analysis<br />Gather information about your Domino environment with CMT Inspector Express<br />Easy, simple to use tool for analysis and reporting on the Lotus Notes & Domino Environment<br /><ul><li>Server Inventory
    20. 20. Application Inventory
    21. 21. Mail File Inventory
    22. 22. Application Usage
    23. 23. Replica Filtering
    24. 24. Design Complexity
    25. 25. Template Matching</li></li></ul><li>Perform a Detailed Mail and Application Analysis<br />Examine Domino in unprecedented detail with CMT Inspector Enterprise<br />Notes Mail Assessments<br /><ul><li>Mailbox Size Planning
    26. 26. Encrypted Mail
    27. 27. Calendar Entries
    28. 28. Out of Office
    29. 29. Delegates
    30. 30. Attachments
    31. 31. Duplicate Attachments
    32. 32. Mail Archives</li></ul>Application Assessments<br /><ul><li>Usage
    33. 33. Access control
    34. 34. Application content
    35. 35. Design
    36. 36. Template matching
    37. 37. Server data
    38. 38. …and more</li></li></ul><li>Consolidate Domino Prior to Coexistence<br />Consolidate Domino domains and servers to streamline the coexistence and migration phases with CMT for Domains<br />CMT for Domains<br /><ul><li>Move users and servers to a single address book
    39. 39. Audit and correct mail files
    40. 40. Update user desktops to reflect a single domain</li></li></ul><li>What is Workflow?<br />The flow or amount of work to and from an office, department, or employee (Dictionary.com)<br />The foundation of organizational productivity<br />Workflow interruption will adversely impact organizational productivity and doom a migration project to failure<br />
    41. 41. Protect the Workflow ofYour Users<br />CMT for Coexistence 3.0 AND CMT for Exchange 3.1 protect the user workflow between Domino and Exchange<br />
    42. 42. Protect the Workflow ofYour Users<br />Prevent interruptions in collaboration with CMT for Coexistence & CMT for Exchange<br /><ul><li>Ensuring Messaging Workflow, including doc & database links
    43. 43. Ensuring Calendar Workflow even for complex recurring meetings
    44. 44. Ensuring Application Workflow by enabling Outlook users to see and act on email-enabled Lotus Notes workflow applications
    45. 45. Ensuring Directory Workflow with directory synchronization
    46. 46. Ensuring Availability Workflow with calendar free/busy lookups</li></li></ul><li>Protect the Directory Workflow of Your Users<br />Ensure that user addressing is transparent and functional<br />CMT for Coexistence Directory Workflow<br /><ul><li>Establishes directory synchronization between Domino and Exchange
    47. 47. Ensures that user addressing is transparent and functional regardless of a user’s migration status
    48. 48. Enables Notes and Outlook users to view traditional hierarchical name addresses in their emails and calendar invites rather than confusing SMTP names addressing</li></ul>Without CMT for Coexistence…<br />…easy to understand email addresses before the migration…<br />…can turn into confusing email addresses during the migration…<br />
    49. 49. Protect the Availability Workflow of Your Users<br />Ensure that users can check invitee availability when scheduling meetings<br />CMT for Coexistence Availability Workflow<br /><ul><li>Establishes calendar free/busy lookups between Domino and Exchange
    50. 50. Ensures that Notes and Outlook users can obtain calendar free/busy information about other users regardless of which system they are on or regardless of their migration status</li></li></ul><li>Protect the Messaging Workflow of Your Users<br />Ensure the normal functionality of email between your users<br />CMT for Coexistence Messaging Workflow<br /><ul><li>Message threads stay intact regardless of migration status
    51. 51. Also enables Outlook users to view and interact with embedded graphics, as well as Notes document and database links, the same way Notes users do</li></li></ul><li>Protect the Calendar Workflow of Your Users<br />Keep your user calendars in sync<br />CMT for Coexistence Calendar Workflow<br /><ul><li>Ensures that calendar events between the Notes users and the Outlook users stay in sync regardless of their migration status
    52. 52. Applies to creating meetings, updating meetings, rescheduling meetings, cancelling meetings, and even apples to changes to complex recurring meetings</li></li></ul><li>Protect the Application Workflow of Your Users<br />Enable Outlook users to act on email-enabled Notes workflow apps<br />CMT for Coexistence Application Workflow<br />The Zero-touch Application Remediation (ZApp) option of CMT for Coexistence 3.0 prevents Notes application failure when users are migrated to Outlook<br /><ul><li>Intercepts mail messages with embedded Notes elements and remediates them for Outlook Users
    53. 53. Catches apps with Lotus UI commands that trigger mail messages and ensures they work properly
    54. 54. Apps that write to a users Lotus Notes calendar are either fixed or the user is notified with the information in a mail message</li></ul>Requires no changes to the applications<br />
    55. 55. Understanding the Components of Coexistence<br />Native Support for Exchange 2010 (full compatibility with Exchange 2007)<br />Internet<br />SMTP<br />SMTP<br />CMT for Coexistence with Complete Workflow Protection<br />BT Directory<br />Domino 6x/7x/8x<br />Exchange 2007/2010<br />DirSync<br />DirSync<br />MS-SQL Server<br />SMTP,<br />HTTP/HTTPS,<br />LDAP<br />NRPC<br />HTTP/HTTPS (Free/Busy)<br />BTStore(ZApp)<br />SMTP (Mail Routing)<br />WindowsCoexistence Server<br />Domino Coexistence Server<br />CMT for Coexistence with ZApp<br />BTCal – Domino Server Task<br />BTDirSync – Domino Server Task<br />BTFreeBusy – Domino Server Task<br />BTEx – Mail Router Extension Manager<br />CMT for Coexistence<br />Directory Synchronization Service<br />Free Time Lookup Web Config<br />
    56. 56. Understanding the Components of Coexistence<br />Native Support for Exchange 2010 (full compatibility with Exchange 2007)<br /><ul><li>Domino Coexistence Server (Release 6.5.5/6.5.6/7.0.3/8.5)
    57. 57. Messaging/Calendaring/Application Coexistence Server Task
    58. 58. Directory Synchronization Server Task
    59. 59. Free/Busy Lookup Server Task
    60. 60. Transitional Domino Database for Storing Remediated Application Mail
    61. 61. Windows Coexistence Server (Exchange 2010/2007 optional)
    62. 62. Directory Synchronization Service
    63. 63. Free/Busy Lookup Web Configuration
    64. 64. Dedicated SQL Database on dedicated or shared SQL Server
    65. 65. Transitional Directory for Directory Synchronization</li></li></ul><li>Highlights of CMT for Coexistence<br />Native Support for Exchange 2010 (full compatibility with Exchange 2007)<br /><ul><li>Supports Exchange 2007 and 2010, OWA 2007 and 2010, Outlook 2007 (Outlook 2010 supported when GA)
    66. 66. Employs open standards/protocols for cross-platform interface:
    67. 67. SMTP, MIME, iCAL, HTTP/HTTPS, LDAP
    68. 68. Achieves data transfer security by utilizing SSL
    69. 69. Meets enterprise stability and scalability demands via TCP/IP and SMTP failover and load balancing
    70. 70. Uses Web Services and native functionality within Exchange and Domino for Mail, Calendar, and Availability Data transfer:
    71. 71. Exchange SMTP routing, Exchange Availability Services
    72. 72. Domino NRPC routing, Domino availability API</li></li></ul><li>Understanding the Components of Coexistence<br />Support for Exchange 2010 and 2007 via Transporter (for Outlook 2003 users)<br />Internet<br />SMTP<br />SMTP<br />CMT for Coexistence with Complete Workflow Protection<br />Domino 6x/7x/8x<br />Exchange 2007/2010<br />NRPC<br />SMTP<br />Notes API (Free/Busy, Dirsync)<br />BTStore(ZApp)<br />SMTP (Mail Routing)<br />Exchange 2007<br />Coexistence Server<br />Domino Coexistence Server<br />CMT for Coexistence with ZApp<br />BTCal – Domino Server Task<br />BTEx– Mail Router Extension Manager<br />Microsoft Transporter<br />ExCalCon - Domino Server Task<br />Microsoft Transporter<br />Directory Synchronization Service<br />Free Time Lookup Service<br />
    73. 73. Understanding the Components of Coexistence<br />Support for Exchange 2010 and 2007 via Transporter (for Outlook 2003 users)<br /><ul><li>Domino Coexistence Server (Release 6.5.5/6.5.6/7.0.3/8.5)
    74. 74. Messaging/Calendaring/Application Coexistence Server Task
    75. 75. Transitional Domino Database for Storing Remediated Application Mail
    76. 76. Transporter Free/Busy Lookup Server Task
    77. 77. Exchange Coexistence Server (Version 2007)
    78. 78. Transporter Directory Synchronization Service
    79. 79. Transporter Free/Busy Lookup Service</li></li></ul><li>Highlights of CMT for Coexistence<br />Support for Exchange 2010 and 2007 via Transporter (for Outlook 2003 users)<br /><ul><li>Supports Exchange 2007 and 2010, OWA 2007 and 2010, Outlook 2003, 2007 (Outlook 2010 supported when GA)
    80. 80. Employs open standards/protocols for cross-platform interface:
    81. 81. SMTP, MIME, iCAL
    82. 82. Requires Notes API connection between Exchange and Domino
    83. 83. Meets enterprise stability and scalability demands via TCP/IP and SMTP failover and load balancing
    84. 84. Uses native functionality within Exchange and Domino for Mail, Calendar, and Availability Data transfer:
    85. 85. Exchange SMTP routing, Exchange Free/Busy Public Folders
    86. 86. Domino NRPC routing, Domino availability API</li></li></ul><li>Retrain Your Users on Outlook before Migrating<br />Help make the transition easier for your users<br />Binary Tree Outlook Training Portal<br /><ul><li>An online training guide for your Notes users to learn Microsoft Outlook
    87. 87. Includes reference sheets, FAQs and more</li></li></ul><li>Why CMT for Exchange?<br />Consider the differentiators<br /><ul><li>Outstanding Data Fidelity
    88. 88. Transparent Mail fidelity (Rich Text, composite HTML, Images & more)
    89. 89. Excellent calendar fidelity:
    90. 90. Repeating calendar events with simple and complex patterns (including custom)
    91. 91. Enhanced transitional calendar workflow
    92. 92. Domino Room, Resource, and On-line Meeting Place information
    93. 93. Contact and personal group fidelity (attachments and comments)
    94. 94. Task Migration fidelity (task ownership)
    95. 95. Excellent Throughput
    96. 96. Effective application performance
    97. 97. High-throughput parallel migration topology
    98. 98. Migration workload distribution to meet enterprise requirements</li></li></ul><li>Why CMT for Exchange?<br />Consider the differentiators<br /><ul><li>Management, Customization, Extensibility
    99. 99. Global Directory Management (NAB and AD) – Transition of users and groups
    100. 100. Rooms and Resource Content Migration from Domino Resource Reservation Databases
    101. 101. Management of the entire migration from a single, customizable interface
    102. 102. Use of standard and custom pre-migration and post-migration tasks
    103. 103. Advanced data filtering, and much more
    104. 104. Integration with mobile and archive migration solutions
    105. 105. Direct Migration from Domino to Exchange 2010
    106. 106. Backward Compatibility for Migrations to Exchange 2007/2003
    107. 107. Flexibility to Migrate to Exchange BPOS-D, BPOS-S, and On-premises</li></li></ul><li>More about Calendar Workflow<br />It’s not just part of coexistence<br /><ul><li>Transitional Calendar Workflow: Ability to schedule, re-schedule, update, cancel meetings across dissimilar platforms regardless of chairperson and invitee migration status
    108. 108. Significant Calendar Workflow is accomplished by CMT for Coexistence and CMT for Exchange separately, but even greater Calendar Workflow is achieved when CMT for Coexistence and CMT for Exchange are used together
    109. 109. Examples:
    110. 110. Notes chair schedules a meeting with some Notes and Exchange invitees, then chairperson and some invitees migrate to Exchange... …Subsequent re-schedules, updates, and cancellations work
    111. 111. Exchange chair schedules a meeting with some Notes and Exchange invitees, then some invitees migrate to Exchange... …Subsequent re-schedules, updates, and cancellations work</li></li></ul><li>Ensure the Fidelity of the Data You MigrateConsider the following example…<br />Room and Resource Databases<br />CMT for Exchange 3.1 – Fully supports the migration of Room and Resource Databases<br />
    112. 112. Understanding the Components of Migration<br />Support for Exchange 2010/2007/2003<br />CMT for Exchange Migration Infrastructure<br />Domino 6x/7x/8x<br />Migration Workstation<br />Exchange 2010/2007<br />Migration Workstation<br />
    113. 113. Understanding the Components of Migration<br />Support for Exchange 2010/2007/2003<br /><ul><li>Migration Workstation: a basic unit of Migration Infrastructure
    114. 114. Read, Translate, Write
    115. 115. Windows XP, Windows 2003
    116. 116. Support for Windows 7 upcoming
    117. 117. Lotus Notes Client 7.0.3 (recommended) or 8.x
    118. 118. Microsoft Outlook 2007 (recommended) or 2003
    119. 119. Read Access to Source Domino Environment
    120. 120. Write Access to Target Exchange Environment
    121. 121. Best: Read and Write over High Speed LAN
    122. 122. Alternative 1: Read over WAN, Write over LAN
    123. 123. Alternative 2: Read over LAN, Write over WAN
    124. 124. Alternative 3: Read over WAN, Write over WAN</li></li></ul><li>Understanding Migration Scalability<br />Automated Workload Distribution (AWD)<br />CMT for Exchange Migration Infrastructure<br />Migration Server<br />Exchange 2010/2007<br />Domino 6x/7x/8x<br />Migration Farm<br />Migration Workstation<br />Migration Workstation<br />Migration Workstation<br />
    125. 125. Global Migration Scalability via Automated Workload Distribution<br />Worldwide migration infrastructure<br />Migration Control Center<br /><ul><li>Windows 2003 Server
    126. 126. Centralized Dashboard
    127. 127. Job Dispatcher</li></ul>1<br />2<br />EMEA<br />Exchange Servers<br />Domino Servers<br />Migration Workstations<br />Migration Workstations <br /><ul><li> Windows XP SP2/2003
    128. 128. Localized Migrations
    129. 129. Poll for jobs from dispatcher
    130. 130. Report results back to dispatcher</li></ul>2<br />1<br />2<br />US<br />Exchange Servers<br />CMT for Exchange <br />can be configured to run on a single machine for small migrations or as a migration farm for large enterprise migrations.<br />Migration Workstations<br />Migration Control Center<br />Domino Servers<br />2<br />AP<br />Exchange Servers<br />Domino Servers<br />Migration Workstations<br />
    131. 131. Ensure the Manageability of Your Migration<br />Make sure you have the management control you need<br />CMT for Exchange 3.1<br /><ul><li>Central management console to track the entire migration process
    132. 132. Simple interface to control migration processing and monitor status</li></ul>Value<br />A centralized repository for all migration related activities<br />
    133. 133. Ensure the Manageability of Your Migration<br />Make sure you can control the entire migration infrastructure<br />CMT for Exchange 3.1<br /><ul><li>Central management console to track the workstation’s migration status at their sites
    134. 134. Ability to add a workstation to the migration farm with ease right on the dashboard</li></ul>Value <br /><ul><li>Central migration management
    135. 135. Reduce time and effort to manage multiple machines</li></li></ul><li>Ensure Migration Extensibility<br />Meeting customer-specific requirements<br /><ul><li>Use standard or develop custom pre-migration Lotus Notes actions to prepare Domino Mail files for migration
    136. 136. For example: replicate mail files to central environment
    137. 137. Send e-mails to end-users with actions to prepare end-user environments (Notes Clients) for migration
    138. 138. For example: decrypt encrypted mail items
    139. 139. Another example: insert local contacts into mail file
    140. 140. Another example: find and push local archives to a central location
    141. 141. Filter migrated data by date range, age, type, size, etc.
    142. 142. Manage ACL contents/Mail File delegations
    143. 143. Anything else?</li></li></ul><li>What about end-user run migrations?<br />Benefits and shortcomings of a self-service model<br /><ul><li>CMT for Exchange supports Server and End-user migration
    144. 144. Every end-user machine becomes a migration workstation
    145. 145. Good: no need to build migration infrastructure
    146. 146. Bad: inconsistent hardware, network bandwidth, OS, application software
    147. 147. Every end-user becomes a migration administrator
    148. 148. Good: no need to allocate resources
    149. 149. Bad: inconsistent expertise, insufficient authority, greater need for support
    150. 150. Every end-user schedules own migration
    151. 151. Good: no need for centralized scheduling and coordination
    152. 152. Bad: no centralized reporting, progress monitoring
    153. 153. Preferred approach – Centralized Server Migration
    154. 154. Local archives can be consolidated on a central File Server or Domino Server and migrated in a centralized mode</li></li></ul><li>Migration from Lotus Domino to Microsoft BPOS<br />
    155. 155. Microsoft Hosted Migration Approach (BPOS-D)<br />Microsoft Online<br />On-premises<br />Domino Infrastructure<br />Data <br />Data (LAN)<br />(WAN)<br /><ul><li>Does not require hardware procurement
    156. 156. Does not require software procurement
    157. 157. Does not requires migration software installation and configuration
    158. 158. Does not require migration expertise</li></ul>MS Data Center Hosted Migration Farm<br />Running migration software (Partner-Managed)<br />
    159. 159. Standard On-Premises Migration Approach<br />Microsoft Online<br />On-premises<br />Domino Infrastructure<br />Data <br />Data (WAN)<br />(LAN)<br /><ul><li>Requires hardware procurement
    160. 160. Requires migration software procurement
    161. 161. Requires migration softwareinstallation and configuration
    162. 162. Requires migration expertise</li></ul>On-premises Migration Farm<br />Running migration software<br />
    163. 163. 3rd party Hosted Migration Approach (BPOS-S)<br />Microsoft Online<br />On-premises<br />Domino Infrastructure<br />Notes Replication<br />Data (High Speed WAN)<br />Temporary Domino Servers<br />3rd party Hosted/Secured<br /><ul><li>No hardware to procure
    164. 164. No migration software to procure
    165. 165. No migration software installation and configuration
    166. 166. No migration expertise requirement</li></ul>3rd Party Hosted Migration Farm<br />
    167. 167. Migration to MS Online (BPOS-S) Considerations<br />Traditional on-premises migration approach appears to give customers a greater sense of control and ownership, but requires a potentially significant investment in migration hardware, software, and personnel<br />Hosted migration approach still gives customer some control, but virtually eliminates customer’s investment in migration hardware, software, and personnel<br />Both on-premises and hosted migration approaches may be suitable for a gradual migration<br />Hosted migration approach is the only way to achieve a rapid migration<br />
    168. 168. Binary Tree Experience with BPOS-D Migrations<br />30,000 Users<br />2,500 Users<br />21,500 Users<br />19,000 Users<br />118,000 Users<br />7,000 Users<br />3,700 Users<br />…has also lead to Weekend Express for BPOS-S<br />On Friday, You’re on Lotus Notes…<br />…On Monday, You’reon Microsoft Online!<br />
    169. 169. Considering Migrating to Microsoft Online/BPOS?<br />Consider the remote hosted migration approach of Weekend Express<br />Online User Training<br />Online User Training<br />Online Training Portal<br />10GB Fiber to BPOS + Redundant Routers & more<br />Migration<br />Client’s Internet Connection<br />Staging/Replication Servers + Migration Control & Processing Workstations<br />Notes Replication<br />Client’s Internet Security Measures<br />plus Weekend Express Firewalls<br />128-bit Encrypted VPN + VLAN Security + Firewalls<br />Customer’s Email Data<br />On Domino Servers<br />Microsoft Online<br />The Binary Tree Data CenterCertified to SAS-70 Type II and PCI Compliance<br />Lotus Audit<br />The migration includes:<br /><ul><li>90 days of email
    170. 170. 1 Year of past calendar entries
    171. 171. All future calendar entries
    172. 172. All contacts
    173. 173. All tasks</li></ul>Relax and leave the migrating to us…<br /><ul><li>No hardware to buy, install or configure
    174. 174. No software to buy, install or learn
    175. 175. No on-site consultants needed
    176. 176. No expertise on migration needed
    177. 177. Includes Outlook online user training</li></li></ul><li>Migration from Lotus Domino to Microsoft Exchange:Going beyond Mailbox Migration<br />
    178. 178. Don’t Forget to Migrate Your Mobile UsersMigrate BlackBerry users between enterprise mobile servers and between enterprise messaging systems<br />CMT Mobile<br /><ul><li>Migrate via user lists of BlackBerry users or via import of a .csv file
    179. 179. Automatically migrate selected BlackBerry users from origin to destination BlackBerry domain
    180. 180. Migration can be prepared and started at a specified time in the future
    181. 181. Users are automatically notified about the date and time of the migration
    182. 182. Includes functionality to monitor and manage the users and environment
    183. 183. Support for iPhones and Windows Mobile Devices coming soon!</li></li></ul><li>Migrate Your Notes Applications to SharePoint<br />Migrate document libraries, discussion databases, TeamRoom and QuickPlace applications<br />CMT for SharePoint<br />Migrates Lotus Notes content<br /><ul><li>Standard Lotus Notes Applications
    184. 184. Custom Applications
    185. 185. Centralized Management
    186. 186. Detects which apps are compatible for migration</li></li></ul><li>Make it Easy for Your Developers to Reuse Code<br />Reuse the best code snippets over and over again<br />Binary Tree’s Transformation Resource Center and Plug-in for Visual Studio<br /><ul><li>Store code snippets of code transformations here
    187. 187. Lotus Notes @Commands
    188. 188. @Functions, and LotusScript to C# and VB
    189. 189. Share with others to gain knowledge across your team</li></li></ul><li>Consolidate & Retire Domino After the Migration<br />Decommission and reture unused servers and applications<br />CMT for DomainsRetire Domino servers to reduce on-going costs<br /><ul><li>Decommission unused servers and applications
    190. 190. Consolidate remaining servers</li></li></ul><li>Binary Tree Provides a Comprehensive Strategy and the Solutions for Migrating from Domino to Exchange 2010<br />A Complete Suite of Software Solutions for a Workflow-Protected Migration<br />LAUNCH& RETIRE<br />PLAN &PREPARE<br />ANALYZE<br />COEXIST <br />MIGRATE <br />Analyze messaging<br />Coexist directories, free/busy, email & calendars<br />Migrate messaging<br />Analyze applications<br />Coexist email-enabled Notes workflow applications<br />Migrate applications<br />Migrate mobile devices<br />RE-TRAIN<br />Re-train Notes users on Microsoft Outlook<br />CONSOLIDATE & RETIRE DOMINO<br />Consolidate and retire Domino servers and applications<br />
    191. 191. Why Choose Binary Tree for Your Migration?<br />Our suite of software provides you with the best solution for migrating from Lotus to Microsoft…<br />A Comprehensive Solution <br />The Highest Fidelity Available<br />Protected User Workflow<br />Complete Control<br />Reduced Costs and Risks<br />
    192. 192. Our Solutions are Referred by Microsoft<br />“Binary Tree is a preferred and leading Microsoft ISV Partner for supporting customers that are seeking to transition from Lotus Notes to Microsoft’s platform for enterprise messaging, applications and collaboration.”– Terry Birdsell, Director of Enterprise Sales, Microsoft<br />“Binary Tree is a leading Microsoft ISV Partner, and their new solutions will provide a complete option for customers who are looking for an alternative to the Notes Transporter Suite.”<br />– David Scult, General Manager in Information Worker Marketing, Microsoft <br />
    193. 193. Prominent global and regional systems integrators have migrated customers using our software<br />
    194. 194. Over 4,000 of the world’s most demanding migration customers have demanded Binary Tree software<br />
    195. 195. Questions and Answers<br />Vadim Gringolts, CTO, Binary Tree<br />April 22, 2010<br />
    196. 196. For More Information, Contact Us<br />Sales: sales@binarytree.com<br />In North America & Asia PacificCarl Baumann, Worldwide Director of SalesOffice: +1-215-550-6561 carl.baumann@binarytree.com<br />In Europe, Middle East & AfricaKurt van den Eynden, Director of Sales, EuropeOffice: +44 (0) 20 7692 5661kurtv@binarytree.com<br />Partners: partners@binarytree.com<br /><ul><li>For Regional Systems IntegratorsAnita Brooks-Jackson, Microsoft Channel Manager, US SalesOffice: +1-630-466-3895 anita.brooks@binarytree.com
    197. 197. Global Systems IntegratorsTraci Blowers, Director of Alliances and Business DevelopmentMobile: +1-716-864-7046 traci.blowers@binarytree.com</li></li></ul><li>Thank You for Attending!<br />Vadim Gringolts, CTO, Binary Tree<br />April 22, 2010<br />
    198. 198. The only option for migration success<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×