SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are currently upgrading from an old version of SharePoint 2007 to 2010. One issue we have discovered is that once we are upgraded versioning did not come across. Not only do we not have prior versions of files, you have to go back into the files and turn versioning back on.

Anyone seen this issue ?

Because of our current configuration we are forced to do the database attach upgrade method. We have one additional step in that we are so far behind, we are going from 2007 SP1, attaching to SP2, then doing the database attach to 2010.

share

migration rejected from stackoverflow.com Apr 19 at 7:29

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as off-topic by Robert Lindgren Apr 19 at 7:29

  • This question does not appear to be about SharePoint within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

    
Well it depends on how you did your migration, was it an in-place upgrade, content database attach? basically you can have these upgrade methods - In-Place upgrade - upgrade is done directly on the production server. Versioning information is maintained. Keeps customizations and farm-wide settings Database attach - requires you to create a new farm on new hardware Versioning information is maintained. customizations are not upgraded unless you have solution deployment and scripted configurations Site backup/restore - somehow it never worked for me... – ukhardy Feb 23 '11 at 12:31
    
We used the Database attach method, but we lost our versioning information it was not maintained – Steve Feb 23 '11 at 23:58
1  
I've recently done an upgrade to 2010 from 2007 on a large intranet with many thousands of documents - and the old versions have been retained. From Microsoft's documentation of the recommended cleanup after upgrade (look for the 'remove extraneous versions' bit) it looks like versions are kept during an upgrade. So, sounds like something went wrong during your upgrade. Have you checked the upgrade log? Have you checked you have sufficient disc space etc? Did you try the [preupgradechecker](technet.microsoft.com/en-us/library/c – James Allen Apr 18 '11 at 13:50
    
I'm voting to close this question as off-topic because user is not seen and question is more than 3 month old with no upvoted answers – Robert Lindgren Apr 19 at 7:29