Case Studies
Explore Symstar Technology Ltd case studies from real business IT projects. Read how we resolved full SharePoint storage for NFA UK, a London accounting company, and delivered a Microsoft 365 migration, file organisation and network improvements for MHC Group. Each project account explains the problem, the work delivered and the reported outcome.
Real projects. Practical improvements.
Explore how Symstar Technology Ltd helps businesses improve email, collaboration and their IT infrastructure.
ACCOUNTING · LONDON · SHAREPOINT STORAGE
NFA UK: SharePoint storage recovery
A large duplicated folder took NFA UK’s SharePoint environment to its 1 TB limit. Symstar retained copies in another SharePoint location and OneDrive, removed the duplicate and revised the desktop sync setup.
ACCOUNTING · MICROSOFT 365 · BUSINESS IT
MHC Group: Microsoft 365 migration and IT modernisation
For an accounting firm with around 30 staff in London and internationally, Symstar migrated email, organised business files and upgraded the network. The main project took two weeks, followed by several hours of adjustments.
On this page
Seven lessons from the MHC Group project and questions for your business
Lesson 1: connect email work to business needs

MHC Group’s published project describes a move from an ageing Exchange environment to Microsoft 365. The work included existing users, new accounts, shared mailboxes and distribution lists. A plugin also supported the firm’s bulk email workflow. These case studies help show why email projects need a discussion of the tasks people actually perform, rather than only a product selection. A different business may have different mailbox, licence or application requirements. Use the example to identify questions about your own communications and responsibilities, then define the proposed work and testing for your organisation separately.
Lesson 2: organise active business files
The MHC Group account describes business files on a local NAS without a clear structure. Symstar organised folders and moved active material to OneDrive, while older information was handled separately. Case studies can illustrate the importance of understanding which documents a team uses each day and who owns them. The same folder design is not automatically suitable for every organisation. Before a file project, identify current locations, authoritative copies and the access colleagues need. Agree how the result will be checked, including representative documents and user tasks, rather than treating a completed transfer as the only measure of success.
Lesson 3: make permissions part of the project
The published MHC Group example states that access was set according to business needs, with highly confidential files separated for access by the business owner. Case studies can help explain why a migration should consider who may use the information, not only where it will be stored. Another company may require a different access model and additional review. Identify the owners of important folders and the intended users before changes are made. Permission work should be authorised by the business and tested against legitimate tasks, with specialist or unresolved requirements kept visible in the project scope.
Lesson 4: distinguish current work from archives
The MHC Group project separated active files from material more than ten years old, which was moved to a local archive. Historical email was exported to PST archives on a local SSD. These are details of that particular project, not instructions that every business should adopt the same arrangement. Case studies can prompt useful questions about the information your organisation needs to use, retain or retrieve. Discuss ownership, access and recovery requirements for archives before choosing a design. Any retention or specialist requirements should be considered separately for the business and systems involved.
Lesson 5: include recovery requirements

The published project account reports daily local file and folder backups as part of the work delivered. That detail shows how recovery questions can sit alongside email and document organisation. Case studies should help you ask what information is protected, who checks copies and how restoration would be tested in your own environment. A backup arrangement described for one client is not a universal recovery plan. Discuss the systems, data locations and business priorities you need to cover, and agree the proposed service, checks and responsibilities before relying on an assumed ability to restore important work.
Lesson 6: consider the network alongside applications
The MHC Group example includes replacement of ageing network equipment, checks on RJ45 ports and connectors, and improved connectivity across the firm’s international sites. Case studies can show that an email or file improvement project may also depend on the infrastructure used to reach those services. Your premises, equipment and suppliers may differ, so a separate assessment is needed before selecting changes. Explain recurring faults, affected locations and the tasks that fail. A coordinated scope can then distinguish application work, connectivity requirements, onsite tasks and the responsibilities of any existing providers.
Lesson 7: allow for follow-up adjustments
The published MHC Group account describes a two-week main project followed by several hours of adjustments. That is the timing reported for this example, not a promised duration for other migrations or network work. Case studies can help you recognise that a project may need checks and refinements after the main implementation. Identify how users will confirm important functions and who handles remaining questions. Agree the scope, acceptance checks and follow-up arrangements for your own business. A realistic plan should reflect the systems, users and dependencies involved rather than copy another project’s timetable.
The business context behind the example
MHC Group is described as an accounting firm with around 30 staff working in London and internationally, without an in-house IT team. Its team depended on communication and document access for everyday work. Case studies are easier to assess when you understand this context, because the same technology can serve different needs in another organisation. Consider your team size, working locations, specialist applications and existing support arrangements when reading the example. Those details help frame a useful discussion about what is relevant to your business and what would require a different scope or approach.
The challenges described by MHC Group

The published account reports recurring email difficulties, slow computers, ageing network equipment and an unclear file structure. Repeated server faults and limited routine maintenance disrupted work, including preparation and delivery of submissions. Case studies connect technical symptoms with the tasks the business needs to complete. They do not establish the cause of a similar problem in another company. If you recognise the symptoms, record what happens, when it occurs and which colleagues are affected. Share that description when requesting an assessment so that proposed work is based on your actual environment and requirements.
What the client reported afterwards
The MHC Group page reports easier email communication and collaboration, documents that were easier to find and share, and a reduction in everyday missing-file problems. These are qualitative results reported in that project account. Case studies should distinguish those observations from an independently measured percentage or financial saving. No new saving or performance figure is claimed here. Use the reported experience to identify outcomes that matter to your team, then discuss how the result of your own project would be checked. A suitable measure depends on the task and the information available to the business.
Read the full project account
This overview is a starting point for exploring the example, while the full MHC Group page explains the client, challenges, work delivered and reported results in more detail. Case studies are most useful when you can see those parts together instead of relying on an isolated headline. Follow the project link above to understand the published account and its limits. If a particular service interests you, ask about that requirement in your own organisation. The example can inform the conversation without becoming an assumption that the same tools, scope or timing will automatically fit another business.
Look for a clearly defined problem
When reading case studies, identify the problem the business wanted to solve before examining the technology used. Was the issue email reliability, document access, a network fault or unclear support responsibilities? The starting point helps explain why particular work was chosen. A list of products alone does not show whether an implementation addressed the business need. For your own project, describe the task that is difficult and the outcome you want. This gives a provider something specific to assess and helps avoid choosing equipment or software before the requirements and dependencies have been understood.
Separate the example from your proposed scope
Case studies describe work for a particular client under particular circumstances. They are evidence to discuss, rather than a service agreement for every reader. Identify the parts of the example that resemble your business, then note the differences in users, locations, applications and responsibilities. Your proposed scope should explain the tasks, systems and deliverables actually included. Ask which items require another supplier or additional work. A clear distinction helps you compare a project example with the quotation you receive and prevents assumptions about features or support that have not been agreed for your organisation.
Ask who was responsible for each task
A project may involve the business, an IT provider, an internet supplier and specialist application companies. Case studies are easier to interpret when responsibilities are clear. If an example does not describe every dependency, ask about the responsibilities relevant to your proposed work rather than fill the gap with an assumption. Identify who can approve account changes, who owns the data and who will test the affected applications. Clear ownership can help coordinate a project and gives the business a useful route for questions during implementation and after the agreed work is completed.
Think about the information being moved
A migration can involve mailboxes, active files, archives and other business material with different access and recovery requirements. Case studies can illustrate how information was handled in one project, but your business may need a different design. Identify where the data is stored, which copies are authoritative and which users need it. Keep private records out of an initial enquiry; a clear description is enough to start the discussion. Before a transfer is agreed, confirm scope, authorisation and the checks needed to establish that the intended information remains available to the right people.
Consider the users affected by a change
A technically completed project still needs colleagues to be able to carry out their work. Case studies can help you look beyond infrastructure to account access, familiar tasks and practical handover. Identify the people affected, their applications and any important deadlines. Discuss how changes will be communicated and how users obtain help. A project proposal should recognise those requirements rather than assume that every employee can adapt without guidance. The appropriate training or handover work depends on the scope, so confirm what is included and what would need a separate arrangement.
Review how results can be checked
An outcome should have a practical way to be assessed. For email, that might involve the agreed communication tasks; for files, authorised users should be able to find and use the intended documents. Case studies can suggest questions about testing without proving that every possible scenario was covered in the published example. Define the acceptance checks for your own business before work begins. Include representative users and relevant applications. Record remaining issues clearly so that completed work can be distinguished from further investigation or new requirements that need another discussion.
Understand timescales in context
A duration reported in case studies belongs to the project described, with its particular users, systems and preparation. It is not a timetable that automatically applies to another business. Discuss the existing environment, dependencies, access and intended outcome before choosing dates. Important deadlines and the ability of staff to continue working may affect the plan. Ask which activities happen before the main implementation and what follow-up is included. A realistic schedule should identify responsibilities and checks, while leaving any additional work visible rather than assuming that it fits within an example’s reported duration.
Compare scope as well as price
Case studies can help explain the types of work a provider has delivered, but a quotation still needs its own clear scope. Compare users, systems, deliverables, testing and support arrangements alongside the price. Ask how licences, hardware, onsite work and third-party costs are handled. A project example does not establish what every future client will be charged. Confirm the proposed tasks, responsibilities and any exclusions in writing before deciding whether to proceed. This helps the business assess the service on its actual requirements and avoids relying on a headline or an assumed package of work.
Review recovery and support responsibilities
After a project, someone still needs to manage the systems and respond when a fault occurs. Case studies can prompt questions about backup checks, account changes, routine support and supplier ownership. Identify what would be included in any ongoing arrangement and what remains a separate task. Keep the business owner of important information clear. Ask how an incident is reported and who can approve recovery work. These questions help connect a planned improvement with the day-to-day responsibilities that follow, without assuming that a completed migration includes indefinite support or every future system change.
Use case studies to prepare better questions
Write down the parts of an example that are relevant to your team and the information you need before making a decision. Case studies may raise questions about shared mailboxes, file structure, account access, connectivity or project coordination. Bring those questions to the initial discussion alongside a description of your own environment. You do not need to know the exact technical solution before asking for help. A focused conversation can establish what needs assessment and which requirements are already clear, making the proposed next step more useful than a request to simply reproduce another client’s project.
Related services for a similar discussion
The MHC Group example connects several areas of business technology: email migration, document organisation, access permissions and networking. Case studies can help you recognise those relationships when exploring services. Symstar’s Microsoft 365, IT support, network and consultancy pages provide starting points for discussing the work your organisation may need. A similar symptom does not mean that every service is required. Describe the business problem and existing responsibilities first. Any proposed assessment, implementation or ongoing arrangement should have a scope suited to your systems, with dependencies and additional requirements confirmed before work is agreed.
Preparing your own project enquiry
Include the main problem or improvement you want, the approximate user count, business locations and current systems. Explain any timing requirements and identify the person who can approve the discussion. Case studies can be referenced to show the kind of outcome you are exploring, but keep differences in your environment clear. Do not send passwords, authentication codes or private customer records in the first message. Symstar can discuss a suitable next step using an ordinary overview, with further information or authorised access arranged only where needed for the agreed assessment or project work.
Read project material alongside independent guidance
Case studies are one source of information about a provider’s work. Independent guidance can also help you ask useful questions about account protection, backup and safe use of business technology. The NCSC small organisations guide linked below offers background for those discussions. It does not replace an assessment of your particular systems or define the scope of Symstar’s service. Use the project example, service information and your own requirements together when deciding what to ask. Any proposal should explain the tasks and responsibilities actually included, with additional services considered separately where needed.
Discuss a project with Symstar Technology Ltd
If the MHC Group example resembles difficulties in your business, tell us what is slowing your team down and which systems are involved. These case studies can begin a conversation about email, documents, networking and coordinated IT improvements. They do not promise the same results or timing for every organisation. Include a suitable contact method and your priorities, keeping sensitive information out of the initial message. Symstar can discuss requirements and an appropriate next step, with the work, availability and charges agreed separately before an assessment or implementation is arranged.
Explore Microsoft 365 support, business IT support and IT consultancy. For independent background, read the NCSC small organisations guide to cyber security.
