Migrating from a SharePoint On Premise solution or other Content Management System to SharePoint Online can be quite time consuming if done by hand. There are several other methods for performing this migration, including a script based migration, developing your own migration solution with C# or using third party tools. In this session Randy will talk about defining a SharePoint Online strategy and methods for migrating data to SharePoint Online.

1. Migrating to Office 365 Randy Williams Enterprise Trainer & Evangelist randy.williams@avepoint.com Twitter: @tweetraw © 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.

2. Randy Williams Enterprise Trainer & Evangelist – AvePoint 20+ years in IT developer, consultant, trainer, author Three-time SharePoint MVP Speaker at many global conferences randy.williams@avepoint.com http://linkd.in/plEEb1 @tweetraw

3. Agenda Migration Solutions Office 365 Overview 1 2 3 4 Migration Planning Q & A

4. Agenda Office 365 Overview 1

5. What’s in the Box? http://office365.microsoft.com/

6. Microsoft’s Promise 99.9% uptime Certified Multiple datacenters Geo-redundant Shorter release cycles http://www.microsoft.com/en-us/cloud/cloudpowersolutions/productivity.aspx?fbid=yk9RvqroDcr

7. Data Centers

8. Managed Service Scalability Low up-front costs—pay as you grow Binding SLAs Disaster Recovery High Availability Globalization Eco-friendly Potential Benefits

9. Potential Issues Security Data Sovereignty Reliability Offline story Compliance Dev/Test/Staging farm? Storage costs Recovery SLAs No server access Locked in

10. Missing Features Today Business Connectivity Services FAST Search Performance Point Services Project Server Power Pivot Secure Store Service Limited device support Full Trust Solutions

11. Current USD Costs (per user/per month) Professional and Small Business(less than 50 users) P$6 – Exchange, Lync, SharePoint, Office Web Apps Enterprise E1 $10 – Exchange, Lync, SharePoint E2 $16 – E1 + Office Web Apps E3$24 – E2 + Office Pro Plus, Excel/InfoPath/Visio/Access Services E4 $27 – E3 + voice capabilities Storage costs might be additional http://www.microsoft.com/en-us/office365/enterprise/subscription-plans.aspx

12. Office 365 Storage * Excludes My Sites

14. Software: Windows Server 2008 R2, SQL Server 2008 R2, SharePoint Server 2010, Office 2010 Professional…Cost?

15. Agenda 2 Migration Planning

16. Deploying SharePoint Online is still a SharePoint deployment. Many of the project tasks such as planning, governance and training do not change. Important Reminder

17. Common Office 365 Scenarios All-in (usually for new deployments) Hybrid Collaboration, My Sites are common services to move Redesigning information architecture On-premise accounts can be used to authenticate to O365 Provides single sign on Must deploy ADFS 2.0 into your on-premises network Establish relationship between on-premises forest and O365 See http://bit.ly/mODcnL for more details

18. Do I need an on-premises staging farm?

19. Why have an on-premises staging farm? Performance Convenience Cleanup/re-architect locally/roll back & re-apply Consolidation Reduce overall risk Increased flexibility with migration tools Can evolve into testing/training environment MSFT recommended approach

20. Questions to Ask How much content needs to be migrated? Can non-SharePoint related assets be properly mapped into SharePoint? How many customizations are currently in use? Can it be done iteratively? How much downtime can be tolerated during cutover? Is loss of metadata and securities acceptable?

21. Migration Considerations Granularity Do you need flexibility on what gets migrated? Fidelity Can you preserve the data context (e.g. metadata)? Mapping Can you represent external data properly? Co-existence Are both systems up? Do you need to do incremental migrations?

22. Migrating from BPOS Migration will happen automatically Scheduled from Sept 2011 – Sept 2012 Microsoft will contact you 60-90 days before migration is done Expect downtime during the migration May take a few hours to two or more days http://www.microsoft.com/online/transition-center.aspx

23. Agenda Migration Solutions 3

24. Migration Options Manual Usually just for files Do you delegate out to users? Use SharePoint Designer Write custom code to call into the SharePoint API Use third party tools

25. APIs available Client Object Model Three flavours - .NET, Silverlight, JavaScript Various limitations Many operations are available within site collection Web, List, Library, Folder, File, Item, etc. OData (REST-ful) web services Creating, updating, deleting items Add reference to /_vti_bin/listdata.svc Classic SOAP-based web services (.asmx) Careful: authentication is tricky!

26. Calling into Office 365 with Client Object Model

27. O365 Migration Tools Microsoft has not provided any ISV and community opportunity/responsibility AvePoint - DocAve Migrator Metalogix - Migration Manager for SharePoint MetaVis- Migrator for SharePoint PCVITA – Express Migrator for SharePoint

28. DocAve for SharePoint Online Designed with staging in mind Supports Standard or Dedicated Office 365 Graphical mapping Content selection filters Based on the DocAve platform Staging

29. O365 Migration

30. Recommendations Treat a migration as a real project Costs, features, schedule Clean up source environment as much as possible Delete/archive out unused content Migration should be iterative process “Big-bang” migrations are much more complex Consider third party solutions Testing is essential Expect to do troubleshooting and problem solving Best to do this in an on-premises environment

31. To learn more about Office 365 Webcast recorded on 2 Aug 2011 Download from http://www.avepoint.com/sharepointuncensored

32. Agenda 4 Q & A

33. Q&A Randy Williams randy.williams@avepoint.com

34. © 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.