Workload and dependency review
Identify the systems in scope, how they connect and who uses them. Record application requirements, identity and access needs, data locations and external providers that could affect the change.
IT services
Plan an infrastructure upgrade or migration around the systems your organisation relies on. Subnet can help scope and deliver the change, with dependencies, testing, recovery arrangements and operational responsibilities agreed for your environment. Start with the outcome you need, then define the work required to get there.
WORK WITH SUBNET
When hosts, storage or operating systems approach a change point, the right project depends on the workloads they support. Subnet can scope infrastructure refreshes, selected virtual-machine migrations and defined server rebuilds around application dependencies and operating responsibilities.
Options can include HPE infrastructure, Microsoft Hyper-V or HPE VM Essentials where they fit the agreed design. These are distinct platforms with different requirements. Define the host, storage and backup components, migration ownership and acceptance checks for the option selected.
Operating-system and application upgrades, physical installation and customer-led migration tasks must be allocated explicitly. Redundant hosts do not remove the need for a change window or recovery plan. Additional recovery testing belongs in the agreed backup and disaster recovery scope.
WORK WITH SUBNET
Moving a workload or desktop service to Azure starts with checking whether the approach fits. Subnet can scope cloud feasibility reviews, bounded proofs of concept and selected Azure Virtual Desktop migrations or modernisation work.
A feasibility engagement may include interviews, a findings report and a roadmap. An agreed implementation may cover selected image and host-pool changes, identity or Intune dependencies, and user acceptance testing. Azure Site Recovery configuration and isolated recovery tests can be considered as a separate workstream.
Advisory work and proofs of concept have their own limits and do not automatically include production implementation, procurement or detailed design. Agree migration responsibilities, licensing and the test criteria. An isolated recovery test does not establish full failover readiness or include a complete recovery runbook.
An approaching renewal, ageing servers or a change in the way people work can create a reason to revisit your infrastructure. The difficult part is understanding what else will be affected: applications, identity, connectivity, backup and the people who support them.
A useful project brief makes those relationships visible before a migration or replacement is approved. It also identifies the business constraints, including busy periods, available change windows and the services that need particular care.
Your project may involve a platform migration, server and storage renewal, or changes across an existing on-premises and cloud environment. The right scope depends on the workloads, their dependencies and the operating model you want afterwards.
Identify the systems in scope, how they connect and who uses them. Record application requirements, identity and access needs, data locations and external providers that could affect the change.
Compare the proposed environment with the current one. Agree the migration sequence, access requirements, licensing assumptions and the conditions that must be met before each stage proceeds.
Define the configuration and migration tasks alongside the tests that will demonstrate whether the changed services are ready to use. Include the people who can validate real business activities, not only technical checks.
Make the support boundary part of the project brief. Agree the documentation, administrator access, unresolved issues and responsibilities needed by the team taking over after delivery.
Illustrative example: an organisation needs to replace an ageing virtualisation environment while keeping its business applications usable.
The project begins with an inventory of the applications and their dependencies. The organisation identifies the application owners and acceptable change windows. A representative workload is selected for a trial, with agreed checks for access, application behaviour and recovery.
The next group of workloads moves only after the agreed review. The implementation team records issues and exceptions, while business owners confirm whether key tasks work as expected. Handover records who will monitor, maintain and support the new environment.
Useful success measures could include completed acceptance tests, resolved migration defects and recovery-test results. Agree the targets and test method for the project.
Identify the decision-maker, business outcome and constraints on timing or expenditure.
Confirm which actions Subnet, your team and other providers will own, including how changes to the brief will be approved.
Name the people who can authorise a change, accept the results or stop the work if a condition is not met.
Review the completed work and any open issues. Decide whether further project work or an ongoing service is needed.
The proposal should name the environments and workloads covered, the implementation tasks, acceptance criteria and handover outputs. Any backup or recovery work needs its own clearly defined systems, responsibilities and tests.
Subnet helped Blackwood High School evaluate an alternative virtualisation platform and migrate its environment. The published case study describes the infrastructure decision and the reasons for reviewing the existing platform.
Read the Blackwood High School case studyNo. The brief can focus on the systems that need to change. Workload requirements, existing dependencies and your operating preferences should guide whether a service stays on premises, moves or is replaced. The design needs to be agreed for your environment.
Yes. Start with the reasons for the review, the workloads involved and the costs and constraints you already know. A useful comparison includes implementation, licensing, connectivity, recovery and ongoing operations. The depth of that assessment should be part of the agreed scope.
Agree change windows, workload sequencing, validation steps and recovery arrangements before implementation. Some changes can require an interruption. Its likely impact and any remaining uncertainty should be discussed for the affected services rather than assuming an interruption-free move.
Only the work specified in the project scope is included. Confirm which systems will be protected, how recovery will be tested and who will maintain the arrangements after handover. A successful migration test is not a substitute for a recovery test.
Yes. Identify the tasks and decisions your team will retain, where specialist project help is needed and which other providers must participate. Access, approval and acceptance responsibilities should be clear before the work starts.
That is an explicit handover decision. Support may remain with your team or be covered by a separately agreed service. Confirm the responsible team, escalation path and any post-project assistance in the proposal.
Moving a workload largely as it is (often called rehosting) usually changes the least and can be the quickest route, but it carries existing limitations into the new environment. Adjusting it (replatforming) makes limited changes to suit the new platform. Replacing it with a different product, or retiring it, suits workloads that no longer earn their place. Effort, risk and cost differ for each. The scope should state the approach assumed for every workload and who owns any application changes.
A common approach is to start with simpler, lower-risk workloads or non-production copies so the process can be proved before critical systems move. It also helps to include at least one representative workload with real dependencies early, so problems appear while the stakes are lower. Avoid busy periods such as financial close or major launches. The order should come out of the dependency review and be approved as part of the project plan.
Agree before each stage what counts as a failed change, who can make that call and how the previous state would be restored. Also record how long the previous environment or a recoverable copy is kept, and test the rollback steps where that is practical. Some changes cannot be fully reversed, so any point of no return should be identified and accepted in advance by the people who approve the change.
Applications rely on network links, name resolution, firewall rules and sign-in or directory services as well as on the servers themselves. Moving a workload can change any of these, and available bandwidth affects how long large data copies take. Services that handle authentication often need to move with the workloads that depend on them. The project brief should list these dependencies and say whether any connectivity or identity changes are in scope or a separate decision.
EXPLORE FURTHER
BEFORE WE TALK
You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.
LET’S TALK
Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.