Skip to main content

techsiagus.com

Cloud Strategy & Modelling

Cloud strategy and modelling — establishing which workloads should move, in what order, to which model, and on what commercial basis.

The problem

What usually brings people to this.

  • A cloud mandate without a workload-level plan
  • Cost projections that do not survive contact with the first migration
  • No agreed position on public, private or hybrid
What we do

Decide what moves, what stays, and what it will cost

Before any migration work, we model the estate: which workloads are suited to cloud, which are not, what the target model looks like, and what the run cost actually becomes. The output is a sequenced plan you can commit budget against.

  • 01

    Workload assessment

    Application and workload-level evaluation of cloud suitability.

  • 02

    Target operating model

    Public, private or hybrid — decided per workload rather than as a blanket policy.

  • 03

    Cost modelling

    Projected run cost against the current estate, including the cost of not moving.

  • 04

    Migration sequencing

    An ordered plan with dependencies and rollback points identified.

Technologies and frameworks in scope

  • Microsoft Azure
  • AWS
Methodology

How the engagement runs.

A defined sequence, so you know what is happening at any point and what comes out of each stage.

  1. 01

    Estate and workload inventory

    Establish what is actually running before deciding what moves.

    • Applications
    • Infrastructure
    • Dependencies
  2. 02

    Workload assessment

    Application and workload-level evaluation of cloud suitability.

    • Suitability
    • Constraints
    • Blockers
  3. 03

    Target operating model

    Public, private or hybrid decided per workload rather than as a blanket policy.

    • Public cloud
    • Private cloud
    • Hybrid cloud
  4. 04

    Cost modelling

    Projected run cost against the current estate, including the cost of not moving.

    • Projected run cost
    • Current estate cost
    • Cost of not moving
  5. 05

    Migration sequencing

    An ordered plan with dependencies and rollback points identified.

    • Order
    • Dependencies
    • Rollback points
  6. 06

    Plan and business case

    Close with a sequenced plan you can commit budget against.

    • Sequenced plan
    • Budget position
    • Stakeholder review
Deliverables

What you receive.

  • 01Workload assessment at application level
  • 02Target operating model per workload
  • 03Cost model and projected run cost
  • 04Sequenced migration plan with dependencies
  • 05A business case you can commit budget against
Outcome

What changes afterwards.

  • A workload-level plan rather than a cloud mandate
  • Cost projections that survive contact with the first migration
  • An agreed position on public, private and hybrid
  • Rollback points identified before work starts, not during it

Talk to us about cloud strategy & modelling.

Describe the estate and the constraint you are working within. We will tell you what the engagement would actually involve.

Questions

Before you get in touch.

Do you assess workloads individually, or apply one policy across the estate?

Individually — the target operating model (public, private or hybrid) is decided per workload rather than as a blanket policy, based on workload assessment.

Does the cost model include the cost of not moving?

Yes — cost modelling projects the run cost against the current estate, including the cost of staying where you are, not just the cost of migrating.

What do we actually get at the end of this engagement?

A sequenced migration plan with dependencies and rollback points identified — something you can commit budget against, not just a recommendation.

Does this include the migration work itself?

No — this is the modelling and sequencing stage. Cloud Migration Services then executes the plan in validated stages once it exists.