Xpert Dynamics

Legacy System Support

Help for older Dynamics CRM systems others no longer want to touch, and a clear path to Dynamics 365 and Power Platform.
Help for older and on-premises Dynamics CRM systems.

Overview

Old Systems Still Run Real Work.

At plenty of companies, an old Dynamics CRM server is still running the business. It is often version 2016 or older, and it still works. But Microsoft no longer supports any of them. The partner who built it may be gone, and the custom work was never written down. Every server patch is a small risk, and fewer people know how to fix things when they break. The system also sits outside most of what Microsoft now builds, such as Power Apps, Power Pages, and Copilot Studio.

There is usually more room than it seems between leaving the system alone and replacing it next month. We keep it running safely while you choose the next step and the right time to take it.

Three paths

Three Ways Forward

An older system can go one of three ways. We help you choose, and we support it on whichever path you pick.

01

Stabilise

Keep the current system running safely. We fix what breaks, write down how it works, and remove the risks we find, such as jobs that fail every night. Good fit when: The system still does the job, and you are not planning anything bigger for at least a year.

Keep the current system running safely. We fix what breaks, write down how it works, and remove the risks we find, such as jobs that fail every night. Good fit when: The system still does the job, and you are not planning anything bigger for at least a year.

02

Modernise

Move up to a newer on-premises version. You cannot jump straight there from an old release, so we plan and test each upgrade step. Along the way, we replace code that is no longer supported. Good fit when: You need to stay on your own servers, because of policy or other reasons.

Keep the current system running safely. We fix what breaks, write down how it works, and remove the risks we find, such as jobs that fail every night. Good fit when: The system still does the job, and you are not planning anything bigger for at least a year.

03

Move Online

Step by step, you move to Dynamics 365 online and bring your data, custom work, and integrations along. After that, Power BI and Power Automate work straight from the same data. Power Apps, Power Pages, and Copilot Studio do as well. Good fit when: You are done looking after servers and want what Microsoft is building now, Power Platform included.

Keep the current system running safely. We fix what breaks, write down how it works, and remove the risks we find, such as jobs that fail every night. Good fit when: The system still does the job, and you are not planning anything bigger for at least a year.

What we look after

What We Look After

Whatever path you choose, support usually covers:

What We Work On

Older and on-premises Dynamics CRM, including systems several versions behind.

  • Errors and failed jobs, including the ones that fail quietly every night.
  • Custom work nobody wrote down: plugins, workflows, scripts, and reports. We review it and write it down.
  • Integrations with your other systems, so they keep running.
  • Some Power BI reports and Power Automate flows may read your on-premises data. They do it through Microsoft's on-premises data gateway, and we look after that link too.
  • Regular checks on your CRM servers and SQL Server databases. We watch disk space, confirm backups run, and keep maintenance jobs working.
  • Checking Windows and SQL Server updates against your CRM version before they are applied.
  • Users, security roles, and access changes.
  • Small changes your team still needs while the bigger plan takes shape.

How It Works

How We Start

Every legacy system starts with the same five stages, each with a milestone you sign off. You set the pace for the bigger decisions.

01

Review

We look at the system as it is: version, servers, custom code, integrations, and what keeps breaking.

02

Write Down

We describe how it works in plain language, so the knowledge no longer sits with one person.

03

Stabilise

We fix the urgent risks first, such as failing jobs or servers running low on space.

04

Choose

We lay out the three paths, with the effort and risk of each. You choose.

05

Support

We look after the system on the path you chose, for as long as you need.

Who it's for

Who It's For

Clients usually come to us when:

You still run Dynamics CRM on your own servers, on a version Microsoft no longer supports.
The partner who built your system is gone, and so are the notes.
Your IT team keeps the servers running but does not know the CRM inside.
You plan to move online, just not this year.

Moving Online

Moving Online, When You Are Ready

Most on-premises systems make the move to Dynamics 365 online in the end. Microsoft puts its new features into the online version, including Power Platform and Copilot Studio, and servers need people to look after them. The timing should still suit your budget and your people.

We plan the move in stages. First we check your custom code against what the online version allows. Some code that runs on your own servers is blocked online, such as plugins that write to files on the server. Your data and history move with you, as described on our Data Migration page.

Faq's

Common Questions

Not seeing your question? Ask us.
Talk to us
It carries risk, because Microsoft no longer sends fixes for it, including security fixes. The risk can be reduced: limit who can reach the servers, keep Windows and SQL Server patched as far as your CRM version allows, and check that backups work. We help you do that while you plan the next step.
Yes. It is the usual case with older systems. We review the system and write down how it works as part of getting started.
No. If policy or anything else keeps you on your own servers, that is fine. We can keep today's system going. Or we can take it up to a newer on-premises version. You will know the effort and risk of both before you choose.
Some of it. Power BI can reach on-premises data through Microsoft's on-premises data gateway. So can Power Automate and canvas Power Apps. Power Pages needs Dataverse, and Copilot Studio works best with data in the cloud. For many teams, that is a good reason to plan the move online.
Not in one jump. Upgrades on your own servers go one major version at a time, so an old system has to climb through each release in order. It takes longer, but we plan and test every hop, and your live system is only touched once each one has passed in test.
Some of it will, and some will need changes. Code that reaches the server's files or other systems directly is not allowed online. We check each piece and tell you what needs to change before the move.

Talk To Us About Your Older System

Tell us which version you run and what worries you about it. We will tell you what we would do first.