SharePoint Online for Small Businesses in Berlin: Document Management Without the Complexity

Berlin SMBs are still running Windows file servers in 2026. Some of them are twelve years old, patched inconsistently, and accessible via a VPN that was configured by a technician who left three years ago. The replacement is not complicated, but it requires understanding what SharePoint Online actually is, what it is not, and the specific decisions that separate a working rollout from a permission nightmare six months later.

OneDrive vs SharePoint: The Distinction That Matters

OneDrive is personal storage. SharePoint is shared storage. Both live on the same underlying Microsoft infrastructure, but the access model is completely different.

OneDrive is owned by a single user. If that user leaves the company and their account is deleted, the files go with it unless you have a retention policy. SharePoint sites are owned by the organisation. Files survive account deletions because ownership belongs to the site collection, not the individual.

For anything that more than one person needs to access, SharePoint is the correct tool. For an individual’s working documents, drafts, and personal files, OneDrive is appropriate. The mistake most SMBs make is using Teams channels (which create SharePoint document libraries under the hood) without understanding the SharePoint layer behind them.

Site Architecture for a 10 to 50-Person Company

Start simple. The common mistake is over-architecting at the beginning with dozens of site collections that nobody maintains. For most Berlin SMBs, the following structure covers 90 percent of use cases:

• Intranet site (Communication site) — company news, policies, onboarding documents, org chart. Read-mostly. Maintained by HR or management.
• Department sites (Team sites) — one per department or function. Finance, Operations, Sales, Engineering. Each has its own document library with version history enabled.
• Project sites (Team sites, often via Teams) — created when a project starts, archived when it ends. Connected to a Teams channel for file access during the project lifecycle.

Do not create a SharePoint site for every small initiative. The overhead of maintaining permissions across thirty sites with five members each is significant and never gets done properly.

Permission Model: Where Rollouts Fail

SharePoint permissions are hierarchical. A site has an owner, members, and visitors. Owners have full control. Members can edit. Visitors can read. The problem comes when admins start breaking permission inheritance and granting item-level or folder-level access to individuals. Within six months, nobody knows who can access what, and the IT department spends half their time on access requests.

Enforce these rules from day one:

1. Assign permissions to Microsoft 365 Groups or Entra ID security groups, never to individual users. When someone joins or leaves a team, one group membership change propagates everywhere.
2. Use SharePoint sharing defaults to restrict external sharing to specific domains if you need to share with clients. For most SMBs, external sharing should be disabled or set to “existing guests only.”
3. Enable access request notifications so site owners see requests rather than users attempting to find workarounds.
4. Review permissions quarterly using SharePoint admin center > Active sites > Sharing. This takes twenty minutes and catches drift before it becomes a problem.

Integration with Microsoft Teams

Every Teams channel has a SharePoint document library. When a user uploads a file in Teams, it lands in SharePoint. When they access the Files tab in Teams, they are looking at SharePoint. This integration is the primary reason SMBs end up with unmanaged SharePoint sprawl — Teams channel creation is unrestricted by default, meaning every new channel creates a new document library with its own permission context.

The solution is Teams governance, which is covered in detail in our Teams Governance guide. At minimum, restrict channel creation to owners and enforce an expiry policy on inactive teams so the SharePoint sites attached to them get reviewed rather than accumulating indefinitely.

Migrating from a File Server

The SharePoint Migration Tool (SPMT) is free and handles most on-premises file server migrations. For larger or more complex environments, Migration Manager in the SharePoint admin center provides agent-based migration with better performance and reporting.

Before you migrate a single file, do the following:

1. Audit the existing file server. Identify active directories versus archives. Files that have not been accessed in three years do not belong in SharePoint — they belong in Azure Blob cold storage or they belong deleted.
2. Map folders to SharePoint structure. A flat folder hierarchy with hundreds of subfolders does not translate well to SharePoint. Take the migration as an opportunity to flatten the structure and use metadata and search instead of deep folder trees.
3. Check file name compatibility. SharePoint does not allow certain characters in file names (asterisk, colon, forward slash, backslash, angle brackets, pipe, question mark). SPMT will flag these, but fixing them in bulk before migration is faster than editing them afterwards.
4. Communicate the cutover. Run read-only mode on the file server for two weeks after migration. Users who try to save to the old location will notice immediately and can be redirected to SharePoint.

GDPR and Retention Labels

For Berlin SMBs, GDPR compliance requires knowing where personal data lives and being able to delete it on request. SharePoint provides two mechanisms that matter here:

• Sensitivity labels (from Microsoft Purview) classify documents containing personal data and can enforce encryption or restrict sharing automatically.
• Retention labels ensure documents are kept for the legally required period and then either deleted automatically or flagged for review. For German commercial correspondence, the retention requirement is typically ten years (HGB §257). Automated retention prevents both premature deletion and indefinite accumulation.

Both features are available in Microsoft 365 Business Premium. Configuring them requires access to the Microsoft Purview compliance portal and about half a day of planning before deployment.

Licensing Reality Check

SharePoint Online is included in all Microsoft 365 Business plans (Basic, Standard, Premium). There is no additional licence cost for the core functionality. The differences that matter for SMBs:

• Storage: Each tenant starts with 1 TB plus 10 GB per licenced user. For a 20-person company, that is 1.2 TB, which is sufficient for most SMBs.
• Sensitivity labels and advanced compliance: Require Microsoft 365 Business Premium or a Purview add-on. If GDPR obligations are significant, Business Premium is the correct licence level.
• Syntex / AI features: Separate add-on licences. Not required for core document management.

What IT Experts Berlin Implements

Our standard SharePoint deployment for Berlin SMBs includes site architecture design, permission model configuration using Entra ID groups, Teams governance integration, file server migration via SPMT or Migration Manager, and retention label deployment for GDPR-relevant document classes. Setup typically takes three to five business days depending on the volume of data being migrated. Contact us for a scoping assessment.