Hi. I'm going to be showing you a super quick demo of how you might migrate a custom Notes application using Quest's Notes Migrator for SharePoint product. So I'm starting in the migration console. And here, we've done a basic discovery of all the databases in my organization. So this is good for an analysis project and includes usage information, data complexity information, design complexity information, and so on.
So I'm going to select one of my databases-- the propose and development tracking database. And if this were a standard database, I would be able to just run one of the prebuilt migration jobs immediately. And you can migrate hundreds of applications in large batches that way.
Or since this is a one-off database, I'm going to go to the Migration Jobs tab in the Database Properties. And I'm just going to create a new migration job on the fly. So I'm going to Create a Source Data Definition that describes how I'm querying the data out of Notes. And let's do the selection based on the form used. And let's pick the Report form-- one of the forms in this application.
On the Data Fields tab, I can select Columns in different ways. In this case, I'll just select the fields that were on this report form. And now I've defined a query. And I could preview that and customize that if I wanted to. I could do things like put in formulas to massage data along the way.
But in this case, I'll just take all the defaults. And I'll go to the SharePoint tab. And I will create a new list on an existing SharePoint site. So let's select that site. And I'll call this Test Dev Tracking.
And I'll create a new list and add it to the quick launch area. And I'll create a Target Data Definition. And this is the description of how the columns will get written out in this new SharePoint list.
So I'll get to my Data Fields tab. And to save time, I'm just going to Load from Source Fields. So this is going to copy the schema of my Notes application over into a new SharePoint custom list.
And again, I could customize things. I could decide the area. I want to call this Product Area. And let's make this be a Choice field and automatically populate all the Choice values from the actual data. And I could similarly customize all my other columns if I wanted to. I'll just take the defaults for the rest of them.
I'm going to automatically map one to the other. So area in Notes will be mapped to Product Area in SharePoint, and so on. I'm going to preserve the metadata-- the Created Modified by Identities and dates. So if it says that Steve created this in 2007, it should still say that on the SharePoint side.
And in Security, I can map security at the list level, at the site level, or all the way down to the document level. And now, I'll go ahead and Run that job. So we're provisioning a new list on this SharePoint site based on the schema that we extracted out of Notes. And then we're migrating some documents.
So while we're still migrating a few documents, I'm going to go to this list immediately. And so if I edit one of these documents, you can see that we've migrated a nice looking document with a rich text field, including embedded images, possibly attachments, or doc links. And all these other fields, which came out of the Notes schema of that custom application.
If I edit this item, I can see that we have fields of different types. And, in fact, we created that Product Area field and provisioned it as a Choice field with all the legal choices that came out of the actual Notes database. So that's a very basic content migration with no bells and whistles.
And I showed you the migration of application content-- rich text, custom data, so on. If I wanted to, I could continue this process and start migrating the application design to bring over the original Notes form or some of the original Notes views. And we could look at migrating to different targets, not just list items, but to pages, libraries. We can generate Word documents, PDF documents, or migrate to SQL Server.
05:09