Microsoft

Question

SharePoint migration to cloud but have unsanctioned online content

By sullvasq ·
Problem: taking over project migrating from 2013 SharePoint on premise to SharePoint online which was started by IT crew no longer with company. Looks like they started some testing but left unattended and departments started building their own sites without supervision or “authorization” of IT. Now those sites “shouldn’t” be “taken down” in process of properly setting up sanctioned SharePoint migrated from real internal SharePoint 2013 server. I have some SharePoint experience and received some training. Already ran SharePoint Migration tool and there are issues but having hard time really figuring out specifics of issue or how to actually fix them. Obviously better to have consultants come in to do, but also obviously organization doesn’t want to spend money - also a non-profit. What to do to really get started?
Thread display: Collapse - | Expand +

All Answers

Collapse -

5 Key Steps for Migrating SharePoint to the Cloud

by rickbale649 In reply to SharePoint migration to c ...

1. Identify what configuration works best for your business
There are several options for running SharePoint both on-premises or in the cloud. As you weigh cloud options, consider which environment best serves your user’s needs. Do you want to move everything to the cloud, or would a hybrid cloud scenario, where only certain workloads or applications (such as email or archive storage) are migrated serve your users better? Depending on the functionality you require and what your organization’s information architecture looks like, evaluating all the options will help shape the scope of the migration and ensure the best solution for your organization.

2. Establish a realistic timeline
Be patient -- your move to the cloud will take longer than you think. I’m not saying that you should estimate how long you think it will take then double it, but the reality is that successful migrations take time. SharePoint is complex and Murphy’s Law always applies. Gartner reported that 80 percent of organizations expect their SharePoint migrations to be quick, easy and trouble-free. In my experience, 20 percent of these organizations will have a stalled project and may even be unable to bring their new SharePoint environment live. This worst case scenario is entirely preventable, but it’s important to be patient and build in extra time up front.

3. Identify what you need to migrate and what you should leave behind
Don’t waste your time and money migrating content that is no longer useful to your business. It’s important to work with content owners and business users to identify relevant content and understand how it is being used and will be used in the future.

4. Test your migration
As with all IT migrations, put a plan in place for testing your SharePoint cloud migration. Try to use content and a SharePoint structure that is as close as possible to your final planned environment. Once you’ve carried out one test, try another and then

5. Verify the results with the business
Once you are satisfied with your testing, share the results with key business users and stakeholders. These are the people that ultimately need to be happy with the move. Make sure that the content has been migrated in line with their expectations and that any new information architecture scoped out on the whiteboard during the planning phase makes sense in the real world.

Related Discussions

Related Forums