Migrating Domino and Encrypted NSF Data to Microsoft 365: What You Need to Know
For organisations still operating historical Lotus Notes data stored in NSF database files, migrating that information to Microsoft 365 can appear straightforward: extract the email, transform it, import it.
In practice, NSF data can be considerably more complex. Decades of platform development, database structures, custom applications, encryption and changing behaviours mean can create challenges that aren’t immediately apparent from the number of users or volume of data involved. Understanding those complexities before migration begins can make the difference between moving data and migrating it correctly.
NSF Is More Than a Collection of Emails
An NSF database can contain information and structures that don’t map neatly to a conventional email model. Domino has evolved over decades and across numerous versions, creating environments containing different structures, fields and application behaviours. Migration technology therefore needs to do more than extract a message body and attachment. It needs to interpret the source correctly and transform the relevant information into something the destination platform understands.
Why Native Interpretation Matters
There are broadly different approaches to interpreting proprietary data structures.
One is to independently interpret the underlying format. Another is to use technologies from the original platform to help interpret the information.
Both approaches can appear to produce the same result when dealing with straightforward data. The differences become more important when encountering the unusual cases accumulated through years of real-world use.
Intelligent Migrator can work with HCL Notes technologies where native Domino interpretation is required. This enables the migration process to draw on established Domino behaviour when interpreting complex source information rather than depending entirely on an independently recreated interpretation of NSF structures.
Then There Is Historical Complexity
Consider what can happen to an archive over 20 years. The organisation changes Domino versions, applications are customised, people leave, certificates expire, databases are moved, retention policies change, software is upgraded, data is imported from other environments, previous migrations take place. Years later, someone is asked to migrate everything into Microsoft 365 or any other platform.
The resulting environment may contain a mixture of perfectly standard information and edge cases nobody anticipated when the data was originally created.
Problematic data needs particular care. The objective shouldn’t simply be to make an unusual item disappear from the migration queue. Migration teams need confidence that the source was correctly understood and that the information arriving at the destination accurately represents it.
Intelligent Migrator identifies problematic or malformed data so exceptions can be investigated and appropriate remediation decisions made.
That visibility is especially important when migrating historical information retained for regulatory, legal or business purposes.
Migrating Encrypted NSF Data
Encryption adds another layer of complexity. Encrypted NSF information must first be accessible before it can be transformed into a format suitable for the target environment.
Intelligent Migrator supports encrypted NSF data where the necessary credentials are available to decrypt the source information. Standard encrypted NSF migration does not require bespoke development simply because the data is encrypted.
Once accessible, the information can be processed, transformed and migrated to the destination while maintaining the visibility and controls expected from an enterprise migration.
You Don’t Migrate an NSF File “Into Microsoft 365”
There is also an important terminology distinction.
Microsoft 365 doesn’t store an NSF database as an NSF database. The information within the NFS needs to be interpreted, transformed and correctly represented in the formats and structures supported by the Microsoft destination. This can include email content, folders, attachements, metadata, and other properties associated with the original data. That means the quality of the transformation process matters. A migration isn’t successful merely because the source NSF has been processed. What matters is whether the information has been accurately preserved and correctly represented in its new environment.
Metadata Matters
The visible content of an email is only part of the record. Historical NSF data can contain metadata and properties that provide important context about the original message, its users and how it was sorted within the source environment.
When that information is migrated to Microsoft 365, not every NSF property will necessarily have a direct equivalent at the destination.
Migration planning therefore needs to establish:
- What information and metadata exists within the source NSF data?
- What needs to be preserved?
- What can the target accept?
- How will NSF data and properties be transformed or represented at the destination?
- How will unsupported or incompatible information be identified and handled?
- How will successful migration be validated?
These decisions should be understood before large-scale processing begins.
Experience With Domino Matters
Domino isn’t a new platform. That is precisely why migration experience matters.
Transvault has been working with enterprise archive and Domino data for many years, allowing Intelligent Migrator to develop around real migration scenarios and unusual data conditions encountered in production environments. Every complex migration contributes to the maturity of the technology. For organisations migrating decades of historical information, that accumulated experience can be as important as any individual feature on a product specification.
Questions to Ask Before a Domino Migration
Before selecting your migration approach, establish:
- Which Domino and Notes versions exist?
- How many NSF databases are involved?
- Is any information encrypted?
- Are the necessary credentials and certificates available?
- Are custom applications or unusual structures involved?
- Has the environment undergone previous migrations?
- How will malformed or problematic information be handled?
- What metadata needs to be preserved?
- How will migrated data be validated?
- And what evidence will be available after migration?
The purpose of a Domino migration isn’t simply to eliminate NSF files. It is to move valuable historical information into a modern environment while preserving what matters about that information. That requires understanding the source, correctly interpreting its data and providing visibility when something unexpected is encountered. After decades of Domino evolution, there are plenty of unexpected things to find.
Planning a Domino or NSF migration to Microsoft 365
Talk to Transvault about your Domino environment, encrypted data and migration requirements.