Migrating from Lotus Notes to Box®

The IONET Pipeliner provides migration services for Lotus Notes Applications to Box.

The following is a basic guide to the Box migration process.
Migrating from Lotus Notes to Box

1. Planning

Plan your migration to get an understanding of what's involved.

TickAudit the Environment. Use the Pipeliner to identify unused or older Applications, and handle distributed data such as local Notes Mail Archives and encrypted Mail.
TickIdentify what to Migrate. You might not want to migrate everything to Box - unused or older Applications can be archived to read-only formats like XML, HTML or PDF, and everything else migrated to your new environment.
TickGroup Applications together. Many Notes Applications can be grouped together, for example all Discussion Databases or all Teamrooms. Use a Profile document in the Pipeliner to specify the migration characteristics for these groups of Databases in one place, plus provide individual settings for custom Applications.
TickMigrate the oldest data first. Older, little-used Applications are good candidates for the first migration, to give you can idea of the process and migration speed in your environment.
TickUtilise Delta Exporting. Delta exporting allows you to migrate the bulk of your data in advance, then easily complete the process for new and modified data when the cutover date arrives.
2. Set up your Box environment

Just create a Box account.
3. Configure Box access

Configure Box access as per the Box SDK setup instructions in the Pipeliner Setup Wizard.
4. Add your Box credentials to the Pipeliner

Add your Box credentials to a Pipeliner Credentials document. Specify the JSON Web Tokens (JWT) file, ID or Developer Token returned by Step 3 above.
5. Install Box support

Install our Box support on your Notes Client or Domino Server using the Pipeliner Tools menu.
6. Add your Applications to the Pipeliner

Use the Setup Wizard to add Applications to the Pipeliner, which simplifies the setup process. You can also choose to add Databases manually, or use a Profile to add all similar Databases (e.g. all Teamrooms).
7. Define Box settings

As well as the default Box settings, you can set specific migration options for each Database.

TickFolder Hierarchy. Use fields and @formulas to define a Box Folder hierachy, e.g. based on Notes Document Categories.
TickCollaboration. Define Box Collaboration on Files or Folders, using Notes fields and @formulas, in conjunction with your Folders and the Box Waterfall Permissions model.
TickMetadata. Define Box Metadata for each uploaded Notes document using fields and @formulas.
TickNotes View Navigation. Recreate your Notes Application Views in Box to provide familiar navigation to end users.
8. Start Migrating

Migration takes place automatically, and the Pipeliner allows you to migrate the same data as many times as you want, so you can change settings to achieve the best result.
9. Results

Folder Hierarchy.
Your defined folder hierarchy is presented in Box, along with optional Navigation. In this case we've migrated a Notes Teamroom Database;
Folder Hierarchy Navigation.
Notes Views are recreated using the original Database Views, to provide familiar end-user navigation;
Navigation Notes Views.
In these Views, documents are presented as links;
Notes Views Document Rendering.
Documents are rendered using the original forms, with Metadata, Rich Text, Doclinks etc;
Document Rendering Responses and Attachments.
Response Hierarchy, Attachments and Embedded Objects are also supported;
Responses and Attachments

IONET SoftwarePO Box 77, Paekakariki
Wellington 5034
New Zealand
Tel: +64 4212 5656
info @ ionetsoftware.com
ProductsMigrating
Archiving
Search
Change
Workflow
CompanyContact
Support
Downloads
Partners