From missed SLAs to
a full cloud transformation.
How WikiTech replaced a failing IT provider, migrated Ferns Group entirely to the cloud in 60 days, and became a long-term technology partner for a £150m infrastructure business.
The challenge
An IT provider that consistently overpromised and underdelivered.
Ferns Group had been with a large managed IT provider for years. On paper, the contract looked reasonable. In practice, the relationship had broken down. SLAs were regularly missed, tickets sat unresolved for hours, and the helpdesk lacked the technical depth to handle anything beyond basic issues.
For a business with 300 users across multiple operational sites, unreliable IT wasn't a minor inconvenience — it was a direct cost. The rigidity of the ticketing system meant that even straightforward, urgent issues like a locked account or a password reset required a formal ticket submission and an unpredictable wait.
Ferns were introduced to WikiTech by an existing client who had seen the difference first-hand. The recommendation led to an initial conversation with Ben, and it quickly became clear that a different approach was possible.
Missed SLAs — consistently
Response time commitments weren't being met. Issues sat in the queue while the business waited.
Helpdesk without the expertise
First-line staff couldn't resolve technical issues. Escalations were slow and accountability was unclear.
Rigid ticketing for urgent issues
A locked account or password reset — things that take minutes to fix — required a formal ticket and a long wait.
Bloated, costly infrastructure
Services had accumulated over the years. Many were unnecessary, outdated, or duplicated — and still being billed for.
The solution
A complete infrastructure transformation — delivered in 60 days.
WikiTech took over fully and immediately. The first priority was a thorough audit — stripping out unnecessary services and building a clear picture of what needed to change. What followed was one of the most comprehensive migrations WikiTech has delivered.
Exchange to Microsoft 365 Migration
Ferns' on-premises Exchange environment was migrated to Microsoft 365, giving 300 users access to modern email, shared calendars, and mobile access — with the reliability and security of Microsoft's cloud infrastructure behind it.
On-Premises to Cloud Server Migration
Physical on-site servers were decommissioned and workloads migrated to cloud-based alternatives. This removed the cost and maintenance burden of ageing hardware while providing the scalability Ferns needed to grow without predicting infrastructure spend years in advance.
Intune MDM & Azure AD Device Join
All company devices were enrolled in Microsoft Intune and joined to Azure Active Directory. Compliance policies were applied across the estate — giving IT visibility and control over every device, and ensuring remote workers are held to the same security standards as office staff.
Microsoft Teams & SharePoint
Teams and SharePoint were deployed and configured as the primary collaboration and document management platform. Staff across multiple sites gained a single place to communicate, share files, and work together — significantly reducing email volume and the confusion of multiple file storage systems.
Power BI Reporting
Ferns continue to develop their use of Power BI to surface operational data as meaningful, actionable reporting. Rather than exporting spreadsheets and building manual reports, key metrics are now available in real time to the people who need them.
Infrastructure Rationalisation
A full audit of existing services identified significant cost and complexity that had built up over time. Unnecessary licences, redundant services, and outdated tooling were removed — replacing a bloated, unpredictable infrastructure bill with a leaner, predictable cost model.
The migration
60 days. Zero business disruption.
A migration of this scale — Exchange, cloud servers, 300 devices, Intune, Azure AD — typically takes months. WikiTech delivered it in 60 days, planned and sequenced so that Ferns' operations were never interrupted.
Discovery & audit
Full inventory of existing infrastructure, services, and licences. Removal of unnecessary costs begins immediately.
Exchange & M365 migration
300 mailboxes migrated to Microsoft 365. Teams and SharePoint deployed and configured for all sites.
Server migration & Intune
On-premises servers decommissioned and workloads moved to cloud. All devices enrolled in Intune with compliance policies applied.
Handover & ongoing support
Full documentation produced. Support contract live. WikiTech becomes the single point of contact for all IT across Ferns' sites.
Three years ago our IT was a constant source of frustration — slow response times, missed SLAs, and a helpdesk that couldn't fix basic issues without a ticket and a long wait. WikiTech changed that from day one. The migration was complex but they delivered it without disrupting the business. Now I call Ben direct when something needs sorting, and it gets sorted. They've moved us entirely to the cloud, improved how our teams work together, and built tools that have genuinely made us more efficient. They feel less like a supplier and more like part of our team.
Beyond IT support
A custom compliance app — built by WikiTech, built for Ferns.
As the relationship deepened, it became clear that technology could do more than just keep the lights on. Ferns' vehicle fleet compliance process was manual, time-consuming, and reliant on staff manually cross-referencing data across multiple systems.
WikiTech designed and built a bespoke vehicle checking application to replace the manual process entirely. The app integrates directly with Ferns' hire and fleet management system for maintenance and repair records, and connects to the DVLA API to pull live vehicle data — MOT status, tax, and registration details — automatically.
What previously required staff to manually check and log compliance data across multiple sources is now automated. Ferns get accurate, real-time compliance visibility across the fleet — and the time that was being spent on manual checks is freed up for higher-value work.
This is what a Technical Account Manager who is also an engineer looks like in practice: understanding the business well enough to spot where technology can genuinely help, and being capable of building it.
Vehicle Compliance App
Custom built by WikiTech for Ferns Group
The outcome
What changed.
Three years on
Not just a support contract. A technology partnership.
Three years in, WikiTech's relationship with Ferns Group has grown well beyond day-to-day IT support. Quarterly Technical Account Manager reviews keep strategy aligned — reviewing the technology roadmap, identifying where automation or new tooling could reduce cost or improve efficiency, and making sure the infrastructure scales as the business grows.
The custom vehicle compliance app is one example of what that partnership looks like in practice. When Ferns identify a process that's costing time or money, the conversation starts with Ben — and if technology can fix it properly, WikiTech builds it.
Ongoing managed IT support across all sites — 300 users, single point of contact
Security maintained and reviewed quarterly — Intune compliance, patching, endpoint protection
Power BI reporting development — operational data surfaced as actionable insight
Custom app development — automating processes that used to cost significant staff time
Direct access to Ben — support issue or strategic conversation, one call away
Your dedicated Technical Account Manager
Every WikiTech client has a dedicated TAM — a senior engineer, not a sales contact. For Ferns Group, that's Ben Wicken. He knows their infrastructure, their team, and their business goals. When Harry calls, Ben answers.
Quarterly TAM reviews keep the technology strategy aligned with where the business is heading. New tooling, automation, custom development — it only gets proposed if it genuinely fits.
Ben Wicken
Managing Director & TAM — Ferns Group
Sound familiar?
If your IT provider is missing SLAs, lacks technical depth, or treats every call as a transaction — it might be time for a conversation.