Migrate to share point 2013 with avepoint 2.14.13

Preview:

Citation preview

Migrating to SharePoint 2013 with AvePoint Mary Leigh Mackie Shyam Oza

VP, Product Marketing Product Manager

mlmackie@AvePoint.com | @mlmackie Shyam.Oza@AvePoint.com | @ShyamOza

Technologies

Support Community Services

Solutions Partners

Goals for SP2013 Upgrades What Are Your Options? Site Collection Upgrades

Farm Upgrade Overview

Utilizing Third Party Solutions Demo: AvePoint’s Migration Solutions

Wrap Up Q&A Additional Resources

Business Intelligence

eDiscovery

Identity Management

Mobile Support

Social Computing

Records Management and Compliance

Web Content Management

Upgrade Migrate

Manual Automated

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?

Out of the Box

Safer upgrades

Reduced Upgrade Time

Power to the people

Eliminate big bang upgrades

Move forward at a manageable pace

Rules can detect and in some cases repair issues

Rules can exist for use in 14 and/or 15 modes

Can be run without doing upgrade

Throttle limit the number of parallel upgrades

Upgrade requests are always queued Status of all queued upgrades are tracked within the queue

Farm Upgrade (On-Prem)

SharePoint 2010 Farm

(READ- ONLY)

SharePoint 2013 Farm

Database servers:

SQL Server 2008 R2 or SQL Server 2012

Web and Application servers:

Install all prerequisites Install SharePoint 2013 Products.

Original SQL Server

Set to read

-on

ly (op

tion

al)

Back u

p

New SQL Server

Set to read

-write (o

ptio

nal)

Most actions take place in SQL Server Management Studio

Database servers

Content databases

Service application databases

Copy databases to new farm

2

Upgrade Databases

3

Server Farm Administrators

4

Create SharePoint 2013 Production farm

1

Upgrade site collections

4

1. Backup everything 2. Upgrade service first

3. Upgrade content databases

4. Upgrade site collections at your leisure 5. Re-index existing content

What About to SharePoint Online?

Office 365 – Dedicated Microsoft no longer supports content migration for Office 365-D customers

Remaining options: Manual migrations, custom-coding, Third-party tools

Office 365 – Standard Options: Manual migrations, custom-coding, Third-party tools

Third Party Solutions

Business continuity – minimal interruption to end-user productivity

Content restructuring and tagging capabilities

Filter outdated, irrelevant content

Upgrade challenges and limitations…

Lower total cost of ownership, Increase return on existing assets

Create a Migration Test Environment

Don’t Forget About Governance

Information Architecture Archive End-of-Life

Content

Reduce Risk of Non-compliance

Harden Security Set End-User Expectations

Perform a Content Assessment

© 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.

Comprehensive metadata, property, and security mappings + Filter + Restructure

Discovery and Test-Run Tools

Migrate OOTB, SPD, and Nintex workflows

Live or scheduled, online or offline

Migrate to SharePoint 2010, SharePoint 2013, SharePoint Online, Legacy Platforms

Centrally report and audit on ALL migration activity and history

Overview

Best For: • Any size environment, from single

server farms to large, distributed farms

• Migration from non-SharePoint Sources

• Restructuring content • Preservation of any metadata or

security

Pros: • Direct migration from 2007 to 2013 • Pre-scan to determine customisations • Reorganise content structures during

migration • Granular migration • Retains metadata, versions,

permissions • Virtually no downtime • Applicable to non-SharePoint

repositories • Options for 24 x 7 Support?

Cons: • Costs associated with purchasing of

additional software • Learning/training of new software

Demo: Migrating to SharePoint 2013 with AvePoint

300TB Migration from multiple sources (SP, Livelink) 60TB migrated in one year

8 TB meeting strict 3-4 month timeline

6TB SharePoint migration

45TB Livelink migration

1.8 TB eRoom migration

Fully custom end-user driven migration project

Questions?

Recommended