Infrastructure planning
Server, cloud services or hybrid: which approach fits your business?
Compare where systems run, what they depend on and who remains responsible before replacing a server or moving a workload.
Start with the workload
Cloud is not automatically better, and a server is not automatically outdated
The useful question is where each application, file store, identity service or business process should run for this organisation.
A small business may use Microsoft 365 or Google Workspace for email and collaboration, keep a specialist application on a local server, and store other information in a managed cloud service. That is already a hybrid environment, even if nobody originally called it one.
The decision should consider application support, data, connectivity, staff locations, security, recovery, performance, ownership, lifecycle cost and supplier responsibilities. JM Restart can help document those requirements before products or migration dates are chosen.
Questions worth answering first
- Which applications are business-critical?
- Where are staff and devices located?
- What happens during an internet outage?
- Who supports each application?
- How much interruption or data loss is acceptable?
- Which integrations and devices must continue working?
- What are the full three-to-five-year costs?
Three broad models
Different locations move responsibilities rather than removing them
On-premises server
Hardware is kept at a business-controlled location. It may suit specialist local applications, large local data sets or requirements that cannot depend entirely on an internet connection.
The organisation remains responsible for hardware lifecycle, power, cooling, physical protection, patching, monitoring, backup and recovery unless those duties are contracted to providers.
Cloud service
A provider operates some or all of the underlying platform. Software as a Service products can remove the need to run the application’s servers, while cloud-hosted virtual machines still leave more operating responsibility with the customer.
Accounts, permissions, data, devices, configuration, backup choices and supplier management still require attention.
Hybrid environment
Some services remain local while others use cloud platforms. This can support a staged migration or a lasting design where different workloads have different needs.
Hybrid can be practical, but identity, connectivity, monitoring, backup and support boundaries need to be documented across both sides.
Shared responsibility
Moving to the cloud does not outsource every decision
The provider may operate physical datacentres, hardware and parts of the platform. The customer still owns important responsibilities.
Those continuing responsibilities commonly include business data, identities, users, access decisions, endpoint devices and many configuration choices. The exact boundary changes between Infrastructure as a Service, Platform as a Service and Software as a Service.
Availability also depends on the whole route. A cloud service can be operational while a local internet circuit, identity configuration, device or integration prevents staff from working. Backup and recovery still need their own design.
Responsibilities to record
- Account creation, review and removal
- Multi-factor authentication and access rules
- Device protection and support
- Application configuration and integrations
- Data retention, backup and recovery
- Monitoring, alerts and incident response
- Renewals, licences and supplier escalation
Decision criteria
Compare the full operating model
Applications
Check vendor support, latency, integrations, peripherals, licensing and whether the application can genuinely move.
Connectivity
Assess bandwidth, reliability, backup connectivity and what staff can still do during an outage.
Security and data
Record identities, permissions, devices, data locations, legal requirements, retention and recovery responsibilities.
Cost and lifecycle
Compare purchase, subscriptions, migration, support, power, connectivity, backup, growth, renewal and eventual exit costs.
Common questions
Server and cloud planning, explained
Does Microsoft 365 mean we no longer need a server?
Not automatically. Microsoft 365 can replace or improve many email, collaboration, identity and device-management functions, but specialist applications, local files, printers, integrations or performance requirements may still need another platform.
Is cloud always cheaper?
No. Cloud services can reduce capital purchases and transfer some operating responsibility, but subscriptions, migration, data transfer, connectivity, support and long-term growth must be included. A fair comparison uses the same period, scope and recovery expectations.
Can we move gradually?
Often, yes. A hybrid phase can reduce disruption and allow each workload to be assessed separately. It also creates additional dependencies, so responsibilities and the intended end state should be documented.
Will cloud services work without internet access?
Some applications offer limited offline features, but most cloud services require reliable connectivity for normal use. Connectivity resilience and temporary working arrangements should form part of the design.
Can JM Restart review an ageing server?
Yes. We can help document the server’s workloads, dependencies, backup, support status and replacement options, then compare suitable on-premises, hosted or hybrid routes. Application vendors may need to confirm their own requirements.
Planning a replacement, migration or hybrid environment?
We can help map the current systems, identify dependencies, compare practical options and turn the decision into a staged project plan.
