SharePoint 2010 data migration

esps used Ask the Experts™
Hi Experts,
I have implemented SharePoint 2010 at a company.
As part of the business strategy and to ensure that mistakes of the past is not repeated, strict business rules, taxonomies and metadata requirements are enforced onto documents when checked into the system.
This all works very well!
BUT and as always there is a but!
The legacy data/documents that is on two previous platforms (MOSS 2007 and LiveLink) needs to be migrated.
Now we are talking many,many plus many documents that now obviously does not conform to the new tags.
Obviously to migrate and save them one by one will take a year.
Would there mabe be a workaround whereby one could perhaps use something like Aspose or whatever method to migrate documents in grouped batched and change the taxonomies and metadata on the fly upon a batch/mass load of logically grouped documents like for example five hundred similar contracts.
Would appreciate any ideas
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Justin SmithSr. System Engineer
Top Expert 2012

You could upgrade the legacy site to 2010.  Then create a powershell script to migrate the documents from one library to the other, while changing metadata during the migration.
As a former developer I am more pro a SharePoint API migration. The fact is that you can use the API to talk to SP2007 to extract the documents and their information in a specific format. For example:
document library 1
Together with the document (or document libraries) you can add a csv file that lists all the files (and maybe their subfolders as well as metadata)
You can then send those CSV files (based on the document libraries) to the people of the business and have them fill in the xls. What I would add (but that is up to you) is a possibility for them to specify if the column needs to be a lookup column or a managed metadata field. Example of the csv

document,description,text,responsible,user,division,lookup,Division,Field of Expertise,MMS,Expertises/IT
doc1x.docx,this is doc1,vosters\koen,division1,SharePoint 2007
doc1x.docx,this is doc1,vosters\koen,division2,SharePoint 2010

Your custom code can then, looking at the first line, do the following
- Create a content type
- Create columns
- Create the lookup list (Division) if it doesn't exist
- Create the group Expertises/IT

In the second line, it can then do the following actions
- Read the lookup field
- Check if the field Division 1 already exists in the Division lookup list, if it doesn't, add it, if it does, reference it
- Check if the Term set SharePoint 2007 already exists in the MMS, if it doesn't, add it, if it does, reference it
- Upload the document
- Set the metadata

It requires quite some custom coding, but you give people the tools they know (Excel with some explanation) to put in the metadata. And they have an easy way of putting content in and sending it back to you.


Hi KoenVosters,

Your approach certainly looks logical and I like the Excel idea.
Can you perhaps provide me with links to sample code (for the API extraction) and/or case study.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial