Planning a Lotus Notes Migration

Successfully migrating Notes Users and Applications requires careful planning, excellent management and great teamwork.

And as in any job, the right tools make it easier. The IONET Notes Pipeliner provides export and migration services for Lotus Notes® Mail, Applications and Quickr® to XML, HTML, MHT, PDF, PST, Microsoft 365™, SharePoint® and Google G Suite/Drive.

Below we list common steps in a migration, and ways the Pipeliner can assist.
How the Pipeliner can assist in your Notes migration.

1. Planning

Flexible Source Data. You don't need to migrate everything. For Mail you could migrate the last 3 months of all Mail, but use Migration on Demand to catch any overflow. For Applications, you could first store little-used Apps as HTML or PDF, then migrate the remainder to SharePoint, or import Notes data into your new platform as XML. Use our Application Migration functionality to help you plan the best approach.
Experienced Resources. What will you need? Do you have sufficient staff, experience and computing power available, or do you want to outsource it to experienced professionals?
Flexible Execution. How do you want to perform the migration? Is it best to use a big-bang migration, pre-migrate some data up front and afterwards, or manage a period of co-existence between different systems?
2. Evaluate Migration Software

What software you use depends greatly on what your requirements are and how much you want to pay. The best approach is to evaluate suitable candidates and test them using your existing data. The Pipeliner allows you to test database migrations using a standard Notes Client as many times as you want, making it easier to evaluate.
3. Discover

Once you've decided the broad outline of your move, audit your environment to identify heavily-used, lightly-used and unused Applications, and the extent of distributed unsecured data such as local Notes Mail Archives.
4. Consolidate

Once you know the extent of your environment, consolidate it as much as possible, by uploading local Mail Archives invisibly, or asking your users to upload their own Archives.
5. Prepare

Backup. Take a full backup (at least the most important parts) of your existing environment.
Define Roles. Define roles for the migration, including deliverables.
Define Timelines. Define the expected timeline and milestones for events, including scope for delays.
Identify Risks and Issues. Create Risk, Issue and Progress Registers to document migration activities.
Contingency. Add enough leeway that you have time to adapt or backout if unexpected events occur, i.e. key people are suddenly unavailable.
Users. Get Business commitment and sign-off. Train users in the new platform and provide regular updates on the migration status.
5. Test

Test a subset of data to make sure you understand the timeframes, security and functionality required. The Pipeliner allows you to migrate the same data as many times as you want.
6. Pre-Migrate

Use the Pipeliner to pre-migrate data that doesn't change regularly, like old Mail or Contact Information. If it does change later, it'll be migrated again, but this process means a large percentage of your workload can be performed in advance.
7. Migrate

Perform the migration - switch Mail to your new system, migrate your Notes Applications and close access to Databases.
8. Backout or Continue

Use regular checkpoints and tests to ensure the main aspects are working as intended. If there are problems, decide if they're fixable or if you need to backout and restore the original environment.
9. Post

Make old Notes Mail available to users via Migration on Demand, and/or allow them to upload additional files after the migration. Store old Notes data as HTML or PDF on the Web for reference.
IONET SoftwarePO Box 57014, Mana
Wellington 5247
New Zealand
Tel: +64 4213 1278
info @