Thomas SegatoCarsten Wexel

Determine Business Case Information Assessment Design New Architecture Pre-Migration Considerations Perform Migration

Determine Business Case Why? SharePoint Online Office 365 Benefits Office 365 Concerns Hybrid Strategy

This is your chance to revisit your approach to Information management in your business: What is the business need?: Where can SharePoint fit into the IM Strategy? Align technology to IA Strategy Use the Business case to: Set and align Success criteria with stakeholders Identify how to measure success and value Identify and define Business drivers Understand key elements of the migration Align budget and cost Risk mitigated Budget Incorporate Adoption and Change Management Outline key dependencies

Business Intelligence Excel BI and Services Visio Searches PowerView and PowerPivot Search Strong search capabilities Rich contextual previews Enterprise Content Management eDiscovery Site Mailbox Record management SkyDrive Pro

Social Communities NewsFeeds Follow and tagging Yammer Support for Different Devises HTML5 APP Model New APP model Separation of logic and platform Public and private store

Simplified Deployment Allocate resources towards driving business value rather than maintaining infrastructure Predictability Easier to forecast cost of platform Faster Updates SharePoint Online updated before on-premises 90 day release cycles Integration Exchange, Lync, Project, Dynamics

Agility Faster solution delivery. Faster response to change in business demand and direction. Transparent scalability Focus Entire Office 365 service is “evergreen” Less underlying IT infrastructure IT resource redeployment Focus on new applications Tackle the “next ten projects” Line of Business enablement Economics Lower delivery costs

Lack of Control Cannot deploy full-trust solutions Cannot opt-out of updates Lack of Flexibility SharePoint 2013 Only Regulations Compliance, data sovereignty Data Loss No access to data without connection Migration Cost of migrating customization Integration with LOB systems

Workloads are divided across separate SharePoint environments Gradual transition to cloud Get the best of both worlds

Determine Business Case Assessment Design New Architecture Pre-Migration Considerations Perform Migration

Content Assessment Application Assessment

Document types Document sizes and average sizes Smallest and largest sizes Content size count Overall document count Database counts Site and site collection counts per content database Security Retention (Life Cycle) Audit/version Business value/Impact Sensitivity Confidentiality

MigrateArchiveDelete

ArchiveMigrate

Regularly accessed data Un-accessed data Rule Set criteria for cleanup Dark Data (File Share) Metadata tagging moves with data Know your classification requirements Versioning and Audit Integration

Application Inventories Business owner Business value/needs Aligned with buinsess strategy Impact / heatmap Complexity Integration Workload type Migrating cost

Determine Business Case Information Assessment Design New Architecture Pre-Migration Considerations Perform Migration

Upgrade/migrate to the cloud Upgrade to next version – sequential Leapfrog to the latest version

Things to look out for:  Storage requirements  customisations & Missing files  Changes in supportabilily limits  Orphaned sites  Patch level (not up to date)  Platform changes (Search, OWA, etc.)  Authentication type (Classic, Claims, etc...) The only built-in method supported and provided by the product

Things to look out for:  Storage requirements  customisations & missing files  Changes in supportabilily limits  Orphaned sites  Functionality in use  Running workflows  Depricated features  Load on resources (hardware and people) Requires 3 rd party tools or multiple upgrades

Things to look out for  Difference in capabilities  Not all workloads available in the cloud  Certain workloads are challenging in hybrid mode  Connectivity to other systems and their locations  Existing solution-specific customisations/managed code  Licensing costs for 3rd party migration tools, support, etc.  Future plans with regards to customisations, integration, etc.  Amount of data to be migrated and throughput targets during process Requires 3 rd party tools or manual migration

What workloads are currently in use (Service Description)? What is the size of environment (Online Boundaries)?

From complex to simple Can exiting code run in SharePoint Online Can we refactor complex to standard Integrations Is or can existing integrations be public Can we move integrations to Windows Azure Third party in house Do you have the code Is it under support

Changing of authentication model can be complex Plan to upgrade authentication model to claims

Who owns the environment? Who manages the environment? Who has access to the environment’s servers? How skilled is your organization on the new version of SharePoint? Operations team Development team Support organization

Project Management Skills & Experience Support within the Organization External or Internal Project Management approach (ITIL, Agile, Ad-Hoc, etc.)

Determine Business Case Information Assessment Design New Architecture Pre-Migration Considerations Perform Migration

Defined as any significant change that: Requires changing client software to match server Requires retraining to use existing abilities

No such thing as zero downtime!!! Possible to reduce downtime using mitigation processes Use Test runs to predict outages

Know what performance you have and what you want Measure existing performance Measure target environment standard Measure target environment with customizations - baseline

Should avoid URL changes whenever possible s Redirects in portals and sites Links from external systems Help users to find new links Create an application with from to parameters

Plan to inform users about upcoming upgrade requirements/events Include info on what will happen Indicate when upgrade will occur Indicate when upgrade must be completed by Indicate when upgrade is finished

Understand upgrade methods and processes Understand performance and downtime mitigation Gain experience and confidence in troubleshooting and validation

Determine Business Case Information Assessment Design New Architecture Pre-Migration Considerations Perform Migration

How to Migrate to Online

Can our ALM platform be moved to the cloud TFS online

Customization using the browser Customizations using supported tools and applications Access Excel Visio InfoPath SharePoint Designer Customizations using apps for SharePoint Other Download 3. party apps Develop apps for others Sandboxes solutions Still supported Use apps where possible

Look and feel Appearance on information Display content from different data sources Customize workflows for business processes Connect SharePoint Online to an on-premises SharePoint Server 2013 deployment

FIRST, TRY BROWSER- BASED OPTIONS THEN, TRY NO-CODE SOLUTIONS : THEN, CONSIDER CUSTOM CODE SOLUTIONS Change site logo, title and description Customize navigation Themes Apply custom css Use Design Manager -Master pages -Page layouts Visual Studio -Site pages -Ribon enhancements -Master pages Look and feel

Appearance on information FIRST, TRY BROWSER- BASED OPTIONS THEN, TRY NO-CODE SOLUTIONS : THEN, CONSIDER CUSTOM CODE SOLUTIONS Edit text and images Add and customize web parts Custom views SharePoint Designer InfoPath Visual Studio -Site pages -Custom web parts

Display content from different data sources FIRST, TRY BROWSER- BASED OPTIONS THEN, TRY NO-CODE SOLUTIONS : THEN, CONSIDER CUSTOM CODE SOLUTIONS Add standard web parts Excel and Excel Services Access 2013 and Access Service InfoPath Business Connectivity Services Visual Studio -Custom web parts

Workflows for business processes FIRST, TRY BROWSER- BASED OPTIONS THEN, TRY NO-CODE SOLUTIONS : Use the available “out- of-the-box” workflow Change the workflow attributes, such as approvers, due date Visual Studio SharePoint Designer Third parties like Nintex

Evaluate third party tools – need to know: POC Costs Capabilities What need to be migrated What kind of throughput can you get in your environment use measures from POC How can you manage deltas Read-only on source Delta runs of tools and scripts

Support Help (training, videos, wiki’) Operations (o365 operations panel) Daily. Weekly and monthly tasks Processes Governance Site provisioning Reference architecture Code guidelines

Retire customizations What remediation needs to be done in legacy production prior to migration Develop a map between the existing and target Information Architectures Cleanup - archive or delete

Verify capabilities Understand the tools – test settings Verify and measure throughput Involve stakeholders in quality assurance and acceptance Incorporate learnings

Automate where possible Transition strategy Freeze periods Gradual or big bang

Migrate sites Freeze source farm – read only if possible Sync deltas Testing and acceptance Address defects Cutover Support

SharePoint 2013 farm Office 365 tenant of E1 (search only), E2 or E3

Upgrade service applications us/library/ee aspxhttp://technet.microsoft.com/en- us/library/ee aspx Upgrade services farms us/library/cc aspxhttp://technet.microsoft.com/en- us/library/cc aspx Configure shared services cross farms us/library/ff aspxhttp://technet.microsoft.com/en- us/library/ff aspx SharePoint 2013 and O365 hybrid us/library/jj aspxhttp://technet.microsoft.com/en- us/library/jj aspx

Determine Business Case Information Assessment Design New Architecture Pre-Migration Considerations Perform Migration

Evaluation Create a Text message on your phone and send it to 1919 with the content: PR I liked it a lot Session Code Carsten Performance (1 to 5) Match of technical Level (1 to 5) Relevance (1 to 5) Comments (optional) Evaluation Scale: 1 = Very bad 2 = Bad 3 = Relevant 4 = Good 5 = Very Good! Questions: Speaker Performance Relevance according to your work Match of technical level according to published level Comments Thomas Performance (1 to 5)

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.