Forum Discussion
Beginners guide to migrating from on prem fileserver to sharepoint online
Hi all, so, due to an ailing and failing on premise fileserver with no spare storage and because we already have Office 365 E3 licences i want to start to migrate our data into sharepoint online. I...
I'm borrowing your thread because I hope I'm helping you at the same time too.
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?
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?
rupie100 borrow away my friend. It sounds like your situation is very similar to mine, so the more info we can share and the more advice we can get, the more progress we can make. 🙂
- Right, so having been pulled away onto other projects i'm now back onto this.........
So, i've got quite a few teams going on, and i can see in the SP admin center that sites have been created from these team, but i've been advised its best to do it the other way round, SP then Teams.
So, i want to perform a test on the IT share on our Z: drive. Only i have access so its no biggie if i break it.
I'll create a Team site (not a communication site), and start to copy over the data i want.
Do i create a subsite for 3rd party IT providers? Is that a good idea?- How did it go? I have a small office 3 employees currently but at times up to 5 or 6. We have sales, customer folders, support, hr, marketing shares on or file server. I’m wanting to do away with the on premises file server and go this route. What can you share from your experience?
