160 likes | 252 Views
Migrating Sites to 365. Ishai Sagi Extelligent Design www.exd.com.au. About me. SharePoint Expert since 2001 SharePoint MVP since 2007 Author of SharePoint How To books ( www.tinyurl.com/SharePointBook2010 , $20 from Amazon) Solution Architect in Extelligent Design www.exd.com.au
E N D
Migrating Sites to 365 Ishai Sagi Extelligent Design www.exd.com.au
About me • SharePoint Expert since 2001 • SharePoint MVP since 2007 • Author of SharePoint How To books (www.tinyurl.com/SharePointBook2010, $20 from Amazon) • Solution Architect in Extelligent Designwww.exd.com.au • Blogger (www.sharepoint-tips.com) • Twitter (@ishaisagi)
Today’s Agenda • What type of sites can we build in Office 365? • What content will we migrate into the sites? • How to create a public facing site in Office 365 • Demo! • Backup • Demo! • Migration Project Plan • Migration Methods and Tools • Demo!
What Sites Can I Build in O365 • Public Sites • Internal Sites (intranets) • Hybrids (extranets)
Intranets • Used to share information with people in your company • Used to manage projects, collaborate on documents, track issues, events and more • Accessible only by people in the company
Extranets • Used to share information with people outside your organisation, but require them to log in • Used to allow clients to view secure information • Accessible using Windows Live logins
Internets (public sites) • Use to show the world what your company is all about • Used to publish pages to the internet • Accessible by anyone to read, need to login to edit or create pages *not 100% SharePoint!
What Migrates to What? • Network file shares • Existing sites • Intranet • Internet • Documents on desktops • Attachments in Emails(?)
Creating an Internet Site • Go to your O365 Administration centre • Click on the SharePoint administration link • Click on “Site Collections” • Open the “New” dropdown and select “Public Site” • Demo!
But Wait! • Build the site on a “safe” URL first, then, when ready, change the URL to an easy one • Internet sites are not actually SharePoint • Extremely limited for code enhancements • Will get better as new versions are released • Have you thought about backup? • Post migration support?
Backup • Do we need backup? • How can we backup? • What are the backup limitations? • Demo!
Migration Project Plan • Business analysis.Figure out how you want to use the site. Come up with information architecture, making sure that all stake holders are involved and agree with the new system’s functionality. • PrototypeBuild the site (unpublished) and have all the stakeholders use the (empty) site for a while and sign off on the functionality. • BuildRebuild the site and deploy any custom solutions with the new information architecture and test to make sure the environment is stable before migrating content across. • Migration PlanningReview the contents of the old environment, and make a mapping to the new site. This mapping should go down to the level of “Document X should go to folder Y” along with any set of rules you can think of, as well as “Information in column A should go to Column B”. • Migrate • Test and validate.
Migration Methods and Tools • Manual • Copy-Paste • Manual upload • Automated • Powershell scripts • SharePoint client side code • 3rd party tools (by Extelligent Design!) • Demo!
More reading • http://www.exd.com.au/Articles/UpgradingSharePoint.aspx
Q&A • Thanks for listening keep in touch: • E: ishai@exd.com.au • T: @ishaisagi • P: 0488789786 • W: www.exd.com.au • B: www.sharepoint-tips.com • Before we go – RSPCA donation anyone?http://tinyurl.com/6q9qwyz