Migrating from SP 2010 to SP 2013

I m new to sharepoint and our new project requirement is to migrate the contents from SP 2010 to SP 2013. we r not going to use any tools , so if we go manually what would be the approach to migrate the custom data to the next version. there is lot of custom
data like features, event recievers, webparts that we have to take care of . do we have to code them again or what .
in depth reply or even some forums link will do . thanks

Check out
http://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=124
All customizations will have to be tested again though, you can't expect them to work correctly. I would start by creating a list of customizations that have to be upgraded and still need to be supported
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Similar Messages

After Migrating from Sharpoint 2010 to Sharepoint 2013 list filter options changed

Hi All,
After migrating from SP 2010 to SP2013 i found list View filter option is changed and filter is not working Pls help its really urgent.... you can check field 1 and field 2 in following screen shot.
Prasad kambar

Hi ,
According to your description, my understanding is that your list filter cannot work after Migrating from SharePoint 2010 to SharePoint 2013.
For your issue, please check your log files for any issues. Also you can refer to the blogs for troubleshooting SharePoint 2013 migration:
Firstly try running Test-SPContentDatabase on your source database for any issues -
Test-SPContentDatabase - http://technet.microsoft.com/en-us/library/ff607941.aspx
Troubleshoot site collection upgrade issues in SharePoint 2013 http://technet.microsoft.com/en-us/library/jj219648.aspx
Verify database upgrades in SharePoint 2013 -http://technet.microsoft.com/en-us/library/cc424972.aspx
And please have a look at your custom solution on your site.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Planning a migration from Exchange 2010 to Exchange 2013

Hello,
I am planning a migration from Exchange 2010 to Exchange 2013 and I was wondering if there was a good guide on the UM migration. I haven't found one that isn't confusing as heck.

Hello,
Is there any update?
If
you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Change GUIDs when migrating from SP 2010 to SP 2013?

When migrating custom list schema from SP 2010 to SP 2013, do I need to change the GUIDs for all the fields or can I use them as is?
Thank you!

Hi,
After migrating SharePoint 2010 to SharePoint 2013, all the GUIDs of the sites and lists would change.
If you just wanted to use the list in the site, it would have no impact on the lists, all the custom lists would work well.
However, if you have some functions or solutions based on the GUIDs of the lists, you should change all the GUIDs for all the solutions.
Thanks,
Jason
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]
Jason Guo
TechNet Community Support

QuickEdit disabled after migration from SP 2010 to SP 2013

Hi,
I have a custom list. In SP 2010, I was able to use the Datasheet view to enter multiple data. I migrated the site to SP 2013, and the custom list, the Quick Edit is disabled.
I recreated a Datasheet view, but still it is not showing.
How to enable the Quick edit mode?
Thanks

Hi Venkatzeus,
You may try below steps.
Use or create a view that uses the Default view style for the list. To edit the selected view, follow these steps:
On the affected list, click the LIBRARY tab on the ribbon, and then click Modify View.
In the Style section of the Edit View page, click
Default, and then click OK.
OR
Go to the list settings> Advanced settings page
Scroll down and Under quick edit options just choose "Yes" and then click OK.
Let me know if it works for you.
Regards,
Amol

Trouble with publishing topology. Migration from Lync 2010 standard to 2013 standard.

Hi,
I have a problem with "Microsoft.Rtc.Applications.Testbot". When I publish the topology I receive an error, I've found many solutions to my problem. One of the best descriptions
I've found here: http://lyncme.co.uk/microsoft-lync-server-2013/unable-to-publish-topology-a-trusted-server-with-the-type-mcxinternal-and-fully-qualified-domain-name-fqdn/
I'm going to do the same method, but I do not understand whether I should remove both entries or only one. If I delete the record 2010, will the 2010 lync continue to work?

Hi Alan,
Lync is not that dependent on what is stored in Active Directory, and the topology builder should recreate any missing entries when it is rerun. I don’t think this operation is a high risk
for the deployment as a whole, but do be careful when using ADSI edit, it’s all at your own risk.
Here’s a similar case for your reference.
https://social.technet.microsoft.com/Forums/lync/en-US/01404c0c-ba63-4471-a5b2-8e110be451e3/lync-server-2013-topology-builder-errors-global-activation-?forum=lyncdeploy
Hope it can be helpful.
Best regards,
Eric

User migration from Lync 2010 to Lync 2013

We have Lync 2013 pool co-existence with Lync 2010 pool. Need to move users based on their AD Group membership. In a particular AD group, only few of the users are enabled for LYNC 2010, not all users. How to get the list of only Lync enabled users in AD
group and move them on to Lync 2013 by PowerShell script?
Thanks in advance for your help
Tek-Nerd

When I ran the below command
Get-ADGroupMember Mygroup | where {$_.msRTCSIP-UserEnabled -eq "true"}
on my Lync 2013 server, got the below error message...
At line:1 char:46
+ Get-ADGroupMember MyGroup | where {$_.msRTCSIP-UserEnabled -eq "true"}
+
~~~~~~~~~~~~
Unexpected token '-UserEnabled' in expression or statement.
At line:1 char:59
+ Get-ADGroupMember MyGroup | where {$_.msRTCSIP-UserEnabled -eq "true"}
+
~~~
Unexpected token '-eq' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordExcep
    + FullyQualifiedErrorId : UnexpectedToken
Tek-Nerd

Migrating From Exchange 2010

I am in the process of migrating from Exchange 2010 to Exchange 2013. I have all mailboxes migrated to Exchange 2013 and am ready to eliminate Exchange 2010 in its entirety, but I am unsure about public folders. We have no public folders other
than the default ones generated during the Exchange 2010 installation. I can't find anything in any of the migration guides that explain what I need to do in this case. Do I need to migrate anything, or can I just uninstall Exchange from the server
and ignore the default public folders?

Thanks. We had one person using Outlook 2003 years ago, but that has since been replaced with Outlook 2010. I was able to remove the "Calendar" folder that appeared in the Public Folder Manager (took me a while to see the "Delete"
link) and was able to proceed. It does not appear that I have caused any problems.

OWA still lands at Exchange 2010 for users migrated from Exchange 2010 to 2013

I never had any issues with OWA redirection for a few users that I migrated from Exchange 2010-2013 initially. For users that I am migrating in the past few days, the OWA 2013 is landing on Exchange 2010 despite the mailbox being successfully migrated to
Exchange 2013.
Troubleshooting:
1. I have restarted the IIS Services
2. I have restarted MSExchangeOWAAppPool.
3. I have also checked the homeMDB attribute of the 2013 migrated user with the Exchange 2013 database.
I would really appreciate if anyone could share their experiences on similar issues.

I have checked it, the migration status is completed. In regard to the namespaces, both CAS 2010 and 2013 are set to mail.domain.com; CAS 2013 is the internet facing. I have also checked the internal access for OWA, it's the same scenario. Migrating them
back to 2010 and 2013 won't resolve the issue in my case, because the issue persists for every new user that I am migrating.
I recently found the following when I login with a user who is not effected and then logout:
1. Login in back with the affected user without closing the browser or clearing the cache, it lands at CAS 2013 OWA.
2. However, I get the below listed error message when I logout.
Your request couldn't be completed.
Click here to continue working.
This may have occurred for security reasons or because your session timed out.

HT204350 Migrating from a 2010 MBP to a 2013 iMac - stuck halfway through???

I have begun migrating from a 2010 MBP to a 2013 iMac after installing mavericks on both. They are connected by ethernet. The MBP isn't updated to the latest version because it was installed from a previous copy from apple. The migration has started and is stuck on 1 hour19 mins, what should i do? is it safe to somehow stop the migration process? or is it best to leave it be for a few hours or something? i had a lot of trouble starting the process as i had to try multiple times to get it to locate all the files and folders on the MBP. Thanks for the help.

Welcome to Apple Support Communities
Leave it for some minutes to see if the migration process continues. If not, simply turn off both Macs, turn them on and transfer the files again.
If the migration gets stuck again, consider the option of making a Time Machine backup of your old MacBook Pro onto an external drive, and then use that backup to restore your files to the iMac. The steps to restore a backup from an external drive are the same.

Migration from sharepoint 2010 enterprise to sharepoint 2013 standard

Hi
I need to do migration from SharePoint 2010 enterprise to SharePoint 2013 standard. We have only one content database and no custom deployments. I had tried database attach upgrade method. After I run Mount-SPContentDatabase PS Command. First it ran well
for few minutes then it got stuck for hours and finally failed . Please let me know if anyone came across this situation. How to migrate from SharePoint 2010 enterprise to SharePoint 2013 standard? Thanks in advance.

Thanks norari,
Yes ,following are the errors that i got during migration.
Event 5586(SharePoint foundation) of severity 'Error' occurred 6 more time(s) and was suppressed in the event log.
Failure trying to synch
web application a1c11f44-3bc3-4cce-ad2d-e1a459c46c67, ContentDB
6681d540-313f-4ccc-a770-66608eecf3be
string1
System.Data.SqlClient.SqlException
(0x80131904): Invalid object name 'TVF_EventCache_ReadPast_LEQId'. Invalid
object name 'TVF_EventCache_Id'. at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean
breakConnection, Action`1 wrapCloseInAction) at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at
System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand
cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler,
TdsParserStateObject stateObj, Boolean& dataReady) at
System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at
System.Data.SqlClient.SqlDataReader.get_MetaData() at
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds,
RunBehavior runBehavior, String resetOptionsString) at
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32
timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior,
RunBehavior runBehavior, Boolean returnStream, String method,
TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean
asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String
method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior) at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand
command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean
retryForDeadLock) at
Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command,
Boolean retryForDeadLock) at
Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command) at
Microsoft.SharePoint.SPChangeToken.GetCurrentChange(SqlSession session,
Int64& changeNumber, DateTime& changeTime) at
Microsoft.SharePoint.SPChangeToken..ctor(SPContentDatabase db) at
Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.SynchContentDB() at
Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean
fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock,
FinallyBlock finallyBlock) at
Microsoft.Office.Server.UserProfiles.WSSProfileSyncJob.Execute()
ClientConnectionId:a1e477c3-5e3c-4e38-818b-18504ae9b5ce Error
Number:208,State:1,Class:16

ActiveSync stops working after migrating from Exchange 2007 to Exchange 2013

We have started the migration from Exchange 2007 to Exchange 2013. We've followed best practices and everything is working great except ActiveSync. I've performed Exchange migrations in the past so this is nothing new for me. I've also been referring to
a great guide which has been a big help,
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html.
Once a user is migrated from Exchange 2007 to 2013, ActiveSync stops working properly. Email can be pulled to the device (Nokia Lumia 625 running Windows Phone 8) by performing a manual sync. But DirectPush is not working. The strange part is it's not affecting
everyone who's been migrated. Anyone who is still on Exchange 2007 is not affected.
At first I thought it was our wildcard certificate. 99% of our users are running Outlook 2013 on Windows 7 or higher but we do have a few terminal servers still running Outlook 2010. Outlook 2010 was giving us certificate errors. I realized it was the wildcard
certificate. Rather than making changes to the OutlookProvider I simply obtained a new SAN certificate. Although that resolved the issues for Outlook 2010 users, ActiveSync was still a problem.
Rebooting the phones and removing the email account from the user's device and re-adding it didn't resolve the issue either.
Then I performed an iisreset on the CAS server. This didn't help either. I didn't know it at the time, but I was getting closer...
I tried using the cmdlet Test-ActiveSyncConnectivity but it gave me the following error:
WARNING: Test user 'extest_0d9a45b025374' isn't accessible, so this cmdlet won't be able to test Client Access server
connectivity.
Could not find or sign in with user DOMAIN.com\extest_0d9a45b025374. If this task is being run without
credentials, sign in as a Domain Administrator, and then run Scripts\new-TestCasConnectivityUser.ps1 to verify that
the user exists on Mailbox server EX02.DOMAIN.COM
I started reviewing how Exchange 2013 proxied information from the CAS to the mailbox server and realized the issue may in fact be on the mailbox server.
I performed an iisreset on the mailbox server and all of a sudden ActiveSync started working again. Awesome!
I can't explain why. The only thing I can assume is when some users were migrated from 2007 to 2013 something wasn't being triggered on the Exchange 2013 side. Resetting IIS resolved the issue. I guess I'll have to do an IIS reset after I perform a batch
of migrations. Disabling ActiveSync and re-enabling it for the affected users didn't help - only the IISRESET resolved the issue.
If anyone has any information as to why this happens, please chime in. Also, if anyone knows why I can't run the Test-ActiveSyncConnectivity cmdlet, I'd appreciate the help.
Thanks.

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

Cross Forest Migration from Exchange 2007 to Exchange 2013

Hi
Could anybody advice me the steps also the pros and cons for below mentioned environment if we are going for the cross forest migration.
Source
Domain - test.local
Active Directory - Windows 2003
Exchange Server - 2007
Target
Domain - test.net
Active Directory - Windows 2012
Exchange Server - 2013
Also if it is possible ,
How could I remove the source environment including the exchange servers. after the migration ?
Regards
Muralee

Hi Oliver ,
Please suggest us.
In my environment we are in a plan to migrate from exchange 2007 to exchange 2013 (cross forest migration).
Source : Exchange 2007 with sp3 ru 10
Target : Exchange 2013 with cu2 ( new environment yet to be created).
Trust : Forest trust in place (two way )
Domain and forest functional level : 2003 in both target and source
Migration Steps :
Step1 :
We are in a plan to execute 'preparemoverequest.ps1' first in the target forest ,so that we will get the disable MEU
in the target forest.
Step2:
Then we are going to use ADMT to migrate users SID'S and password .
Step3:
Then we are going to move the mailboxes with New-moverequest
Please have a look in to our steps and suggest us ,whether we are going to proceed the migration in a right way or not
.Is anything needs to be changed please intimate me .
Thanks
S.Nithyanandham
Hey there,
Sorry for taking a little while to get back to you, i've been busy working on Hosted Lync deployments!
Use ADMT first, then when using preparemoverequest.ps1 script using the -uselocalobject cmdlet. This will then tie it up to the ADMT migrated account.
More info in this thread here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/2916e931-36a0-4ba4-8c04-196dbe792b44/preparemoverequestps1-and-admt?forum=winserverMigration
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,MCITP:Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Migration from Exchange 2007 to Exchange 2013

We are migrating from Exchange 2007 to Exchange 2013. We have a new Exchange 2013 server will all of the roles installed, but none of the mailboxes have even been moved yet. We are seeing some of our users getting prompted to accept the self signed certificate
on the exchange 2013 server. Exchange 2007 server is still handling all of the mail flow and connectors. Any reason why some of our users would be prompted with the certificate for the exchange 2013 server even though their mailbox is still on exchange 2007.
Our users are on outlook 2010.
Ed
Ed

Hi,
Could you show us what is the prompt details?
According to your desciption,I recommend you refer to the following methods to troubleshoot:
1.Please check if outlook anywhere been configured to connect exchange 2013.
2.Ctrl+Right click outlook, use “Test E-mail AutoConfiguration” to check all the settings .
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11

After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11

Migrating from SP 2010 to SP 2013

Similar Messages

Maybe you are looking for