How the Pipeliner can assist in your Notes migration.
You don't need to migrate everything. For Mail you could migrate the last 3 months of Mail
to production, and everything else to an archive. 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.
What will you need? Do you have sufficient staff, experience and computing power available, or do you want to outsource it?
How do you want to perform the migration? Is it best to use a big-bang migration
, pre-migrate data up front then afterwards, or manage a period of co-existence between different systems?
What software you use depends mainly 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.
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 data such as local Notes Mail Archives.
Once you know the extent of your environment, consolidate it as much as possible, by uploading local Mail Archives invisibly
Take a full backup - at least the most important elements - of your existing environment.
Define roles for the migration, including your deliverables.
Define the expected timeline and milestones for events, including plenty of scope for delays.
Identify Risks and Issues.
Create Risk, Issue and Progress Registers to document migration activities.
Add enough leeway that you have time to adapt or backout if unexpected events occur, i.e. if key people are suddenly unavailable.
Talk to Users.
Get Business commitment and sign-off. Train users in the new platform and provide regular updates on the migration status.
Hold regular Project meetings with all members of the migration team, to provide project visibility and identify any potential conflicts or problems.
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
Use the Pipeliner to pre-migrate data
that doesn't change regularly, like old Mail or Contacts. 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.
Perform the migration - switch Mail to your new system, migrate your Notes Applications and close access to Notes Databases.
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.