Stop carrying the on-prem risk. Get a migration path you can stand behind.

A focused sprint that gives CIOs and senior leaders a realistic, staged plan to move from Dynamics CRM on-premise to Dynamics 365 Online — without guesswork.

Is This You?

You have a Dynamics CRM on-prem system that still supports your organisation.
Users depend on it; operations lean on it; integrations rely on it.

And yet, the cost of maintaining it is rising.

Not just licence and infrastructure cost.
Risk cost, complexity cost, knowledge cost, opportunity cost. All made worse by on-prem nearing end of life and being out of support.

Most executives are not trying to avoid migration.

They are trying to avoid an uncontrolled migration.

What the Sprint Is Designed to Solve

The On-Premise to Online Migration Sprint exists to answer the questions that stall decisions.

  • The On-Premise to Online Migration Sprint exists to answer the questions that stall decisions.
  • How much risk are we actually carrying?
  • What dependencies will bite us during migration?
  • What must be preserved, and what should be retired?
  • What are our non-negotiable constraints (security, data residency, uptime)?
  • What is the most controlled path forward?
  • What can we do now to reduce future cost and disruption?
  • What decision do we need to make first?

You do not need a 120-page technical document.
You need clarity you can take to governance.

What you get from the sprint

At the end of the On-Premise to Online Migration Sprint you will have:

1) Current-state clarity

A clear view of what exists, what matters, and what the organisation truly depends on.

2) A grounded view of migration complexity

An assessment tied to your environment. Not generic advice.

3) A staged migration pathway

Options, sequencing, and a recommended approach that balances risk, cost, and organisational capacity.

4) Executive-ready decision support

A concise briefing you can use for ELT, steering committee, and budget conversations.

What we do in the sprint

The On-Premise to Online Migration Sprint is intentionally short and structured.

Step One: Targeted discovery

Interviews with the people who understand the platform, its usage, and its constraints.

Step Two: Architecture and dependency review

Customisations, integrations, reporting, security model, and operational reliance.

Step Three: Risk and governance assessment

Supportability, security exposure, ownership, decision rights, and non-functional constraints.

Step Four: Migration pathway workshop

A working session to shape realistic options and an agreed direction.

Step Five: Executive briefing

A clear summary of findings, options, trade-offs, and recommended next steps.

What the Sprint is (and what it is not)

This is not:

  • a full migration project
  • a vendor selection exercise
  • a generic cloud pitch

This is:

  • Executive clarity and a controlled migration path

The sprint exists to reduce the likelihood of a pressured migration later.

Frequently Asked Questions

How long does the sprint take?
Typically delivered over a short, focused period. Enough time to get the facts and make decisions, without creating a long-drawn-out discovery phase.
Will you tell us to do a big bang migration?
Not unless it is genuinely the lowest-risk path, which is uncommon. Most organisations benefit from staged transition and deliberate simplification.
We have heavy customisations and integrations. Is the sprint still useful?
Yes. Those environments need clarity most. The sprint is specifically designed to surface hidden dependencies early.
We are highly regulated. Can we still move to online?
Often yes, but the constraints must be understood and designed for. The sprint is where those constraints become explicit.
Do you do the migration as well?
Opsis can support the broader program if you choose. The sprint is intentionally decision-focused. It gives you a plan you can execute with Opsis or with your preferred delivery partner.

Who Should Be Involved

  • CIO / Head of Technology (Sponsor)
  • Enterprise Architect or Applications Lead
  • CRM Product Owner or Senior Business Owner
  • Integration Lead or Technical SME
  • Security or Risk representative (where relevant)

Outcomes You Can Measure

After the sprint, you should be able to say:

We know our real dependencies.

We know where risk is accumulating.

We have a staged migration plan and clear next decisions.

We have clear ownership and governance.

We can proceed with confidence, or deliberately defer with controls in place.

I’m Gill Walker, and I help executive leaders protect and maximise the commercial value of their Microsoft Dynamics 365 investments — ensuring CRM delivers measurable business outcomes rather than becoming an increasingly expensive system.

This work is delivered through Opsis, where I advise organisations on Dynamics 365 strategy, governance, and transformation decisions — particularly where complexity, risk, or scale require experienced leadership.

  • Over twenty years of global CRM and transformation experience.
  • Trusted strategic advisor to government, not-for-profit, and complex commercial organisations across seventeen countries, and a former Microsoft MVP.
  • Founder of Opsis and recognised authority in Microsoft Dynamics 365 and Power Platform.

Opsis helps organisations succeed with Dynamics 365 through executive advisory, governance, and delivery leadership.

We help leaders make decisions early — when the options are still good. That is how you avoid the migration that happens to you, instead of the migration you control.

Start Privately

If you are still running Dynamics CRM on-prem and need a controlled path to Dynamics 365 online, let’s talk.