# Cloud migration services that move your systems in tested waves, with a rollback for each one

Cloud migration services plan and carry out the move of servers, databases and applications from your own hardware to a cloud platform, or between clouds. Goldenroz runs each migration as a project: a dependency inventory, a target design, a pilot wave, cutover runbooks and a tested rollback step for every wave. Projects start at $25,000 at a fixed price per phase, and larger programs run $100,000 and up.

**From $25,000, fixed price per phase**

Updated: 2026-11-14. By Shai Goldenberg.

## What usually goes wrong

- **A renewal date drives the plan:** A storage array leaving support or a hypervisor licence renewal forces a decision by a fixed date. A plan made against that deadline tends to skip the inventory.
- **Nobody knows what depends on what:** A scheduled job on an old server feeds the finance system and appears in no diagram. It surfaces the morning after cutover.
- **Lift and shift that raises the bill:** Virtual machines copied to the cloud at their on-prem size run all day at list price. The saving in the business case does not arrive.
- **Data too large for one window:** Big file shares and databases cannot be copied inside a single maintenance window over a normal link. The plan needs replication and a final sync, and both need a rehearsal.

## What is included

- **Discovery and dependency map:** An inventory of servers, virtual machines, databases, scheduled jobs, integrations, certificates and IP addresses, with the links between them.
- **Strategy per system:** Each workload is marked rehost, replatform, rebuild, retire or keep on-prem, with the reason and the cost of that choice.
- **Target design:** Accounts or subscriptions, networking, identity, backup and logging in the cloud, designed and approved before the first workload moves.
- **Pilot wave:** A small group of low-risk systems moves first to test the tooling, the timing and the runbook format.
- **Cutover runbooks and rollback:** Named owners, a maintenance window, checks that must pass and a rollback step that is tested before each cutover.
- **Documentation and handover:** Diagrams, configuration records, credentials in your name and a working session with your IT team.

## Cloud migration consulting: decide what moves before anything moves

Cloud migration consulting is the planning half of the work, and it is where most of the risk is removed. We assess your own workloads: what each system does, what it uses at peak, who depends on it and what it costs today. The output is a written plan with a fixed price for the next phase.

Not everything should move. Steady workloads with large data volumes, software licensed per physical core and systems tied to local equipment often cost less where they are. For many mid-size and large organizations the plan ends in hybrid cloud solutions: some systems stay on-prem, some move, and backup or disaster recovery sits in the cloud.

## On premise to cloud migration on AWS or Azure: what we do and what we do not claim

An on premise to cloud migration follows the same method as every move covered by our [IT infrastructure services](https://goldenroz.com/it-infrastructure-services/): inventory, waves, a pilot, runbooks and a rollback. Buyers looking for AWS migration services or Azure migration services usually ask which tooling is used. Both platforms provide their own replication and database migration tools, and we choose between those and a rebuild during the design phase.

We are direct about the evidence. Goldenroz has no published infrastructure case studies and does not claim a record of completed migrations onto AWS, Azure or Google Cloud. [Shai](https://goldenroz.com/about/shai/), our CTO, scopes and leads each project and is accountable for it, with senior infrastructure engineers working alongside him. For a very large move onto one platform, we say where a specialist partner should lead.

Once the systems are running in the cloud, release pipelines for them are covered by [DevOps consulting](https://goldenroz.com/devops-consulting/).

## What it costs

Every project starts with an assessment. Each phase after it has a fixed scope and price. Hardware, licences and hosting are paid directly by you to the vendor.

- Infrastructure project: From $25,000 (Fixed price per phase, starting with the assessment)
- Larger infrastructure programs: $100,000 and up (Data center migrations and multi-site programs over several phases)
- Hardware, licences and hosting: Paid by you (Bought directly from the vendor or distributor you choose)
- Scoping call: $0 (One hour with Shai)

## Who it is not for

- Small offices moving one file server or a few mailboxes, and budgets under $25,000.
- Buyers who need a vendor with published migration case studies or AWS or Azure partner status. We have neither.
- Application rewrites. Rebuilding software for the cloud is a software development project and is scoped separately.

## Questions buyers ask

### What do cloud migration services include?

At Goldenroz they include a discovery and dependency map, a migration strategy for each system, a target design, a pilot wave, cutover runbooks with a tested rollback, and a handover. Ongoing operation after the move is a separate retainer.

### How much does a cloud migration cost?

Projects start at $25,000 at a fixed price per phase, beginning with the assessment. Programs that move many systems over several phases run $100,000 and up. Our [pricing](https://goldenroz.com/pricing/) page explains how phases are quoted. Hosting, licences and data transfer charges are not included.

### How long does an on premise to cloud migration take?

It depends on the number of systems and how tightly they depend on each other. A few dozen servers are usually planned in months, including the pilot and a period of parallel running.

### Do you provide AWS migration services and Azure migration services?

We plan and run migrations to both, scoped per project. We hold no partner status with either vendor and do not claim a list of completed migrations on them. The platform choice is made in the assessment.

### Is a hybrid setup a sign the migration was left unfinished?

No. Hybrid is often the correct end state for an organization with steady on-prem workloads and newer systems that change in size.

---
Page: https://goldenroz.com/cloud-migration-services/
Book a free one-hour call: https://calendly.com/daniarozin/daniel-rozin-consultation-1-hour-clone
