Tag Info

Hot answers tagged

46

Just moved (drag & drop) a file in Explorer View from one document library to another, and it did retain previous versions! Obviously both libraries need to have versioning enabled. Try it yourself. EDIT: note that it ONLY retains the versions if you MOVE the files. It does not do so when you perform a COPY!


10

As Sean says one option is to make a template, and create a new list using that. http://grounding.co.za/blogs/neil/archive/2008/10/05/moving-a-list-with-content-between-sharepoint-servers.aspx If its simple you can perhaps use the DataSheet view to copy and paste the data to the new list if you've already setup the structure. You can IIRC do a ...


9

If the WSP has any assemblies in it - no. The assemblies developed for SharePoint 2010 will be referencing the SharePoint 2010 core assemblies, and will fail when trying to load them in SharePoint 2007. If the WSP only has XML in it, and no server side code in assemblies, it should deploy fine, given it has no Feature code that's new in 2010 (such as ...


8

This is a big topic. There are two main ways of doing this - "in-place upgrade" and "database attach". There is no "gradual upgrade" option, as there was with SP2003. In-place upgrade is easier because you keep the farm configuration. The drawback is that your sites will be offline while the upgrade runs. There is also the slight risk that if something goes ...


7

Last year I added functionality to Chris O'Brien's SharePoint Content Deployment Wizard to copy documents from one library to another. I'm pretty sure I tested that versioning copied over as well. Have a try of that and if you have any problems using it please leave me a comment here and I'll update my answer with more info.


7

When prepping for an upgrade you will want to run the pre-upgrade check on 2007. It was originally introduced with SP2, but improved with the Oct 2009 CU (also included in SP3). This will analyze your farm and also provide a detailed list of all features installed or referenced. Any missing features will be identified by GUID and must be cleaned up prior ...


6

Quest Migration Manager allows you to go from 2003 to 2010 as does Metavis Migrator and Metalogix Migration Manager.


6

Update: The more structured and concise step-by-step description by Puhan. The answer to this question is the same as answer(s) to question Infopath change Publish Location Update: Though the marked as best and the most upvoted there answers proposing the use UDCX data connection files are not applicable to Infopath Form templates of ...


5

I would use the SharePoint Content Deployment Wizard tool by Chris O'Brien on CodePlex. http://spdeploymentwizard.codeplex.com/ You can backup/restore from individual files/lists/libraries all the way up to full site collections.


5

I think the best solution is to open the document library in an Explorer window (using WebDav) and move or copy stuff around that way. You could also use the Site Content and Structure site action (you need to have the publishing feature enabled on your site) and select all the documents in the folder and move them to a new folder. But this tool is not able ...


5

No, import/export can only be done to farms of the same version. You could Add a new content database to your 2007 web application move the single site collection to the new database Run pre upgrade check Attach and run Test-SPContentDatabase on the 2010 server Then upgrade with Upgrade-SPContentDatabase Then move the site collection from the upgraded ...


5

I can think of a couple of problems with this. First you will need to make sure that your SharePoint 2007 farm is patched to the latest version to ensure it is supported on Windows Server 2008 R2. Also, you may need to slipstream the latest service pack in order to install on Windows Server 2008 R2. You will be creating a new SQL Server machine and moving ...


5

You have two options, and your choice will ultimately be determined by how many pages you have and how many of those need to be "modified" before / during the migration. Use a 3rd party migration tool There are now a number of great proprietary tools on the market (some free) which allow you to migrate publishing page content into SharePoint 2010. Here is ...


5

You are correct in that there isn't a direct path from 2007 to 2013. You will need to upgrade 2007 to 2010 first and then upgrade 2010 to 2013. My suggestion to you would be to setup a new virtual environment (you could even use the demo VMs you download from Microsoft) for 2010 and 2013. Then using the database attach method, migrate to 2010 and then to ...


4

If the content is in a content database with no other content, you could backup the content db and move it and then attach it in the new farm. If it is not, you can use the command line stsadm.exe -o backup -url [yoursitecollectionurl] -filename [filename] to back the file up on the current server, then copy the file to the new server and use the command ...


4

As Anders mentions in his answer, my company SharePoint Products has a tool named CopyMove for just that. It is free to use for 1 named user - only organizations that need to offer the tool to their end-users will need to purchase a license. The product can copy/move documents, list items and folders with no loss of metadata, version history and ...


4

If you read this article by Thao Nguyen at Bamboo Solutions you will find 4 different methods for migrating a list from SharePoint 2007 to SharePoint 2010. My preferred method is number 1: Method 1 - Migrate a single list from SharePoint 2007 to 2010 using a list template Save the list as a list template (".stp" file). Download the list template Change ...


4

Theres several ways to do this. One is to export the list using "save as template" and check "include content". Theres limitations on that approach depending on list size. AFAIR the limit here is 2 gb. Another way is to simply restore the database into your dev machine and get to the list from there. EDIT: Just saw you were using SP2010. In Central ...


4

This answer is for WSS3.0 but all the same applies to SharePoint 2010 Which is the easiest way to migrate entire List to a new new site? As you are talking about from production to dev I am assuming that you're talking about a rolldown type procedure so you may want to check out Gary Lapointes STSADM gl-exportlist and gm-importlist extensions because as ...


4

I don't think it is possible to change the internal column name of a field after it has been created (only display name). You'll need to specify the name before it is created in SharePoint. What we normally do is create the column name with only alphanumeric characters (less than 32 characters) and then rename it. For example, if my survey field is called ...


4

If you didn't already - upgrade your MOSS 2007 Farm to SP2 + October 2009 Cumulative Update (or newer), then go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin and type in the command: stsadm -o preupgradecheck This command won't change anything in your farm, but will generate a report about your farm health, customizations, ...


4

You cannot restore a content database to a prior version (major or minor). You also cannot restore a site collection. This is by design, and any attempt to change that can lead to instability and you will not be supported by MS. You will need to upgrade the destination system to the same version; SP1 and any CUs if installed. If the patch failed to ...


4

No. You will almost certainly need to make modifications. Migration tools will only work perfectly on the most simple applications, and even they can have problems. The more features of the core libraries that your systems make use of, and the more assumptions that you have been working with about "the way things work" in SP, the more problems you will ...


4

You should pass the same user name as OldUser and as NewUser, note the IgnoreSID parameter. This will get new SID from AD for that account and update that in userinfo tables. Move-SPUser -Identity "DOMAIN\OldUser" –NewAlias "DOMAIN\NewUser" -IgnoreSID Source


4

Are you missing custom solutions in your new 2010 farm, that exist in the 2007 farm? Compare the installed features/solutions in both farms. However, you really should upgrade to SP2. The preupgradecheck stsadm command was added in SP2 and is very good at identifying where you're going to have issues. The upgrade alone may even solve your problems.


3

a way to move documents through doc lib is to use the Content Deployment API. using objects like SPExport and SPImport the copy, move actions of the content site and structure (sitemanagement.aspx) are performed using this API. and you can set that you want to keep the versions!


3

found it. the best way is to export the list to a spreadsheet in 2007 and then import that xslx file in 2010. I found this article very useful: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?List=56f96349-3bb6-4087-94f4-7f95ff4ca81f&ID=91 by the way, I faced a problem when exporting to excel if the site is using forms based authentication with ...


3

I know of no OOTB way to do this, so you would have to code this functionality yourself. I know that Lars Fastrup has created a tool that does just what you want: CopyMove for SharePoint It also has a web service API. hth Anders Rask



Only top voted, non community-wiki answers of a minimum length are eligible