How much content?How long? How much downtime can you tolerate?How much customization?“Big Bang” or scaled/phased approach?Loss of metadata / security acceptable?Who can help?Minimum requirements?Mappings available?Can we restructure?Maintain coexistence?
SharePoint SharePoint 2010 Farm 2013 Farm (READ- ONLY) Database servers: SQL Server 2008 R2 or SQL Server 2012 Web and Application servers: Install all prerequisites Install SharePoint 2013 Products.
Original SQL Server New SQL Server Most actions take place in SQL Server Management Studio Set to read-write (optional) Set to read-only (optional) Database servers Back up Content databases Service application databases
1 2 3 4 Create SharePoint 2013 Production farm Copy databases to new farm Upgrade Databases Upgrade site collections Server Farm Administrators
1. Backup everything2. Upgrade service first3. Upgrade content databases4. Upgrade site collections at your leisure5. Re-index existing content
Business continuity – minimal interruption toend-user productivityContent restructuring and taggingcapabilitiesFilter outdated, irrelevant contentLower total cost of ownership, Increase returnon existing assetsUpgrade challenges and limitations…
Discovery and Test-Run ToolsMigrate to SharePoint 2010, SharePoint 2013, SharePointOnline, Legacy PlatformsLive or scheduled, online or offlineComprehensive metadata, property, and securitymappings + Filter + RestructureMigrate OOTB, SPD, and Nintex workflowsCentrally report and audit on ALL migration activity andhistory
OverviewBest For: Pros: Cons:• Any size environment, from single • Direct migration from 2007 to 2013 • Costs associated with purchasing of server farms to large, distributed • Pre-scan to determine customisations additional software farms • Reorganise content structures during • Learning/training of new software• Migration from non-SharePoint migration Sources • Granular migration• Restructuring content • Retains metadata, versions, permissions• Preservation of any metadata or • Virtually no downtime security • Applicable to non-SharePoint repositories • Options for 24 x 7 Support?
Demo: Migrating to SharePoint 2013 with AvePoint