
Server on site, in the cloud or hybrid: how small companies decide
How small companies choose between an on-site server, the cloud or hybrid: six questions per application, when each fits and who patches and backs up.
Cloud and Microsoft 365
Plan a clear move to Microsoft 365 and the cloud, or tidy what you already have, so email, files and collaboration work consistently across your offices.

Microsoft 365 is the main workspace for many small and midsize companies: email, calendars, documents, chat and video meetings all live in the same place. That convenience also means that a poorly organised setup quickly becomes a problem, with duplicated licences, files scattered across personal drives and permissions nobody remembers granting. Our Microsoft 365 and cloud service helps you plan a clean move or tidy an existing environment, for teams in Europe, with support in English and Spanish.
Buying Microsoft 365 is straightforward. Making it work for several offices is not. Decisions made in the first weeks, such as how users are named, how groups and shared mailboxes are structured, where documents are stored and who may share them externally, tend to stay in place for a long time because changing them later disrupts real work.
Companies operating in more than one country also deal with different languages, time zones, local suppliers and, in some cases, different expectations about where data is held. We do not provide legal advice, but we can document how your environment is configured so that your legal adviser or customers can understand it. The goal is a setup that is simple to explain, simple to administer and consistent from one office to the next.
We start by looking at what you already use: existing subscriptions, mailboxes, file servers, third-party tools and any other cloud services. We then compare it with how your teams actually work, so licences match roles instead of being bought in one size for everyone. This often reveals unused subscriptions and overlapping tools that can be retired. To compare the Business Basic, Standard and Premium plans, see our guide to Microsoft 365 Business plans.
A well-organised tenant begins with identity. We help define naming conventions, user and group structure, administrator roles, and sign-in rules including multi-factor authentication. Where the business already has an on-premises directory, we explain the options for connecting it. These choices also support the security work described under cybersecurity. Our Microsoft 365 security baseline checklist lists the basic settings worth reviewing.
We plan the move from existing email, file servers or other collaboration platforms into Exchange Online, SharePoint, OneDrive and Teams. Planning covers what to migrate and what to archive, the order in which teams move, how to keep email flowing during the transition, and how to communicate changes so users are not surprised. Cut-over dates are agreed with you around your calendar and peaks of activity. If you are moving from Google Workspace, our migration guide covers the plan, cutover and post-move checks.
We help configure laptops, phones and tablets so they sign in with company accounts, receive updates and follow the policies you have agreed. Onboarding and offboarding steps are written down so that new colleagues receive the right access and leavers lose it promptly.
Collaboration works best with clear rules: which team owns which library, how guests are invited, how long files are retained and what may be shared outside the company. We help you set sensible defaults and document them in plain language. We also discuss backup of cloud data, because a cloud provider’s availability is not the same as a recoverable copy of your information.
A cloud provider’s availability is not the same as a recoverable copy of your information. We discuss backup of cloud data when setting up sharing, storage and governance for your Microsoft 365 environment.
Microsoft runs the platform, and you remain responsible for your own data. This is usually called the shared responsibility model: the service is built to stay available, while deciding who can delete information, how long it is kept and how it is recovered after a mistake or an attack is up to the customer. Check Microsoft’s current documentation for how this applies to your plan.
Built-in features such as recycle bins, version history and retention settings help with accidental deletion, but retention is not backup. Those windows are limited, they depend on your plan and configuration, and they can change, so check the current Microsoft documentation instead of assuming a period. A malicious deletion, an error synchronised to every device or a compromised account can also reach those copies.
When you talk to any provider about backup of Microsoft 365 data, it is worth asking:
We discuss these points as part of setup, and scope is agreed per organisation. For the wider approach to copies, recovery targets and restore tests, read our backup and recovery guide. Many of the account settings that protect your data are listed in our Microsoft 365 security baseline checklist.
Before anyone proposes a design, we read what already exists. Four pieces of work come first, and each narrows the questions left for the next.
We list subscriptions, mailboxes, file servers and third-party tools, and set them against what each role actually uses. It comes first because a licence is paid for whether or not anyone opens the application. Typical findings are accounts of people who have left, one person holding two overlapping licences, and separate tools bought for something an existing plan may already cover. Check the current Microsoft documentation for what each plan includes before drawing conclusions.
If a tenant exists, we review its users, groups, administrator roles and access rules before proposing changes. Useful questions: who holds administrator roles and still needs them, which external guests were never removed, which groups nobody can explain. A typical pitfall is a tenant created by one colleague or a former supplier, with nobody sure who owns it. If the current arrangement cannot be explained in plain language, it is usually easier to define the target structure and move towards it than to tidy in place.
We map the mailboxes, shared folders and source platforms that hold your data, which is what lets us decide what to migrate and what to archive. Moving data is the straightforward part; the decision that saves effort is what not to move, such as shared folders with no owner or mailboxes of leavers kept just in case. Whether information must be kept for legal or contractual reasons is a question for your legal adviser, and we note the answer before deciding what to archive.
We talk to each team about how it actually collaborates, so that licences and the structure of sites and groups follow real work. Illustrative example, not a client: a team that says it only uses email may in practice run its week from a shared mailbox and a spreadsheet on a file server, and the new structure has to start from that, not from job titles. To decide what stays on a local server and what moves, see our on-site, cloud or hybrid server guide.
The migration plan turns those readings into a sequence and answers four questions that would otherwise surface in the middle of the move. See a sample migration plan outline (illustrative example).
Material still needed for daily work moves. Material needed only for reference is archived where it can be found. Material with no owner and no evident purpose is raised with the people who may know before anything is dropped.
The order follows dependencies and your calendar, not seniority: teams that share a mailbox or a library usually move together, and a team with a deadline or a seasonal peak should not move just before it.
The plan states how mail keeps arriving while some people are on the old system and others on the new. Usual pitfalls are forgotten shared mailboxes and aliases, forgotten forwarding rules, and devices, scanners or applications still pointing at the old server. Sender records for the domain are covered in SPF, DKIM and DMARC for your domain.
People need to know what changes for them, on which day, what they have to do themselves and where to ask for help. For wider planning questions, see our guide to planning IT and cloud services.
If you want continuing work after the move, it falls into four areas, agreed per organisation and carried out within our published hours, Monday to Friday, 09:00–18:00 CET/CEST.
Joiners, leavers and licence changes by role. Access follows the role: a new colleague receives what the role needs, and a leaver loses access, which also frees the licence. Our IT onboarding and offboarding checklist lists the steps worth agreeing.
Access policies, updates and device compliance, handled from a central console. The criterion is what a device must meet before it reaches company data, such as current updates and central management.
A periodic review of administrators, external guests and sharing permissions. Permissions only grow unless someone looks: people change roles, projects end and shared links stay open.
We check the scope of the copy, who can delete it and the result of the last restore test; the reasoning is in the Microsoft 365 backup section above.
We do not give legal advice on data residency. Where data may be held, and whether an arrangement satisfies a contract or a regulation, is for your legal adviser. We can describe the configuration: which services are in use, what a plan offers (checked against Microsoft’s current documentation) and how the tenant is set up.
This service is designed for organisations that want their cloud tools to be reliable and understandable without building a large internal IT team. Typical situations are:
Scope, responsibilities and working arrangements are agreed for your organisation before work begins. We do not claim vendor status or special licensing terms; we help you make sound use of the platform and explain each choice in English or Spanish, whichever your team prefers.
For continuing administration and user support, see our managed IT services.
Once the environment is organised, the Automation and AI service can look at automating workflows across Microsoft 365 and your other tools.
To talk through your current setup or a planned move, contact us with a short summary of your users, offices and tools.
We review your current systems, users, locations and priorities, and agree what is in scope.
We propose a structure for identities, groups, storage and sharing, with the options and trade-offs explained.
We prepare the tenant, test the configuration with a small group and plan communications for staff.
We move data and users in the agreed order, supporting your team through the changes.
We document how the environment is set up. If you want continuing administration and user support, it can be agreed as part of managed IT services.

How small companies choose between an on-site server, the cloud or hybrid: six questions per application, when each fits and who patches and backs up.

A disaster recovery plan for small business that fits on one page: critical systems, roles, contact tree, recovery order and how to test it with your team.

How to migrate Google Workspace to Microsoft 365: what to inventory, prepare and check, how a phased move runs and what to verify before closing Google.
Tell us what your team needs today and what you would like to improve.