Dynamics 365 upgrade and end of support

Upgrade or end of support putting your Dynamics 365 customizations at risk?

When a version, library or platform component reaches end of support, your custom plugins and workflow activities are what break. We upgrade them and prove that nothing your business depends on has changed.

Request a Health Check What the Health Check includes
  • 20+ years with Dynamics CRM and Dynamics 365
  • Ten-time Microsoft MVP
  • Hundreds of custom plugins and workflow activities written for customers worldwide

What an upgrade or end of support does to custom code

  • Code that signs in through a retired authentication library stops working or becomes a security risk
  • Integrations with no handling for the request limits the online platform enforces start to fail
  • Connections that are rebuilt on a timer or never released cause intermittent problems
  • Old SDK and framework versions, and dependencies bundled in ways Dataverse doesn't load, block the move
  • Source that no longer exists means nobody can change any of it
The risk isn't the upgrade. It's not knowing what changed. Custom code fails quietly, and a change that looks harmless can alter what runs against your data.

How we handle it

1

Inventory and risk check

Every custom component, what it does, and what in it won't survive the move.

2

Upgrade

Current Dataverse client and authentication, request-limit retries, and cleaned-up dependencies.

3

Prove nothing changed

Automated before-and-after tests, so differences are found and judged before release.

4

Document and hand off

Source in your repository, plain-English documentation, and a repeatable build.

Proof

Two upgrades, both proven rather than hoped for

On-premises to online

A lost-source integration, moved to Dynamics 365 Online

Replaced the retired authentication library with MSAL, turned on request-limit retries, and removed a connection leak, after recovering the source and covering it with 207 offline tests.

Read the case study
Upgrade without breaking

A 96-activity workflow assembly

An automated before-and-after test covering all 79 activities in the previously published version found every difference before release.

Read the case study

Common questions

Which versions do you support?

Dynamics 365 Customer Engagement (online and on-premises) and Dataverse.

Will you change anything in production?

No. We work in a non-production environment first, and nothing changes in production without your approval.

What if we don't have the source code?

That's one of our specialties. We recover it first, then upgrade it. See lost source code recovery.

How much does it cost?

We start with a fixed-price Plugin Health Check that tells you what needs to change, and quote any follow-on work from what we find.

Know what will break before the deadline does

Book a free 30-minute consult. We'll tell you what we'd check first, whether or not you hire us.

Request a Health Check

Free 30-minute consult first. Fixed price, quoted before we start.