Sharepoint 2007 to Sharepoint 2010 migration

Hi,
Does Microsoft recommends/support below techniques for SharePoint 2007 to SharePoint 2010 migration?
Migrate SharePoint 2007 site to 2010 using save list as template technique: I use this technique. I have to delete all look up columns and add them again. Because I deleted all look up columns, I lost data of those columns. I am not able to update these
columns data using spreadsheet view copy and paste as those are look up columns. Please tell me what is the easy way to update these look up columns data. After I move it production again I have to do incremental update.
Migrate SharePoint 2007 site to 2010 using an Access table technique: This technique does not support all data types.
Migrate SharePoint 2007 site to 2010 using Power Shell STSADM command: As in my site there are some customization I am not able to migrate site using STSADM command. It is giving me errors.
Thanks,
Amit Khatri

hi
mentioned techniques can be used for copying the data across different web apps/farms within the same Sharepoint version (i.e. from SP2007 to SP2007 or from SP2010 to SP2010, but not from SP2007 to SP2010). If you need to perform upgrade from SP2007 to SP2010
you have 2 ways:
- in-place upgrade
- db attach upgrade
Check the following post for more details:
Upgrade single SPWeb from Sharepoint 2007 to 2010.
Blog - http://sadomovalex.blogspot.com
Dynamic CAML queries via C# - http://camlex.codeplex.com

Similar Messages

Steps for Migration from SharePoint 2007 to SharePoint 2010?

Hi All,
Can any one tell the steps for migration from SharePoint 2007 to SharePoint 2010.
Thanks in advance!

This is the official communication:
http://technet.microsoft.com/en-us/library/cc263212.aspx
and this is a step by step guide:
Step by Step inplace upgrade to SP2010
Hope it helps!
Thanks, Ransher Singh, MCP, MCTS | Click Vote As Helpful if you think that post is helpful in responding your question click Mark As Answer, if you think that this is your answer for your question.

SharePoint 2007 to SharePoint 2013 Upgrade - Need to Goto SharePoint 2010 First?

All,
I've seen some posts that say one can go from SharePoint 2007 to SharePoint 2013 - without upgrading to SharePoint 2010. Other posts say otherwise.
Therefore, what is indeed the answer. Ideally I'm looking to stand-up a new SharePoint 2010 or SharePoint 2013 farm then likely do a detach then upgrade of the SharePoint 2007 content databases to SharePoint 2010 or 2013.
Thanks

If you want to do a standard SharePoint upgrade, yes you must go to SharePoint 2010 prior to 2013. If you want to use a 3rd part/in-house custom application content migration upgrade, then you can go straight from SharePoint 20xx to 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Move library and folder from SharePoint 2007 to SharePoint 2010?

Hi, I want to move two libraries from SharePoint 2007 to SharePoint 2010
And also there is one folder (in another third library) want to SharePoint 2007 to SharePoint 2010 library.
Can I use Export command for library in SharePoint 2007 and Import in SharePoint 2010?
And how to move folders?

Hi Prakash,
You can use third party tools like Metalogix which free for up to 25 GB data
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/4347677b-b232-428b-a6cf-8d43034fa353/move-files-and-folders-from-sharepoint-2007-to-sharepoint-2010-with-same-attributes?forum=sharepointadminprevious
If you donot to keep the metadata then you can use windows explorer
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/b0569a5f-dd30-45a1-87d9-ee1eb28f258d/migratemove-document-library-from-sharepoint-2007-to-sharepoint-2010?forum=sharepointadminprevious
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

Third party tools to upgrade sharepoint 2007 to sharepoint 2013

I'm looking for third party tools that can be used to upgrade sharepoint 2007 to sharepoint 2013. Any suggestions?
Thanks,
JohnWeb

Hi,
To migrate from 2007 to 2013 directly. I believe AvePoint and possibly Axceler have such products.
https://social.technet.microsoft.com/Forums/office/en-US/f46e4593-1283-4aec-bd63-564779883ac8/upgrade-moss2007-to-sharepoint-2013?forum=sharepointadmin
http://social.technet.microsoft.com/wiki/contents/articles/15743.sharepoint-2013-upgrading-from-sharepoint-2007-q-a.aspx
http://www.threewill.com/the-final-four-or-five-sharepoint-migration-tools/
Regards
Prasad Tandel

Delta migration on sharepoint 2007 to sharepoint 2010

To
SharePoint2010 Dear All ,
I am working on (SharePoint 2007 – SharePoint 2010 – SharePoint 2013) migration project . I need to do content database migration from one environment to another and many sites are suggesting the Content Database attach approach. It is working fine but doing
in production it’s taking more time minimum one week to complete this process.
I want to take the incremental backup of MOSS 2007 Content DB (only modified or newly added data )only with one week of updated data and restore in SharePoint 2010 and 2013 Environment .Kind of Delta migration.
Please advice on this.
sarav

If you want to do that the only approach I see is use a 3rd party product such as DocAve and Quest to do delta migrations.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

How to migrate search configuration and db from SharePoint 2007 to SharePoint 2010

hi all
currently we have a plan to migrate sharepoint 2007 farm to sharepoint 2010 with sp2 version. we have used the ssp, and only the search function.
Now the search db is quite big.
we have to use the database attach way to do migraion, because the old system must be online in 24 hours per day.
what i want to know is can we migrate the search db directly instead of recreate content source and reconfigure the search and do full crawl?
thanks.

Hi,
Below links should help you
http://technet.microsoft.com/en-us/library/gg593614(v=office.14).aspx
http://msdn.microsoft.com/en-us/library/office/ff828776(v=office.14).aspx
http://www.orcsweb.com/blog/cory-granata/sharepoint2k7-to-2k10-migration-using-db-attach-method/
http://technet.microsoft.com/en-us/library/cc263403.aspx
Please remember to click 'Mark as Answer' on the answer if it helps you

Post migration Nintex workflow isse (sharepoint 2007 to Sharepoint 2010)

SharePoint2010
Conversation Options
SG
SARAVANAN GAJENDRAN
SARAVANAN GAJENDRAN
To
SharePoint2010 Hi ,
I have migrated Nintex workflow from shrepoint 2007 to sharepoint 2010 after migration one of the workflow is not working .
I am getting the below error .please advise on this .
Tried to export the perticular workflow from sharepoint 2007 and imported in sharepoint 2010 .
Workflow Messages
Time Event Message Outcome
3/2/2015 7:33 AM Workflow Comment Document Creation (v1.60)
3/2/2015 7:33 AM Workflow Comment Error checking in item. The workflow failed because the action requires the document to be checked out. Error
3/2/2015 7:33 AM Error An error has occurred in Document Creation 1.
Please advise on this
sarav

Hi Sarav,
From the error message, it seems that it needs to check out the document first to make the workflow to be executed.
I recommend to check if “Require documents to be checked out before they can be edited” is set to Yes in the Versioning settings of the library where the workflow associated.
If yes, please set it to No and then run the workflow to see if the issue still occurs.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

SharePoint 2007 (WSS 3.0) migration to SharePoint Foundation 2013

Hi
I have a requirement to migrate a SharePoint 2007 (WSS 3.0) farm to a SharePoint Foundation 2013 farm. The WSS 3.0 farm has SQL Server 2005 Standard running so no restrictions on the size of the content database. The SharePoint Foundation 2010 and 2013 farms
will share the same SQL Server 2012 Standard instance (as I know WSS 3.0 will have to be migrated to 2010 before 2013). I also have two other WSS 3.0 farms (so three WSS 3.0 Farms, lets call these A (250GB), B (90GB) and C (60GB)) that I need to migrate
into WSS 3.0 Farm A before the migration to SP 2010.
My question is, can I migrate a 400GB WSS 3.0 site collection to SP 2010 or will I have to split this into separate site collections? I have read that there is a best practice limit of 100GB per site collection but this does not stop a larger migration from
happening. Obviously over time when the migration has completed to SharePoint Foundation 2013 the single site collection will grow and grow so perhaps now is the right time to split this out into, say, year named site collections, but surely this will incur
an end of year process to create new site collections and a custom dev headache due to different locations to send newly created sites?
Thanks.

The answer is Yes, and you are correct about the best practice of a limit of 100GB,
although, document and record centers (e.g. non collaborative) can go much higher.
http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#ContentDB
That being what it is, your sites will perform better if you find a topology that allows the content databases to be under 100GB each. You can use Move-SPSite to accomplish that feat.
You'll want a separate instance for 2010 and a separate instance for 2013
and finally, put some quota's in place and then governance document\statement that informs users that 100 GB is the max for any given site collection that uses collaborative features (calendars, lists, workflows, etc.)
The simple path is explained on technet, go from 2007 to 2010 (you can inplace upgrade if you want) then go from 2010 to 2013, database detach and attach is only way.
please check the below link that explains more about the migration from share point 2007->2013.
http://technet.microsoft.com/en-us/library/cc262483(v=office.15)
Stacy www.sharepointpapa.com

Exchange 2007 to Exchange 2010 Migration

Hi all,
I am migrating to exchange 2007 to exchange 2010 .This is not a migration data only migration like i am exporting mailboxes and importing it to new mailboxes .But email address and SAM account name will be same as per the source.Post migration i will point
the auto discover to new organisation.May i know what will be the impact to users??need to reconfigure outlook profile or does it will look for auto discover and prompt for new email id?
Jayakumar K

Is it in the same forest of or both the servers are different forest?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Sharepoint 2007 into Sharepoint 2010 migration MOUNT-SPCONTENTDATABASE fails and Sharepoint management shell closes automatically

Hi all,
I am trying to Migrate from sp2007 into sp2010. I have a heavily customized site with lots of sites, lists etc totalling upto 180GB size. Now when i perform Mount-spcontentdatabase, the command prompt ie Sharepoint Management shell closes after a certain
period of time eg 18%. Now, if i try to re-run the command again, the database is locked, as it might still be running something in the background.
Also, i tried running the Upgrade-Spcontentdatabase with forcedeletelock as true, so it unlocks and then upgrade, still with no luck
So quick question Can i run the Upgrade-spcontent command before running Mount, as i noticed my database version is old and need to be upgraded. Or Mount should def be run before upgrade regardless if the database is old or not?
Would really appreciate if someone could answer this soon?
Thanks in advance
cheers
Ren

what is the version of the SP2007, if database required upgrade then you should do this in 2007, once status says "no action required" then migrate to 2010 & mount it there.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Migrate a List from SharePoint 2007 to SharePoint 2010

There's a SharePoint List in the 2007 server having some 32 SiteColumns. None of the columns are of type LookUp i.e., there is no dependency of any column over any other Lists. I just need to copy it as it is to 2010 server. Only problem is that it has got
items worth more than 10GB size. [The list has many video attachments]
Saving the List as template along with its contents is certainly not an option. What I am proposing is to export the entire List to a number of "DAT" files using powershell and then again import the same to the 2010 server. This definitely includes
manually changing the version of the List from 12 to 14 after export.
Plz advice if there's any better alternative to do this.

hi
also check Migration Manager for SharePoint, which may migrate content from older SP versions to newer and has trial version. And of course it is always possible to write custom script
or console utility which will save all metadata to the file system and then import it to new SP version.
Blog - http://sadomovalex.blogspot.com
Dynamic CAML queries via C# - http://camlex.codeplex.com

Migrate Sharepoint 2007 to sharepoint 2013 questions

I am in the process of moving sp 2007 to 2013 using db attach/detach. I have some questions.
1) Should I do visual upgrade in 2010, then migrate to 2013 or wait until 2013 and do visual upgrade?
2) Should I convert to Claim in 2010, then migrate to 2013 or wait until migrate to 2013 then convert to claim.
3) What happen if i attached db that was ntlm to web application that currently use use claim?
4) any good article show step by step and things to look for?

1) You must do the visual upgrade to 2010 prior to migration to 2013. SharePoint 2013 does not support the 2007 UI look and feel.
2) Personally, I convert to Claims in SharePoint 2013. Given you're running 2013 SP1 with the April 2014 CU (I recommend Sept 2014 CU) or higher, the conversion will be quicker.
3) Windows Claims is just NTLM or Kerberos. You would need to re-covert. If you're converting in 2013, after you attach the Windows Classic-enabled db to the Claims-enabled web application, you would run Convert-SPWebApplication.
http://technet.microsoft.com/en-us/library/cc263299(v=office.15).aspx
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

TS4136 Apple Mail ActiveSync issue during Exchange 2007 to Exchange 2010 migration

When customer configures the ActiveSync account on Apple Mail (using Exchange Server 2010 CAS array name) for the user whose mailbox is on Exchange Server 2007, they are not able to get any mail and account displays offline. It shows the mailbox empty as well, even though mailbox has the email items in it.
But when same account is configured using ActiveSync (using Exchange 2007 CAS Server name) it works fine.
ActiveSync & Web Services URLs for Exchange 2010 and Exchange 2007 are given as below:
S#
Virtual Directory
URL
Exchange Server 2010
Exchange Server 2007
1
Web Services Virtual Directory
Internal URL
https://email2.domain.ae/EWS/Exchange.asmx
https://email.domain.ae/EWS/Exchange.asmx
2
Web Services Virtual Directory
External URL
https://email2.domain.ae/EWS/Exchange.asmx
https://email.domain.ae/EWS/Exchange.asmx
3
ActiveSync Virtual Directory
Internal URL
https://email2.domain.ae/Microsoft-Server-ActiveSync
https://email.domain.ae/Microsoft-Server-ActiveSync
4
ActiveSync Virtual Directory
External URL
https://email2.domain.ae/Microsoft-Server-ActiveSync
https://email.domain.ae/Microsoft-Server-ActiveSync
Following error is logged on Console on Mac when this issue happens:
30/10/12 3:27:28.398 AM
Mail
*** Assertion failure in -[EWSConnection _fetchRootFolderId:], /SourceCache/Message/Message-1278/MessageStores.subproj/EWSConnection.m:202
EWS fetchRootFolderId: expected one folder in response, received: 0
0   Message                             0x00007fff8cdeeef8 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 116
1   Message                             0x00007fff8cdef08e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 185
2   Message                             0x00007fff8cd1c8db -[EWSConnection _fetchRootFolderId:] + 768
3   Message                             0x00007fff8cd1deba -[EWSConnection _connectAndAuthenticateUsingAccount:] + 650
4   Message                             0x00007fff8cd1c42d -[EWSConnection connectUsingAccount:] + 462
5   Message                             0x00007fff8cd1996a -[EWSAccount authenticatedConnection] + 437
6   Message                             0x00007fff8cd2c00e -[EWSGateway connection] + 55
7   Message                             0x00007fff8cd2dddf -[EWSGateway sendMessage:forRequest:] + 43
8   Message                             0x00007fff8cd3e54c -[EWSRequestOperation executeOperation] + 108
9   Message                             0x00007fff8ce0f97f -[MonitoredOperation main] + 228
10 Foundation                          0x00007fff94aae6b4 -[__NSOperationInternal start] + 705
11 Foundation                          0x00007fff94ac1912 ____NSOQSchedule_block_invoke_2 + 124
12 libdispatch.dylib                   0x00007fff8adc8a86 _dispatch_call_block_and_release + 18
13 libdispatch.dylib                   0x00007fff8adc9965 _dispatch_worker_thread2 + 255
14 libsystem_c.dylib                   0x00007fff8a32c3da _pthread_wqthread + 316
15 libsystem_c.dylib                   0x00007fff8a32db85 start_wqthread + 13

Hi Akebono,
Let's check a few things in your server:
1. From the Organization Configuration - Client Access - Exchange Activesync policies - Default: Verify if the option "Allow non-provisionable devices" is ON.
2. From Server Configuration - pointing <YourExchange2010> - Certificates: Verify if your SSL certificate is assigned to IIS. (You should also be able to see this certificate from OWA https session)
3. The problem may also reside in iPhone outdated software, try to test activesync connection from iPhone with the latest OS version.
4. Take a look at logs in C:\inetpub\logs\LogFiles\W3SVC1\ of Exchange 2010, those might give some more details on connectivity problems.
5. If you still experience such problems - post the ExRCA error report here.
▲ Vote if Helpful / Mark if Answer
MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
MaximumExchange.ru

Remove bad dll reference after content data migration sharepoint 2007 - sharepoint 2010

I have 400 subsites under one root site and we need to remove one DLL reference from default.aspx Home page of each sub site.
Assmbly ref like this.
<%@ Register TagPrefix="WpNs0" Namespace="DS.DSQueryWebPart" Assembly="DS.DSQueryWebPart, Version=1.0.0.0, Culture=neutral, PublicKeyToken=709ed70a96eaa5cb"%>
This assmebly is not used anywhere .
This assembly is reflecting in subsite default.aspx after the content database migration sharepoint 2007 to sharepoint 2010.
Is there any way we can remove this bad reference through database query or any other way around
sarav

Hi,
If are sure that this is the only customization in the default.aspx page, then you can safely go into Site Settings -> Site Actions -> Reset to site definition -> Select Reset specific page to site definition version and enter the default.aspx
page url. This will replace the customized page with the original site definition page. The process can be automated using PowerShell/C# Code. Here is an example:
using (SPSite site = new SPSite("http://aissp2013/sites/Team/"))
foreach(SPWeb web in site.AllWebs)
using(web)
SPFile file = web.GetFile(web.Url + "/default.aspx");
if (file.Exists)
file.RevertContentStream();
The main part here is to get hold of the default.aspx file and use RevertContentStream() to reset it to site definition page.
However, if there are other customizations as well, then you will need to get hold of the Project or WSP file and remove the reference there and then run update-spsolution powershell command to update to new WSP.
Thanks,
Nadeem
Please remember to up-vote or mark the reply as answer if you find it helpful.

Sharepoint 2007 to Sharepoint 2010 migration

Similar Messages

Maybe you are looking for