You are on page 1of 97

10

bniaulin

FAILED

sharepoint migration

REASONS your

SharePoint 2013 has arrived

So You took off with SharePoint 2013

But ignored

KEY CONCEPTS

OVERLOADED

Now you feel

OVERLOADED
Like it might all come

Now you feel

CRASHING DOWN

SO WHY DID YOUR

SHAREPOINT MIGRATION
FAIL?

1 YOU DONT KNOW SharePoint

bniaulin

Yes, you.

Yes, you. But its ok, thats mostly everyone

SharePoint is easy to use. A few clicks,


and you get:

Sites, Lists, Libraries, Pages...

And now you Feel like the

coolest
person in town

But SharePoint requires

time knowledge patience and experience

Its built on
Windows Server IIS .NET SQL DNS Javascript AD
and so much more...

Its built on
Windows Server IIS .NET SQL DNS Javascript AD
and so much more...

Thats a lot of moving parts to consider when migrating

and if youre not an expert in all of these elds....

then ASSEMBLE an EPIC team of them

bniaulin

YOU THOUGHT

TRAINING
WAS OPTIONAL

SH OC KIN G!

SH

OC

KIN G!

Training is often left at the end of the project or even ignored

BUT WHY?

Some see it as too big an expen$e

Some see it as too big an expen$e


cost of training + cost of lost productivity

TRAINING HELPS!

TRAINING HELPS!
employee satisfaction

TRAINING HELPS!
employee satisfaction tackle more tasks

TRAINING HELPS!
employee satisfaction tackle more tasks motivation to use SharePoint

TRAINING HELPS!
employee satisfaction tackle more tasks motivation to use SharePoint increased adoption

TRAINING HELPS!
employee satisfaction tackle more tasks motivation to use SharePoint increased adoption and much more...

SO DONT IGNORE TRAINING IN YOUR PLANNING

Let the users play with SharePoint

and ensure your SharePoint migrations success

3
LACK OF

bniaulin

COMMUNICATION

By bringing change

By bringing change

you are already the

bad guy

trying to change their routine.

Without announcements

or proper communication

its going to

HIT HARD

SharePoint Migration experience

increasing your chances for a bad

Take the time to show o !


New Features Dates & Milestones Organize launch events How itll facilitate tasks Reasons for the change

COMMUNICATE and see yourself become the hero coming to the rescue

bniaulin

YOU THOUGHT DATABASE-ATTACH WOULD DO EVERYTHING

There can be only 1


...upgrade scenario
according to Microsoft, only Database-Attach is supported
this is only from SP2010

and you thought this would work like magic

bringing along all the old junk.


thats everything that was in the Databases

did you forget you had custom coded solutions?

Though it might work for some...

Take the time to pick and choose what to migrate to SharePoint 2013

Enough has changed in SharePoint 2013


That youll want to build a new architecture

bniaulin

IGNORED BUILDING A NEW ARCHITECTURE

2013

SP2013 arrived with cool new features

Search
WCM SkyDrive Pro

Social

WebParts

Design Manager

Doing a Database-Attach upgrade

and bringing the same old architecture over is like...

getting a COOL new o ce

And furnishing it with old computers

things like the Content Search WebPart will completely redene how you see a SharePoint Architecture

What used to be a brick wall you couldnt workaround


(boundaries between sites, site collections, etc.)

Can now easily be done using

SEARCH

bniaulin

YOU DIDNT INVENTORY YOUR SITES AND TEST THEM FOR UPGRADE

Many factors will inuence whether your site will still work after migration

If you dont know what you have in your environment

Then you wont know what could potentially cause a problem after an upgrade

Take the time to inventory your sites

and know what you have

To run the available health checks and tests before upgrading

bniaulin

NO PLANNING NO GOVERNANCE NO INFORMATION ARCHITECTURE

Governance
Should not strike fear when said out loud Should not be a burden to carry during the project

A Governance plan helps establish rules. With so many users and sites, it helps maintain everything together.

but keep it simple.

or it will turn into a document NO ONE will read

Information Architecture
is the logical way of organizing your SharePoint architecture

it will help you dene things like Metadata Columns Sites Navigation Hierarchy Content on Pages

and everything else that will be used in your SharePoint

Make sure you have a plan


SharePoint Migration is no easy task

set goals and milestones to measure the success of your migration

This can be simple Look at what you want to

Remove Migrate Rebuild

And this will be even easier to do if you did an inventory of your sites before

bniaulin

NO MEASURABLE GOALS WERE SET

Without a clear set of goals

You wont know if the migration is a success or if its nished. Youll keep going on and on

Dene clear goals Objectives that make it a successful migration for you

Measuring can be as simple as knowing how many sites have to be: Removed Migrated or Rebuilt
14%

Remove Migrate Rebuild

47%

39%

or using SharePoint Analytics to see if users are using the new features

bniaulin

BRANDING SEEMED IRRELEVANT TO YOU

DID THESE IMAGES EVOKE AN EMOTION?

WHICH INTRANET WOULD YOU HAVE RATHER USED?

But it has all the same functionality, why not?

Branding helps increase user adoption and if done correctly, might even help with User Experience and Findability

10

bniaulin

IGNORING THIRD PARTY TOOLS

Tools cost money

But so does your time

THESE TOOLS MIGHT END UP SAVING YOU TIME AND MONEY

SOME OF THEM ARE EVEN PRETTY COST EFFECTIVE and EASY TO USE

USEFUL LINKS
Supported Migration Scenarios Introduction to SharePoint 2013

bniaulin

What might not work after you upgrade Tools and Techniques to create a simple Governance Plan Planning a SharePoint Migration Whats new with SharePoint Analytics Using the Content Search Web Part to Roll Up Sites

NO MORE FAILED SHAREPOINT MIGRATIONS

Thank You!

Please Share to help others with their SharePoint Migration

Benjamin Niaulin twitter.com/bniaulin bniaulin.wordpress.com en.share-gate.com/blog

You might also like