Challenge: semi-structured Notes data
Semi-structured data represent a specific challenge for modernizing classic Lotus Notes applications.
First, rich text fields in Notes applications should be transformed to equally formatted HTML. Secondly, most classic Notes applications use “wysiwyg” forms — compound documents whose layouts are precisely designed for both data-entry and print. In modern applications, this concept has been replaced by responsive design for web and mobile (often combined with PDF output for printing or delivering customer-facing documents).
Challenge: application consolidation
There are also other reasons why migrating data from old databases can be more complex than anticipated. New applications don’t necessarily match old applications one-to-one. In some cases, business processes have evolved over the years; in others, mergers, acquisitions, or restructurings have taken place. Or, a company may have simply attempted to reduce IT complexity by consolidating applications and infrastructure. Developers then need to rethink the entire data model and perhaps start from scratch to re-architect the system.
To jettison historical baggage and mitigate risks, companies can break the data migration process into three steps:
- Extracting historical Notes records to an archive repository
- Re-architecting databases and applications
- Migrating only necessary data to the new system
Following this process frees developers from the burden of supporting legacy data, which accelerates new application development and data migration. New databases will contain only live data, while historical records will be available to authorized users for future reference, especially in the event of litigation or an audit.
Do you have a specific Notes application modernization or data migration project you would like to discuss with us? Please send us your thoughts, comments or questions.