Business continuity is often treated as a backup problem. It is not.
Backups matter, but a resilient organisation also needs clearly defined recovery objectives, dependable business systems, secure infrastructure, tested procedures and an affordable technology strategy. These elements must work together when a major supplier fails, a cyber incident disrupts operations, a data centre becomes unavailable or a critical application simply stops responding.
For UK SMEs, the challenge is often greater than it first appears. A business may be modernising finance and operations through Microsoft Dynamics 365 Business Central while still relying on an established IBM i Management estate, third-party integrations, office networks, telephony and specialist applications.
That is why continuity should be designed as one IT strategy, led by an experienced consultant acting as a Fractal IT Director: creating a coherent structure from complex, interdependent systems. Traditional Managed IT Services and technical support still have an important role, but they should execute and reinforce the strategy rather than define it.
1. Disaster Recovery starts with business impact
A Disaster Recovery plan should begin with business processes, not products.
A retailer may need stock, payments and fulfilment restored quickly. An accountancy practice may prioritise access to client records, secure communications and financial systems. A healthcare organisation may have strict requirements for availability, confidentiality and documented recovery procedures. In freight and logistics, a short outage may affect transport schedules, customer commitments and regulatory records.
The first step is therefore a business impact analysis. This identifies:
- Which processes are genuinely mission-critical
- Which systems and suppliers those processes depend on
- The financial and operational impact of downtime
- The information that can be recreated, and the information that cannot
- The order in which systems must be recovered
From this, the business can define two practical measures:
- Recovery Time Objective (RTO): how quickly a service must be restored
- Recovery Point Objective (RPO): how much data the organisation can afford to lose
An RTO of four hours and an RPO of fifteen minutes create very different technical and financial requirements from an RTO of two days and an RPO of twenty-four hours. The objective is not to purchase the most sophisticated recovery platform available. It is to match investment to commercial risk.
Microsoft explains that Business Central online includes automatic backups, built-in redundancy, high availability and geographically redundant protection. Production environments benefit from automatic backups retained for 28 days and point-in-time restoration capabilities. However, those platform capabilities do not automatically recover every integration, endpoint, user process or external dependency around the system.
A proper plan must explain who makes the recovery decision, how users are authenticated, how integrations are restarted, how data is validated and how customers and suppliers are informed.
Most importantly, it must be tested.
An untested plan is an assumption. It may satisfy a document request, but it does not demonstrate that the business can recover under pressure. Failover testing, restoration exercises and scenario rehearsals expose practical issues before an incident does. They also produce evidence for governance, insurers, customers and auditors.
The Disaster Recovery service should therefore be treated as an operational capability, not a file stored in a shared drive.
2. Dynamics 365 Jump Start should connect systems and decisions
A Dynamics 365 Jump Start is not a software sales exercise. It is structured implementation and consultancy support for organisations moving towards Microsoft Dynamics 365 Business Central.
The strongest implementations begin by mapping how the business actually operates. Finance, purchasing, stock, sales, service delivery, project work and reporting must be understood before technology decisions are finalised. The aim is to remove unnecessary complexity, clarify ownership and create processes that staff can follow consistently.
For an SME, a focused implementation programme should typically cover:
- Process discovery – documenting finance and operational workflows.
- Data assessment – identifying what should be migrated, cleaned, archived or retired.
- Integration planning – understanding links to banking, payroll, e-commerce, warehouse, CRM and legacy systems.
- Role and control design – ensuring users have appropriate access and approval responsibilities.
- Testing and validation – checking transactions, reports, interfaces and recovery procedures.
- Change management – preparing staff to use the new processes confidently.
- Operational handover – ensuring the organisation knows how the system will be supported and governed.
Business Central online is built on Microsoft Azure and provides a resilient foundation, including automatic backups and high-availability architecture. That is valuable, but availability is not the same as continuity. A system can be online while a business is unable to trade because a connected service, network route, user permission or operational process has failed.
The Dynamics 365 Jump Start should therefore include continuity questions from the outset:
- What happens if an integration is unavailable?
- How are restored transactions reconciled?
- Which reports are essential on the first day of recovery?
- How are temporary manual processes controlled?
- Can staff operate if offices or local networks are unavailable?
- Which extensions and connectors require separate validation?
This is where consultancy creates measurable value. The objective is a Business Central environment that supports the organisation’s operating model, rather than another application layered on top of existing confusion.
3. IBM i Management belongs in the same continuity conversation
Many UK businesses still depend on established IBM i estates for core applications, transaction processing, manufacturing, distribution, retail or financial operations. These systems may be dependable, but dependable does not mean self-managing.
IBM i Management is a specialist consultancy discipline involving availability, patching, performance, backup, security, operational knowledge and long-term modernisation planning.
Power Systems and AS/400 environments must be assessed alongside newer cloud platforms. Their recovery objectives should be documented by business process, not simply by server. For example, the recovery requirement for a nightly batch process may be very different from the requirement for a live order-processing application.
A joined-up review should consider:
- Backup frequency and restoration procedures
- Journalling or replication arrangements
- Hardware and hosting dependencies
- Operator knowledge and succession risk
- Batch scheduling and job queues
- Interfaces with Business Central and other systems
- User access, privileged accounts and patching
- Performance trends and capacity constraints
- A realistic route towards modernisation, replacement or continued operation
The relationship between an IBM i platform and Business Central is particularly important. If data moves between systems, a recovery plan must define how both sides are restored and reconciled. Restoring one platform without considering the other can create duplicate transactions, incomplete orders or unreliable management information.
There is no virtue in modernising for its own sake. A specialist consultant should help the business decide what to retain, what to improve and what to replace, based on risk, value and operational reality.
4. Technology Expense Management funds resilience
Continuity investment is easier to justify when technology spending is understood as a portfolio rather than a collection of invoices.
Technology Expense Management (TEM) provides a framework for reviewing connectivity, voice services, licences, support contracts, hardware, cloud consumption and specialist suppliers. The purpose is not to cut indiscriminately. It is to remove waste, duplication and unsuitable commitments so that funds can be redirected towards the controls that reduce business risk.
A TEM review may identify:
- Unused or duplicated software licences
- Connectivity services that no longer match the operating model
- Voice contracts with unsuitable capacity or terms
- Expired support agreements
- Hardware that is costly to maintain but not business-critical
- Cloud resources that are over-provisioned
- Separate tools performing overlapping backup or monitoring functions
- Suppliers without clear service responsibilities
This is strategically important. Savings from rationalised contracts can support tested recovery, improved identity controls, better monitoring or specialist IBM i expertise. Cost management and resilience should not be treated as opposing priorities. Good cost management makes resilience sustainable.
The same principle applies to bolt-on execution services. Cloud Solutions, Network Solutions, Voice and Connectivity, Helpdesk Support and Managed IT Services all underpin the strategy, but none should exist in isolation.
A resilient network is of limited value if critical applications have not been prioritised. A reliable voice service is not a substitute for a recovery plan. Helpdesk Support is essential during an incident, but only when escalation routes and decision-making authority are clear.
The Fractal IT Director model brings these elements together: high-level strategy first, specialist execution where required, and measurable commercial outcomes throughout.
ISO 27001 and Cyber Essentials reinforce the design
ISO 27001 and Cyber Essentials should be treated as practical governance frameworks, not paperwork exercises.
ISO 27001 encourages a risk-based information security management system, with documented responsibilities, controls, evidence, review and continual improvement. Continuity planning fits naturally within this structure because recovery objectives, testing records, supplier responsibilities and incident procedures can all be connected to identified risks.
Cyber Essentials provides a valuable baseline for common technical threats. Its five core areas include firewalls, secure configuration, security update management, user access control and malware protection. These controls directly affect continuity. Poor access management can delay recovery. Unpatched systems can become the route into a wider outage. Weak configuration can make a backup environment insecure.
The NCSC Cyber Essentials guidance makes clear that the scheme is intended to protect organisations against common online threats. For many SMEs, it provides a practical starting point for improving control and demonstrating that security is being actively managed.
Neither standard replaces a business-specific recovery strategy. Instead, both help create evidence that the strategy is governed, reviewed and maintained.
A continuity strategy should be tested as one system
The most effective continuity programmes bring the four layers together:
- Disaster Recovery defines how the business returns to operation.
- Dynamics 365 Jump Start aligns finance and operations with a structured implementation.
- IBM i Management protects specialist and legacy workloads while planning their future.
- Technology Expense Management makes resilience financially sustainable.
Around these sit the execution services: Cloud Solutions, Network Solutions, Voice and Connectivity, Helpdesk Support and Managed IT Services.
For organisations in property and real estate, continuity may also depend on wider operational services beyond the technology estate. Where that broader requirement is relevant, the Evestaff group can be accessed through its main gateway.
The strategic question is not whether an SME has backups, cloud services or a support contract. It is whether the complete operating environment can withstand disruption, recover in the right order and continue delivering value.
That is business continuity by design: a single, commercially informed IT strategy, led by consultancy and supported by the right technical specialists.
SEO tags: Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity, business continuity UK, Microsoft Dynamics 365 Business Central, ISO 27001 consultancy, Cyber Essentials consultancy, UK SME IT consultancy
Join The Discussion