SharePoint 2013 The Essential Migration Process. in association with

Transcription

1 SharePoint 2013 The Essential Migration Process in association with

2 About Cygnet Infotech We are a global IT services & solutions provider. We provide custom software development services across technologies and domains to our clients in over 23 countries. We are ISO 9001, ISO and CMMi Level III Certified Learn more about us at

3 Code Less, Test More TestingWhiz is an Easy, Intuitive and Affordable Test Automation Solution that uses Keyword-Driven Testing and Data Driven Testing for Web and Cloud Application Testing m1 enterprise ordering systems provide a range of smartphone based ordering apps applicable for B2B, retail, restaurants and catalog companies

4 Today s Webinar SharePoint 2013 The Essential Migration Process Presenter: Jay Mehta SharePoint Consultant & MCT

5 Objectives The Essential Migration Process to SharePoint 2013 How to migrate the content database to SharePoint 2013 How to migrate the service applications database to SharePoint 2013 How to migrate the site collections to SharePoint 2013 How to migrate the user experience to SharePoint 2013 How to migrate workflows to SharePoint 2013 How to manage disruptions and downtime How to validate successful migration Q&A

6 The Essential Migration Process to SP 2013 Reasons to Migrate to SharePoint 2013 Obviously not for minor changes ROI Social Enterprise & WCM Strong and Effective Enterprise Search Sharing Increase End User Productivity Apps and the Marketplace Improved BI for Decision Makers Governance Automation Easy moving from SharePoint 2013 to Office 365

7 SharePoint Migration Process SharePoint 2013 Plan Prepare Test Implement Validate SharePoint 2010

8 The Essential Migration Process to SP 2013 Server Prerequisites Remove previous version of SharePoint. To use existing hardware Backup your farm using SharePoint backup tool OR PowerShell Uninstall Old SharePoint version and other dependent products Find more details on TechNet about Hardware and Software for SharePoint 2013.

9 The Essential Migration Process to SP 2013 End Client Software Requirement Office 2010 or Office 2013 Full Offline and integrated experience SharePoint Designer SPD 2010 only works for SP version 14 sites SPD 15 works for both SP versions 14 and 15 sites Web Browser Internet Explorer 8 or higher Firefox (Latest version) Chrome (Latest version) Apple Safari (Latest version)

10 Understanding Migration Process & Checklist Migration Methods Database Attach Supported Databases for Database Attach Method Content Databases Project Databases Search Admin Database Profile Database Social Database Managed Metadata Databases Secure Store Database Access Database

11 Understanding Migration Process & Checklist Migration Methods Database Attach Unsupported Databases for Database Attach Method Configuration Databases Sync Database Search Index Databases In-Place Farm Upgrade (NOT SUPPORTED for V2V)

12 Understanding Migration Process & Checklist Preparing Check list Content Databases Service Applications Farm/Web Application Farm Settings List down all the customizations Plan Upgrade Performance

14 Migrate Content Databases to SP 2013 Create a Web Application for Upgrade

15 Migrate Content Databases to SP 2013 PowerShell Commands SharePoint Farm Upgrade-SPFarm Content Database Mount-SPContentDatabase Test-SPContentDatabase Upgrade-SPContentDatabase SharePoint Site Test-SPSite Repair-SPSite Upgrade-SPSite

16 Migrate Content Databases to SP 2013 Migrate Content Database

18 Migrate Service Apps Databases to SP 2013 PowerShell Commands New-SPBusinessDataCatalogServiceApplication New-SPMetadataServiceApplication New-SPPerformancePointServiceApplication New-SPProfileServiceApplication New-SPProjectServiceApplication New-SPSecureStoreApplication New-SPSubscriptionSettingsServiceApplication Restore-SPEnterpriseSearchServiceApplication Upgrade-SPEnterpriseSearchServiceApplication Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings

20 Migrate Site Collections to SP 2013 Deferred Site Collection Upgrade Faster upgrade approach It is the replacement of Visual Upgrade feature Visual upgrade preserves old master pages, CSS and HTML files only where deferred site collection upgrade preserves many things, even Features. This upgrade allows you to use previous version of SharePoint UI seamlessly. Main difference Site Collection (SPSite) UI will be upgraded granularly instead of Site (SPWeb). Once the site collection is upgraded then it cannot be rolled back.

21 Page Rendering Coexistence

22 Migrate Site Collections to SP 2013 Feature Fallback Behavior SP 2013 Mode Lookups SP 2013 Features List SP 2013 Features SP 2010 Features SP 2013 Features Only Deprecated Features - Hidden SP 2010 Features List SP 2010 Mode Lookups SP 2010 Features replaced by SP 2013 Features SP 2010 Features Only SP 2010 Deprecated Features

24 Migrate Customizations & SP 2013 UI/UX Understand Customization Categories UI Information Structure Back-end Service Applications 3 rd Party Customizations SharePoint 2013 User Experience SP Mode 14 SP Mode 15

25 Migrate Customizations & SP 2013 UI/UX Copy Customizations to SP 2013 Farm

27 Migrate SharePoint OOTB Workflows Set up Windows Server 2012 server with SQL Server 2008 R2 / 2012 and SharePoint 2013 farm Copy the SharePoint Server 2010 Content Database(s) to the SharePoint 2013 Server farm i.e. Backup SharePoint 2010 content databases and Restore to target SQL Server A. Create SharePoint 2013 Web Application B. Attach and upgrade the content database(s) Upgrade the site collection(s) using deferred site collection upgrade method Activate and Verify SharePoint OOTB Workflows Feature

28 Migrate SharePoint Designer Workflows Enables SharePoint 2010 Workflows to work in SP 2013 Negotiates between two versions of SharePoint WF in SharePoint 2010 AWS in SharePoint 2013 Supports Stages and Loops, can call Web Services, WCF, REST & JSON Enhanced rich editor

29 New Workflow Activities and Actions

30 SharePoint Designer Workflow Stages Each stage has an entry point and gate Primary core in Workflow 4 flow step in a flow chart It can contain multiple steps Mitigates SharePoint Designer loop limitation

31 Migrating SharePoint Custom Workflows 1. Custom SharePoint Workflow Activities 2. Associated Custom Forms with Workflows A. Workflow Initiation Forms B. Workflow Association Forms C. InfoPath Forms compatibility 3. Third Party Workflows compatibility

32 An approach to Workflow Migration using Visual Studio Consider the SharePoint 2010 and 2013 GAC location 2. Modify.CSPROJ file of Custom SharePoint Solution Target Framework Version should be v4.5 Target Office Version should be Modify Package designer SharePoint Product Version = Reload the Project and verify the references to SP 15 API 5. Add your business / code logic to Web Service / WCF Services

34 Understand Downtime & Disruption Migration what can t be? PowerPoint Broadcast site collection Content Editor Web parts are no longer supported? Any replacement? Script Editor Web part. Performance URL Changes after the migration Governance and Notification Plan Customization Code and Codeless Farm Topology Clean-up the Environment

36 Validate Migration Review Logs Upgrade Logs Application Event Logs

37 Validate Migration Validate Migrated Environment Review and Validate Web Applications Review and Validate Services Validate External Data Sources InfoPath BCS Connections (External Content Types and External Lists) Excel Services connections External targets for Enterprise Search Authentication Providers Customization defects and fixes

38 Migration from MOSS 2007 SP 2013 Yes, It s possible!!! There is no need to stop at SharePoint 2010 Fact There is no direct migration from MOSS 2007 to SharePoint 2013

39 Write to us: To get free consultation on your SharePoint Migration queries Next Cygnet Infotech Webinar: Test Automation 3.0: Evolution of Rapid Application Testing Date: June 25, Visit to register