UncategorizedNo Comments

default thumbnail


This is the second blog on Agile PLM data migrations.  My prior post “Agile PLM Data Migration – Part 1: Anatomy of an Agile PLM Data Migration” covered the typical process I use while performing a migration and this post will aim to set the stage for a sample migration of a document object with the assignment of a revision, requiring a change order. As mentioned in the first blog, there are a lot of other posts and books on migrations but seeing it is a lot different than reading about it from a theoretical point of view (or from someone who hasn’t actually done one).

Imagine, if you will, that you have 10,000 documents to migrate.  All of which were released in the legacy document management system on different dates. This would be a great job for the DataLoad tool because we can easily create all change orders in a released status and assign the desired revision to the imported documents. This is a Oracle Consulting Services and Partner only tool designed specifically for data migrations. It has the ability to reproduce revision history and load most object types, not just Items. The purpose of this blog is not to provide a tutorial on the DataLoad tool, but rather to give a high level overview of how an Agile PLM migration can be accomplished with a real example.

Use Case

I have done many migrations where the source data is in a proprietary system or where the team is managing their documents and revisions in an excel spreadsheet. In these cases, I typically receive the Excel workbook as the source metadata and a file system for the attachments. Attachment names often begin with the item number or have a path in the spreadsheet to the directory the file are located in.

For our demonstration I will use a source spreadsheet with a single row of metadata and a file system where the attachment names begin with the item number. From this we can prepare the metadata for the Oracle DataLoad tool and also parse out the file system and build a manifest for the File Load tool (Java Client).


Here are the steps I will take for the migration:

  1. Import the spreadsheet into an Oracle database. Again, imagine I am migrating 10,000 documents with different release dates and a more complex data set.
  2. Run SQL against the imported spreadsheet for some clean up, validation and loading into the DataLoad schema
  3. Validate data in DataLoad
  4. Perform the Migration
  5. Import the attachment listing into Oracle
  6. Run SQL to build a file load manifest and export to a CSV file
  7. Run File Load to import attachments

Wrap Up

In the next post, I will walk through the first four steps to migrate the metadata. I will not be going over the DataLoad tool in depth but will show it and discuss its basic functionality so Agile customers can understand how it works at a high level.

Please do not ask for a copy of the DataLoad tool; you will need to engage OCS or an Agile PLM partner.

Be the first to post a comment.

Add a comment