Joel's SharePoint Architecture Blog

SharePoint Server, SharePoint Online and Office 365 Training, Architecture, Administration and Development

SharePoint Thing a Day – 033 – Migration. The Whole Process.

by

The Whole Process

View this post on Instagram

#spthingaday 033 – Migration. The Whole Process. #SharePoint, #Office365, #Migration.. The playbook for a successful migration to SharePoint Online usually goes like this: 1. Plan communications and support for the business 2. Inventory your content and customisations 3. Prepare to clean up any content and customisations you don't need 4. Select a migration tool – preferably one that supports delta or incremental top-ups 5. Plan the migration including any steps to redevelop and restyle 6. Remember to coordinate your migration plan with the business to minimise impact 7. Perform a test migration with a representative subset of content and customisations 8. Test it works! 9. Perform the full migration 10. Test it works again! But often, step 8 onwards is more like this: 8. Break your migration plan into manageable chunks 9. Establish your to-be SharePoint Online structure 10. Migrate, then test, one chunk of content at a time, making each one live as you go 11. Repeat until complete When all this is done, keep your old SharePoint Server environment around in read only mode until you are happy to finally decommission it. #microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement

A post shared by JFDI Consulting #spthingaday (@jfdiconsulting) on

The playbook for a successful migration to SharePoint Online usually goes like this:

1. Plan communications and support for the business
2. Inventory your content and customisations
3. Prepare to clean up any content and customisations you don’t need
4. Select a migration tool – preferably one that supports delta or incremental top-ups
5. Plan the migration including any steps to redevelop and restyle
6. Remember to coordinate your migration plan with the business to minimise impact
7. Perform a test migration with a representative subset of content and customisations
8. Test it works!
9. Perform the full migration
10. Test it works again!

But often, step 8 onwards is more like this:

8. Break your migration plan into manageable chunks
9. Establish your to-be SharePoint Online structure
10. Migrate, then test, one chunk of content at a time, making each one live as you go
11. Repeat until complete

When all this is done, keep your old SharePoint Server environment around in read only mode until you are happy to finally decommission it.

SharePoint Thing a Day – 032 – Migration. Little Gotchas – 06.

by

Little Gotchas – 06

View this post on Instagram

#spthingaday 032 – Migration. Little Gotchas – 06. #SharePoint, #Office365, #Migration.. Today's lesson: Beware! Customisations everywhere! You must evaluate every piece of customisation in your SharePoint estate to see if it needs to be migrated, and whether it is safe to do so. Identify custom and third-party code: Full Trust DLLs, Farm Solutions, Sandbox Solutions. Almost all of those will have to go, be rewritten or an alternative found. Identify SharePoint Designer customisations: If users have used Advanced Mode to edit a page in SharePoint Designer, this may cause problems moving to SharePoint Online. Audit them all: replace or throw away? Identify custom JavaScript and third-party libraries: Moving from 2013 to SharePoint Online, these scripts may work, but only for "Classic" Pages. For Modern Page support, you must replace or redevelop with SharePoint Framework. Identify Workflows: Review each one before migration, to make sure that any embedded or hard-coded URLs or identifiers can be updated to reflect your new environment. #microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement

A post shared by JFDI Consulting #spthingaday (@jfdiconsulting) on

Today’s lesson: Beware! Customisations everywhere!

You must evaluate every piece of customisation in your SharePoint estate to see if it needs to be migrated, and whether it is safe to do so.

Identify custom and third-party code:

Full Trust DLLs, Farm Solutions, Sandbox Solutions. Almost all of those will have to go, be rewritten or an alternative found.

Identify SharePoint Designer customisations:

If users have used Advanced Mode to edit a page in SharePoint Designer, this may cause problems moving to SharePoint Online. Audit them all: replace or throw away?

Identify custom JavaScript and third-party libraries:

Moving from 2013 to SharePoint Online, these scripts may work, but only for “Classic” Pages. For Modern Page support, you must replace or redevelop with SharePoint Framework.

Identify Workflows:

Review each one before migration, to make sure that any embedded or hard-coded URLs or identifiers can be updated to reflect your new environment.