For many UK SMEs, an ageing finance or ERP system stays in place because it still does the job. The reports run, invoices go out and the team knows its way around the screens. Replacing it can feel like a project for another quarter.
Then the supplier stops supporting it.
End of support turns a familiar system into a strategic decision. Without vendor updates, vulnerabilities may go unpatched, compliance evidence becomes harder to defend and recovery can be less certain. The deadline does not make migration simple, but it does make postponing the decision more expensive.
End of support is a business risk, not just a software date
A system can continue operating after its support ends. That does not mean it remains safe or suitable for the business.
An ERP environment is more than the application itself. It may include the operating system, database, integrations, add-ons, client software and remote-access routes. If any of these components are no longer supported, the business needs to understand the combined risk, not just check whether the ERP licence still works.
The UK’s Cyber Essentials requirements set expectations around supported software and security updates. Unsupported software in scope can affect certification; in some cases, the business may need to remove it from scope or isolate it appropriately. Isolation is a risk treatment, not a permanent replacement plan.
For organisations using ISO 27001 as their information-security framework, there is no single universal ERP migration deadline. The requirement is to identify and manage risk. That means recording unsupported systems, assessing their impact, applying appropriate controls and keeping a credible remediation plan. A decision to retain an ageing system should be documented, reviewed and approved, not left as an assumption.
Check the dates, and the whole environment
A supplier’s lifecycle page is the starting point. For example, Microsoft’s Dynamics 365 Business Central on-premises lifecycle policy lists support dates by release. As at 18 October 2026, version 26.x has passed its listed end date of 14 October 2026; version 27.x is listed through 6 April 2027.
These dates apply to those specific Business Central releases. They do not tell you the status of every older finance or ERP installation. Check the lifecycle for your actual product and version, then check the surrounding infrastructure and dependencies with the relevant suppliers.
Build a simple inventory covering:
- ERP version, database and operating system;
- add-ons, customisations and integrations;
- where data is stored and how it is accessed;
- update and vulnerability-management arrangements;
- backup, restore and recovery procedures;
- the business processes that depend on the system.
That inventory helps establish whether the next step is an upgrade, a migration, a replacement, or a short, controlled period of continued operation while the business prepares.
Make the migration a strategy, not a panic purchase
A support deadline can create useful momentum, but urgency is not a substitute for planning. Before choosing a new platform, clarify what the business needs from its finance and operational systems: which processes matter most, what data must move, what can be retired and which integrations genuinely earn their keep.
For suitable SMEs, Dynamics 365 Business Central may provide a supported route forward. A consultancy-led Dynamics 365 Jump Start should begin with discovery and design: assessing processes, data quality, reporting, security, integrations and the practical impact on staff. The purpose is not to reproduce every historic workaround in a new system. It is to decide what the business needs, then plan a controlled implementation around it.
Microsoft’s migration guidance matters too. The route depends on the version and starting platform; older Dynamics NAV installations, for example, may need an upgrade step before moving to Business Central online. Review the Microsoft migration guidance against the actual environment, and confirm technical requirements before setting a cutover date.
Keep legacy platforms safe while the plan is delivered
Not every business can switch off a legacy system immediately. Some organisations have established applications, specialist workflows or operational dependencies that cannot be replaced in a single step.
Where a business relies on IBM i Management, the right response is to assess the platform’s support status, access controls, network exposure, patching, monitoring and recovery arrangements. Specialist management can help keep an important legacy estate controlled while the organisation decides its longer-term architecture. The same principle applies to any system that must remain operational during a transition: know the risk, restrict unnecessary exposure and set a dated review or replacement plan.
This is where an IT consultant’s role is broader than arranging a server upgrade. David’s practitioner-led experience (including IBM i system administration, multi-national onboarding and Google-certified IT project management) supports strategic decisions grounded in how technology is used and operated. Specialist channel partners can add focused implementation capacity where required. The objective is a coherent roadmap, not a collection of disconnected supplier projects.
Protect continuity through cutover
A successful migration is not simply a new system going live. It is the transfer of critical processes and data with a workable route back if something goes wrong.
Before cutover, define who approves the change, what data will be reconciled, which interfaces must be tested and how long the business can tolerate disruption. Agree the rollback or contingency approach before the event, not while users are waiting for access.
Backups should be tested through restoration, and recovery plans should be realistic for the new environment as well as the old one. A backup that has never been restored is an assumption. A written Disaster Recovery plan should identify responsibilities, recovery priorities, dependencies and the steps needed to resume core operations.
During testing, include ordinary business tasks: posting transactions, checking reports, processing approvals, reviewing permissions and reconnecting integrations. The aim is to confirm that the organisation can operate, not merely that the software starts.
Fund the change through Technology Expense Management
Migration budgets are easier to defend when they are connected to measurable risk reduction and operational priorities. Technology Expense Management (TEM) can help identify spend that no longer supports the business: unused licences, duplicate tools, overlapping services and contracts tied to software that is unsupported or scheduled for retirement.
This is not about cancelling anything that looks expensive. Review usage, dependencies, renewal terms, security implications and the cost of replacing a service before making changes. A disciplined review may release budget for discovery, data cleansing, implementation and testing, while reducing the number of systems the business needs to support.
A useful roadmap can also coordinate related decisions across Cloud Solutions, Managed IT Services, Network Solutions, Helpdesk Support and Voice and Connectivity. These are execution services around the strategy, not a substitute for deciding what the business needs. Keeping that distinction clear helps avoid paying for activity without improving the underlying technology estate.
Turn the deadline into a decision
A practical first move is to name an owner and set a review date. Confirm the software lifecycle, document the business impact, assess Cyber Essentials and ISO 27001 implications, and compare the realistic options: migrate, upgrade, replace or temporarily contain the legacy environment.
Then build the delivery plan around business priorities, with defined responsibilities, funding, testing and recovery steps. If you need an independent view of the roadmap, Evestaff is the gateway to the group’s services, while IT Support and Consultancy focuses on technology strategy and implementation support.
End of support does not dictate one answer for every SME. It does remove the comfort of treating the decision as optional. A clear plan (supported by evidence, controlled execution and tested recovery) is a better investment than waiting for the deadline to choose for you.
SEO tags: ERP end of support, software end of life UK, Cyber Essentials consultancy, ISO 27001 consultancy, Disaster Recovery, Dynamics 365 Jump Start, IBM i Management, Technology Expense Management, Cloud Solutions, Managed IT Services, Network Solutions, Helpdesk Support, Voice and Connectivity
Join The Discussion