Forum Discussion
Beginners guide to migrating from on prem fileserver to sharepoint online
We (a small company) are migrating to SharePoint Online too. I've been spending many hours to trying to figure this out. SharePoint Online is almost completely new to our users and I want to keep this as simple as possible but at the same time leave room for growth, changes and future adoption of extra features such as Teams. But at the beginning, SharePoint would be a file and document library that is mostly synced to the local file explorer because that's familiar to users.
1.
I considered creating one Team Site (and the Team) for each unit and save all files in Teams-based SharePoint sites. Then, the team could start using Teams or they could not - their choice. Is this a good idea?
But, even that could be too complicated. So, an even simpler (or not) migration:
2.
Store all company files on one site, probably the root site; Put each unit's documents in a separate document library. Assign unique permission for each library (using security groups or Office 365 groups). I would also create the Office 365 group and Team for each unit, to have the email list, calendar, planner etc...and if they wanted to test Teams. What do you think about this?
1.
I considered creating one Team Site (and the Team) for each unit and save all files in Teams-based SharePoint sites. Then, the team could start using Teams or they could not - their choice. Is this a good idea? But, even that could be too complicated. So, an even simpler (or not) migration:
Spot on - I have deployed SharePoint Team sites to a number of clients recently without Teams for the simple reason of not overloading them with change. If more technically minded/savy business teams want to use Teams then just "Teamify" the SharePoint site collection.
2.
Store all company files on one site, probably the root site; Put each unit's documents in a separate document library. Assign unique permission for each library (using security groups or Office 365 groups). I would also create the Office 365 group and Team for each unit, to have the email list, calendar, planner etc...and if they wanted to test Teams. What do you think about this?
I wouldn't recommend this, for example having the possibility that users could accidentally see HR or finance data would give me sleepless nights if the permissions weren't setup correctly. Also would be a proper pain when you came to do point 1 eventually.
Thanks for the quick reply, appreciate it.
...
Spot on - I have deployed SharePoint Team sites to a number of clients recently without Teams for the simple reason of not overloading them with change. If more technically minded/savy business teams want to use Teams then just "Teamify" the SharePoint site collection.
The more I research about the subject, the more convinced I'm becoming this is the way to go. Although my boss will probably object because he'd like to see all the libraries in one place (central navigation). This can of course be achieved but I don't think there's a way to easily list and link all sites you have access to?