The Migration Process
Over the years, the majority of development associated with Lotus Notes was all about building fancy forms and views; the amount of developers writing complex LotusScript or Java agents was quite minimal. Because of this, most simple data validation, background document processing and button event scripting was achieved with canned actions and Notes formulas. In fact, about 75 to 85 per cent of Notes and Domino applications fall into this category and, as such, the process of converting NSF to PST for this portion is relatively easy. Here are the five steps you can take when migrating this portion. Bear in mind that, when it comes to the remaining 15 to 25 per cent of highly complex applications, these steps will not suffice.
1. Inventory and sponsor
When an organisation makes a decision to convert NSF to PST — that is, to migrate from Lotus Domino to Microsoft Exchange — there are many best practices to keep in mind. In this article, we’ll take a look at six of these best practices, from understanding the difference between Notes and Outlook to paying attention to the issue of replication.
1. Understand the difference between Lotus Notes and Outlook
The simple fact is that Notes (the client) and Domino (the server) possess more features and are capable of a great deal more than Outlook and Exchange (again, the client and server respectively). Notes, for example, is capable of presenting mail with active content, while Outlook is not. Additionally, Domino can host many applications that Exchange cannot. As such, you might find that it’s a good idea to keep Lotus Notes available to ensure you have continued access to your current applications and active mail.
2. Run test migrations
In a world of rapidly developing technologies, it’s often prudent for a company to move large databases from older systems to new systems in order to ensure they do not become obsolete. This process is known as data migration. A common example of data migration involves moving Lotus Notes email files to Microsoft Outlook. However, converting Notes to Outlook manually is a difficult process; as a result, Microsoft has provided its users with the Exchange Server Migration Wizard. In this article, we’ll discuss the benefits of using the migration wizard, while also pointing out some of its limitations.
The benefits of Migration Wizard
When it comes to converting Notes Storage Format (NSF) files for Lotus Notes to Personal Storage Table (PST) files for Outlook, there are some processes that Exchange Server Migration Wizard can perform successfully. Some of these include:
As new technologies emerge, companies with large informational databases risk becoming obsolete if they don’t take steps to migrate their data from old to new. However, the data migration process is full of roadblocks; most organisations find that it’s never as simple as moving their data from one file system to another. In this article, we’ll take a look at four key tips to keep in mind for a smooth data migration process, from using the migration as an opportunity for spring cleaning to dealing with compatibility issues such as converting NSF to PST.
1. Use the opportunity for spring cleaning
Before you even consider beginning data migration, you need to understand and organise the data that is already there. Where is the essential data that needs to be moved? While you’re there, do some spring cleaning. There is bound to be unused data simply taking up space and adding to the difficulty of the data migration process. For example, it might be a good idea to only migrate the latest five versions of a given document, instead of all 40 of them. Get this part right and the rest of the data migration process is bound to go significantly more smoothly.
Lotus Notes, which stores its data in the Notes Storage Format (NSF), is fast being replaced by Microsoft solutions such as Exchange and SharePoint, which store data in the Personal Storage Table (PST) format. When it’s time to convert NSF to PST, however, the process is not as simple as it might seem. In this article, we’ll show you six steps to take in order to successfully migrate from Lotus Notes to Microsoft solutions.
1. Figure out what’s needed
The first step in any good plan is to take stock of what will be involved in the process. When migrating to Microsoft solutions, then, you need to figure out the user requirements for the new environment. Will your current infrastructure suffice for the new setup? If not, new infrastructure needs to be considered. The migration team must also ascertain which of the Notes features are mission-critical and ensure there is a way for these applications to be migrated without causing downtime.
2. Begin planning