Although most organizations that use IBM Domino have started a migration from the platform, few have found a way to complete it. While moving Lotus Notes email proved a fairly easy task, the migration of IBM Notes based applications has been quite the opposite. Companies have spent years attempting to migrate their applications, only to now face issues that appear insurmountable. With misleading promises of simplicity, organizations are now realizing increased licensing costs, unmanageable proprietary solutions, unsupportable legacy code, and long-term support contracts.
It’s been more than ten years since we began to see the decline in interest in IBM’s Lotus Notes & Domino platform. It was evident IBM was struggling with the positioning of the platform. IBMs software catalog had numerous products that directly competed with IBM Domino and so instead it was positioned as a collaborative or email product. It was not seen as an enterprise rapid application development environment as it had been used for years prior. If you were looking for an application development platform IBM steered you toward DB2, Rational, or WebSphere. The long-term viability of Lotus Domino was also impacted by the fact that the product itself had been around since the 90’s, and significant portions of its code have never been touched or updated and meant the cost to update the platform wasn’t going to be insignificant. So, IBM let it flounder, the industry took notice, and Notes Domino became a legacy platform.
Microsoft did an exceptional job presenting competitive solutions to Lotus Notes Domino, and Office 365 soon became the de facto platform for migrated Notes email. Microsoft also maintained that SharePoint was going to be an ideal destination for Domino applications, but that hasn’t proven to be the case. While some organizations achieved limited success moving simple document repositories to SharePoint, most have found it far too limiting in reproducing Domino business applications. Not only was it impossible to deliver the same level of functionality and usability as the original Domino application, the migration/development process ended up taking on a significantly higher cost than the original cost of developing the Domino application. With increased application complexity in the native Domino application, migrating to SharePoint has largely been a failure.
Proprietary 3rd party solutions can appear to be promising, but they typically only address a very small subset of applications. Also, they are often based on non-enterprise technologies that require architectural exceptions that can be difficult and costly to maintain. In the end, most organizations have been forced to leave their applications on Domino, without a migration plan. But the “do nothing” strategy means you now have outdated applications, aging or nonexistent Domino expertise, and unfulfilled end user requirements. It’s a big problem that is only getting bigger.
Nine years ago, when we rebranded our former Notes Domino company as Rivit, we did so with the sole intention of helping companies transition away from Domino. We’ve successfully worked with many companies to assist in their application migrations and along the way, have seen all the reasons why companies have failed. But more importantly, we have found what meets the needs of organizations in your position. A destination framework based on open and widely accepted enterprise standards that encompasses the core features your users have come to depend on. A solution that includes migration utilities and features to provide a faster transition than you’ve experienced. And most importantly, you need technologies you currently have experience with, with a vast and growing low-cost resource pool. Revive is that solution, and we’re here to help you get packing.