Skip to content
Free IT audit

Microsoft 365 & Cloud

SharePoint & Microsoft Teams

We implement SharePoint and Microsoft Teams with a file and permission structure that survives company growth. We migrate from the local file server keeping the working logic intact, define who sees what at group level, and hand over guidance so people do not fall back to emailing attachments.

Request a site surveyAll services in this area

Who it is for

  • Businesses with files on a local server and users outside the office
  • Teams exchanging files by email and losing track of versions
  • Companies with departments needing distinct permissions
  • Organisations already paying for Microsoft 365 and not using it

When we are NOT the right choice

  • If migration is wanted with no restructuring at all
  • If an application requires files on a local network path
  • If no owners can be nominated per workspace

PROCESS

The process

Indicative times from signature of the proposal, subject to hardware availability. Every project is shaped to the size and the needs of the client.

  1. 01File and group inventory

    We record where files live today, who uses them, and what permissions actually apply in practice.Time: 2-5 working daysDeliverable: Data and permission map

  2. 02Structure design

    We design spaces per department and project, with permissions at group level. A structure copied from the old server rarely survives.Time: Alongside the studyDeliverable: Workspace and permission structure

  3. 03Data migration

    We migrate files into the new structure and verify permissions and access per group before anyone starts using it.Time: Depending on volumeDeliverable: Files in the new structure with history preserved

  4. 04Teams configuration

    We build teams and channels pointing at the same file spaces, so two parallel systems do not emerge.Time: During implementationDeliverable: Teams and channels wired to the same file spaces

  5. 05Guidance and handover

    We hand over short instructions for the practical points: where to save, how to share, what no longer goes by email.Time: On completionDeliverable: Usage instructions per role

What is includedWhat is not included
Inventory of files, groups and permissionsMicrosoft licence costs
Workspace structure designCustom Power Platform development
Migration from a local file server or another serviceContent cleanup and decisions on what to delete
Group level permission configurationArchiving and legal compliance services
Teams wired to the file spaces
Usage instructions per role

Technology and equipment

  • SharePoint
  • Microsoft Teams
  • OneDrive
  • Microsoft 365
  • Microsoft Entra ID

From practice

The most common SharePoint implementation is a copy of the old file server placed in the cloud, with the same deep folders and the same per-folder permissions. It works for a few months, until someone needs access to a subfolder four levels down.

A structure that lasts is flatter and organised around teams and projects rather than around the org chart. And permissions go to groups, never to individuals, because individuals change roles.

Prerequisites

  • Access to existing files and their permissions
  • Nominated owners per department or workspace
  • A decision on what migrates and what is archived
  • Active Microsoft 365 licences for the users

Cost

Quoted as a project based on user count, data volume and permission complexity. The structure study is a separate line in the quotation, because that is what determines whether the implementation lasts.

We do not publish a price list. Every proposal follows a site survey and separates hardware from labour.

What moves the cost

  • Volume of data to migrate
  • Number of departments and permission levels
  • Which system the migration starts from
  • Whether parallel operation is needed during transition

Frequently asked questions

What is the difference between SharePoint and OneDrive?

OneDrive is each user personal space, SharePoint is the shared space of a team. The most common mistake is company files living in somebody OneDrive, and access being lost when that person leaves.

Can we keep our existing folder structure?

Partly. A structure built for a file server usually has deep paths and per-folder permissions that do not migrate cleanly. We recommend reorganising into spaces per department and project.

What about applications that need a local path?

They are identified in the inventory and handled separately. In several cases the local file server stays in place for those, while everything else moves.

Will training be required?

Minimal, but necessary. Short instructions per role covering three things are enough: where to save, how to grant access, and what no longer goes out as an attachment.

Related services

Also connects with

NEXT STEP

Get your files organised properly

We start with a data and permission map, then propose a structure that holds as the company grows.

Request a site survey+30 210 598 9588

GET IN TOUCH

Tell us what you need

Four fields. An engineer replies, not a sales desk.

Fields marked * are required.

By sending this form you accept the processing of your details under our Privacy Policy.